Wednesday, 2013-07-24

*** eharney is now known as Guest4639900:00
*** kebray has quit IRC00:00
*** Guest46399 is now known as eharney00:01
*** eharney has joined #openstack-meeting00:01
*** marun has joined #openstack-meeting00:03
*** zehicle_at_dell has quit IRC00:03
*** portante|afk is now known as portante00:04
*** virajh has quit IRC00:04
*** marun has quit IRC00:04
*** gokrokve has quit IRC00:05
*** ryanpetrello has quit IRC00:07
*** stevemar has joined #openstack-meeting00:09
*** michchap has quit IRC00:17
*** michchap has joined #openstack-meeting00:17
*** SumitNaiksatam has quit IRC00:18
*** jlucci has joined #openstack-meeting00:25
*** fmanco has joined #openstack-meeting00:33
*** nati_ueno has quit IRC00:35
*** ffive has quit IRC00:40
*** ayoung has joined #openstack-meeting00:40
*** gyee has quit IRC00:43
*** HenryG has joined #openstack-meeting00:44
*** jlucci has quit IRC00:47
*** ryanpetrello has joined #openstack-meeting00:53
*** cwolferh has joined #openstack-meeting00:54
*** nati_ueno has joined #openstack-meeting01:00
*** markvan has quit IRC01:00
*** SumitNaiksatam has joined #openstack-meeting01:01
*** nati_uen_ has quit IRC01:02
*** nati_ueno_2 has joined #openstack-meeting01:03
*** sjing has joined #openstack-meeting01:15
*** cody-somerville has joined #openstack-meeting01:18
*** markwash has joined #openstack-meeting01:18
*** danwent has quit IRC01:24
*** canadianchris has joined #openstack-meeting01:25
*** Mandell has quit IRC01:25
*** nati_ueno_2 has quit IRC01:27
*** nati_ueno_2 has joined #openstack-meeting01:29
*** danwent has joined #openstack-meeting01:29
*** stevemar has quit IRC01:31
*** danwent has quit IRC01:32
*** cody-somerville has quit IRC01:33
*** ryanpetrello has quit IRC01:33
*** markwash has quit IRC01:33
*** rods has quit IRC01:35
*** rnirmal has quit IRC01:38
*** yaguang has joined #openstack-meeting01:39
*** tanisdl has quit IRC01:42
*** rnirmal has joined #openstack-meeting01:45
*** rnirmal has quit IRC01:45
*** Tross1 has quit IRC01:49
*** chuckieb|2 has joined #openstack-meeting01:51
*** lbragstad has quit IRC01:54
*** chuckieb has quit IRC01:54
*** lbragstad has joined #openstack-meeting01:56
*** yaguang has joined #openstack-meeting01:56
*** neelashah has joined #openstack-meeting01:56
*** markvan has joined #openstack-meeting01:57
*** Tross has joined #openstack-meeting02:00
*** dcramer_ has quit IRC02:06
*** cwolferh has quit IRC02:08
*** venkatesh has joined #openstack-meeting02:09
*** gongysh has joined #openstack-meeting02:10
*** fnaval_ has quit IRC02:10
*** salv-orlando has quit IRC02:14
*** venkatesh has quit IRC02:16
*** chuckieb|2 has quit IRC02:18
*** yaguang has quit IRC02:19
*** dcramer_ has joined #openstack-meeting02:20
*** ilyashakhat_ has quit IRC02:23
*** Kharec has quit IRC02:24
*** Kharec has joined #openstack-meeting02:24
*** ilyashakhat has joined #openstack-meeting02:24
*** nati_ueno_2 has quit IRC02:32
*** yaguang has joined #openstack-meeting02:32
*** sjing has quit IRC02:39
*** vkmc has quit IRC02:40
*** markvan has quit IRC02:40
*** fmanco has quit IRC02:45
*** fmanco has joined #openstack-meeting02:45
*** fmanco has left #openstack-meeting02:46
*** yaguang has quit IRC02:51
*** fnaval_ has joined #openstack-meeting02:54
*** fnaval_ has quit IRC02:55
*** fnaval_ has joined #openstack-meeting02:56
*** Tross has quit IRC02:58
*** yaguang has joined #openstack-meeting02:59
*** stevemar has joined #openstack-meeting03:02
*** nati_ueno has quit IRC03:10
*** dcramer_ has quit IRC03:13
*** Tross has joined #openstack-meeting03:17
*** yaguang has quit IRC03:18
*** Mandell has joined #openstack-meeting03:18
*** jrodom has quit IRC03:22
*** yaguang has joined #openstack-meeting03:31
*** lbragstad_ has joined #openstack-meeting03:32
*** dguitarbite has joined #openstack-meeting03:33
*** MarkAtwood has joined #openstack-meeting03:37
*** jrodom has joined #openstack-meeting03:49
*** jrodom has joined #openstack-meeting03:50
*** Tross has quit IRC03:50
*** dguitarbite has quit IRC03:53
*** vipul is now known as vipul-away03:55
*** dguitarbite has joined #openstack-meeting03:57
*** ryanpetrello has joined #openstack-meeting03:58
*** mestery has joined #openstack-meeting04:00
*** SergeyLukjanov has joined #openstack-meeting04:03
*** canadianchris has quit IRC04:06
*** MarkAtwood has quit IRC04:06
*** MarkAtwood has joined #openstack-meeting04:07
*** nati_ueno has joined #openstack-meeting04:08
*** ryanpetrello has quit IRC04:12
*** vipul-away is now known as vipul04:13
*** ivar-lazzaro has quit IRC04:15
*** nati_ueno has quit IRC04:15
*** neelashah has quit IRC04:33
*** westmaas_ has joined #openstack-meeting04:33
*** garyk has quit IRC04:34
*** westmaas has quit IRC04:34
*** westmaas_ is now known as wesstmaas04:34
*** wesstmaas is now known as westmaas04:35
*** ryanpetrello has joined #openstack-meeting04:36
*** nati_ueno has joined #openstack-meeting04:42
*** nati_ueno has quit IRC04:46
*** MarkAtwood has quit IRC04:50
*** abaron_ has quit IRC04:52
*** canadianchris has joined #openstack-meeting04:52
*** nati_ueno has joined #openstack-meeting04:53
*** canadianchris has quit IRC04:54
*** glikson has quit IRC04:55
*** stevemar has quit IRC04:55
*** stevemar has joined #openstack-meeting04:57
*** Tross has joined #openstack-meeting05:03
*** vipul is now known as vipul-away05:04
*** colinmcnamara has joined #openstack-meeting05:05
*** colinmcnamara has quit IRC05:07
*** vipul-away is now known as vipul05:08
*** esker has joined #openstack-meeting05:08
*** lastidiot has quit IRC05:09
*** nati_ueno has quit IRC05:13
*** ryanpetrello has quit IRC05:23
*** fnaval_ has quit IRC05:29
*** koolhead17 has joined #openstack-meeting05:31
*** koolhead17 has joined #openstack-meeting05:31
*** SergeyLukjanov has quit IRC05:36
*** glikson has joined #openstack-meeting05:37
*** markpeek has quit IRC05:38
*** bdpayne has quit IRC05:40
*** garyk has joined #openstack-meeting05:45
*** nati_ueno has joined #openstack-meeting05:49
*** abaron_ has joined #openstack-meeting05:59
*** salv-orlando has joined #openstack-meeting06:00
*** mrunge has joined #openstack-meeting06:03
*** jrodom has quit IRC06:04
*** rwsu has quit IRC06:04
*** uvirtbot has quit IRC06:04
*** uvirtbot has joined #openstack-meeting06:04
*** rwsu has joined #openstack-meeting06:05
*** abaron_ has quit IRC06:19
*** sushils has quit IRC06:27
*** thomasbiege has joined #openstack-meeting06:29
*** uvirtbot has quit IRC06:29
*** uvirtbot has joined #openstack-meeting06:29
*** GheRiver1 is now known as GheRivero06:34
*** MarkAtwood has joined #openstack-meeting06:34
*** koolhead17 has quit IRC06:40
*** abaron_ has joined #openstack-meeting06:42
*** jhenner has joined #openstack-meeting06:42
*** brucer has quit IRC06:48
*** Mandell has quit IRC06:49
*** egallen has joined #openstack-meeting06:51
*** koolhead17 has joined #openstack-meeting06:52
*** Mandell has joined #openstack-meeting06:53
*** plomakin has joined #openstack-meeting07:04
*** MarkAtwood has left #openstack-meeting07:06
*** nati_ueno has quit IRC07:06
*** SergeyLukjanov has joined #openstack-meeting07:06
*** mrunge has quit IRC07:07
*** abaron_ has quit IRC07:08
*** pnavarro has joined #openstack-meeting07:16
*** yaguang has quit IRC07:17
*** dguitarbite has quit IRC07:17
*** salv-orlando has quit IRC07:18
*** ttrifonov_zZzz is now known as ttrifonov07:20
*** salv-orlando has joined #openstack-meeting07:21
*** salv-orlando has quit IRC07:21
*** mrunge has joined #openstack-meeting07:22
*** sushils has joined #openstack-meeting07:24
*** mrodden has quit IRC07:25
*** jcoufal has joined #openstack-meeting07:27
*** jrodom has joined #openstack-meeting07:30
*** slavayssiere has joined #openstack-meeting07:32
*** ndipanov_gone is now known as ndipanov07:36
*** dguitarbite has joined #openstack-meeting07:36
*** afazekas_ has joined #openstack-meeting07:40
*** stevemar has quit IRC07:40
*** Mandell has quit IRC07:43
*** jrodom has quit IRC07:43
*** jrodom has joined #openstack-meeting07:44
*** yaguang has joined #openstack-meeting07:45
*** dguitarbite has quit IRC07:48
*** dguitarbite has joined #openstack-meeting07:49
*** leseb has joined #openstack-meeting07:53
*** johnthetubaguy has joined #openstack-meeting07:59
*** dguitarbite has quit IRC08:01
*** johnthetubaguy1 has joined #openstack-meeting08:01
*** slavayssiere has quit IRC08:03
*** johnthetubaguy has quit IRC08:04
*** jhenner has quit IRC08:04
*** abaron_ has joined #openstack-meeting08:09
*** dguitarbite has joined #openstack-meeting08:14
*** abaron_ has quit IRC08:19
*** whenry has quit IRC08:20
*** abaron_ has joined #openstack-meeting08:21
*** jhenner has joined #openstack-meeting08:24
*** hemanth has joined #openstack-meeting08:27
*** dhellmann_ has joined #openstack-meeting08:27
*** derekh has joined #openstack-meeting08:28
*** jeblair_ has joined #openstack-meeting08:28
*** pleia2_ has joined #openstack-meeting08:29
*** martines_ has joined #openstack-meeting08:29
*** maurosr- has joined #openstack-meeting08:29
*** dhellmann has quit IRC08:29
*** guitarzan has quit IRC08:29
*** Guest79217 has quit IRC08:29
*** novas0x2a|laptop has quit IRC08:29
*** rdo has quit IRC08:29
*** akscram has quit IRC08:29
*** edleafe has quit IRC08:29
*** pleia2 has quit IRC08:29
*** maurosr has quit IRC08:29
*** mrunge has quit IRC08:29
*** martines has quit IRC08:29
*** asalkeld has quit IRC08:29
*** jeblair has quit IRC08:29
*** dhellmann_ is now known as dhellmann08:30
*** rdo has joined #openstack-meeting08:30
*** dabo- has joined #openstack-meeting08:30
*** mrunge has joined #openstack-meeting08:30
*** akscram has joined #openstack-meeting08:30
*** asalkeld has joined #openstack-meeting08:30
*** novas0x2a|laptop has joined #openstack-meeting08:31
*** guitarzan has joined #openstack-meeting08:33
*** yaguang has quit IRC08:34
*** cody-somerville has joined #openstack-meeting08:46
*** SergeyLukjanov has quit IRC08:49
*** slavayssiere has joined #openstack-meeting08:49
*** yaguang has joined #openstack-meeting08:52
*** johnthetubaguy1 is now known as johnthetubaguy08:53
*** SergeyLukjanov has joined #openstack-meeting08:55
*** dguitarbite has quit IRC08:56
*** boris-42 has joined #openstack-meeting09:05
*** abaron_ has quit IRC09:06
*** cody-somerville has quit IRC09:13
*** dguitarbite has joined #openstack-meeting09:14
*** Tross has quit IRC09:15
*** dguitarbite has quit IRC09:20
*** dguitarbite has joined #openstack-meeting09:22
*** abaron has joined #openstack-meeting09:26
*** salv-orlando has joined #openstack-meeting09:30
*** abaron has quit IRC09:39
*** rods has joined #openstack-meeting09:45
*** abaron has joined #openstack-meeting09:52
*** [1]glikson has joined #openstack-meeting10:04
*** jrodom has quit IRC10:05
*** glikson has quit IRC10:06
*** [1]glikson is now known as glikson10:06
*** pcm_ has joined #openstack-meeting10:09
*** pcm_ has quit IRC10:09
*** pcm_ has joined #openstack-meeting10:09
*** koolhead17 has quit IRC10:17
*** egallen has quit IRC10:26
*** ndipanov has quit IRC10:34
*** [1]glikson has joined #openstack-meeting10:34
*** glikson has quit IRC10:37
*** [1]glikson is now known as glikson10:37
*** slavayssiere has quit IRC10:38
*** glikson has quit IRC10:45
*** ndipanov has joined #openstack-meeting10:46
*** afazekas_ has quit IRC10:50
*** afazekas has joined #openstack-meeting10:51
*** gongysh has quit IRC10:52
*** yaguang has quit IRC10:54
garykboris-42: ping11:21
boris-42why in meeting?)11:21
boris-42probably it will be better in Nova to11:21
garykboris-42: did you read what you wrote on the review?11:21
garykoops my bad11:21
*** slavayssiere has joined #openstack-meeting11:21
boris-42go in Nova?11:22
*** bogdando has quit IRC11:27
*** bogdando has joined #openstack-meeting11:29
*** woodspa has joined #openstack-meeting11:33
*** thomasbiege has quit IRC11:36
*** chuckieb has joined #openstack-meeting11:37
*** salv-orlando has quit IRC11:50
*** brucer has joined #openstack-meeting11:50
*** dguitarbite has quit IRC11:53
*** afazekas is now known as afazekas_mtg11:55
*** jhenner has quit IRC11:56
*** jtomasek has quit IRC11:57
*** dkranz has joined #openstack-meeting11:57
*** afazekas_mtg has quit IRC12:01
*** slavayssiere has quit IRC12:01
*** jhenner has joined #openstack-meeting12:01
*** jtomasek has joined #openstack-meeting12:03
*** GheRiver1 has joined #openstack-meeting12:04
*** GheRiver1 has quit IRC12:04
*** Tross has joined #openstack-meeting12:08
*** canadianchris has joined #openstack-meeting12:09
*** thomasbiege has joined #openstack-meeting12:13
*** afazekas_mtg has joined #openstack-meeting12:14
*** branen_ has joined #openstack-meeting12:19
*** vkmc has joined #openstack-meeting12:19
*** vkmc has quit IRC12:19
*** vkmc has joined #openstack-meeting12:19
*** branen has quit IRC12:22
*** dprince has joined #openstack-meeting12:23
*** afazekas_mtg has quit IRC12:23
*** dandrushko has joined #openstack-meeting12:41
*** martine_ has joined #openstack-meeting12:41
*** henrynash has quit IRC12:45
*** slavayssiere has joined #openstack-meeting12:45
*** lbragstad_ has quit IRC12:46
*** jasondotstar has joined #openstack-meeting12:50
*** GheRivero has quit IRC12:55
*** GheRivero has joined #openstack-meeting12:56
*** lbragstad has quit IRC12:56
*** GheRivero has quit IRC12:56
*** GheRivero has joined #openstack-meeting12:56
*** henrynash has joined #openstack-meeting12:58
*** thomasbiege1 has joined #openstack-meeting12:58
*** anteaya has joined #openstack-meeting12:59
*** thomasbiege has quit IRC13:00
*** esker has quit IRC13:00
*** jhenner1 has joined #openstack-meeting13:02
*** jhenner has quit IRC13:04
*** alexpilotti has joined #openstack-meeting13:06
*** slavayssiere has quit IRC13:06
*** afazekas has joined #openstack-meeting13:10
*** matrohon has joined #openstack-meeting13:11
*** slavayssiere has joined #openstack-meeting13:14
*** glikson has joined #openstack-meeting13:16
*** egallen has joined #openstack-meeting13:16
*** sudorandom has joined #openstack-meeting13:20
*** pentameter has joined #openstack-meeting13:24
*** lbragstad has joined #openstack-meeting13:24
*** neelashah has joined #openstack-meeting13:25
*** ryanpetrello has joined #openstack-meeting13:28
*** koolhead17 has joined #openstack-meeting13:28
*** woodspa_ has joined #openstack-meeting13:29
*** henrynash has quit IRC13:30
*** woodspa has quit IRC13:32
*** brucer has quit IRC13:34
*** hemanth is now known as Guest4155013:38
*** markpeek has joined #openstack-meeting13:39
*** esker has joined #openstack-meeting13:42
*** ivasev has joined #openstack-meeting13:42
*** topol has joined #openstack-meeting13:44
*** rohit404 has joined #openstack-meeting13:49
*** stevemar has joined #openstack-meeting13:50
*** fmanco has joined #openstack-meeting13:52
*** thomasbiege1 has quit IRC13:53
*** thomasbiege has joined #openstack-meeting13:53
*** jrodom has joined #openstack-meeting13:55
*** jrodom has quit IRC13:55
*** jrodom has joined #openstack-meeting13:56
*** cp16net is now known as cp16net|away13:56
*** cp16net|away is now known as cp16net13:56
*** markvan_ has joined #openstack-meeting13:56
*** lifeless has quit IRC13:57
*** eharney has quit IRC13:57
*** rkukura has joined #openstack-meeting13:58
*** Sukhdev has joined #openstack-meeting13:58
mesteryHey, ML2 meeting time!13:59
*** glikson has quit IRC13:59
*** apech has joined #openstack-meeting13:59
*** BobBall has joined #openstack-meeting13:59
*** thomasbiege has quit IRC13:59
mestery#startmeeting networking_ml214:00
openstackMeeting started Wed Jul 24 14:00:03 2013 UTC.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking_ml2)"14:00
openstackThe meeting name has been set to 'networking_ml2'14:00
*** markvan_ is now known as markvan14:00
rkukurahi14:00
mesteryHi, apech, matrohon, rkukura here?14:00
apechhi, yup14:00
mestery#link https://wiki.openstack.org/wiki/Meetings/ML2 Agenda14:00
pcm_hi14:00
*** afazekas has quit IRC14:00
mesteryOK, lets get started14:01
mestery#link https://wiki.openstack.org/wiki/Neutron/ML2 ML2 Wiki Page14:01
mesteryThanks to rkukura for starting to add information to the ML2 Wiki14:01
*** asomya has joined #openstack-meeting14:01
mesteryI'm going to add some devstack information once we settle on the devstack direction for the patch I have in review14:02
Sukhdevgood morning14:02
mesterySukhdev: Hi!14:02
*** burt has joined #openstack-meeting14:02
mesterySo, any additional information people can add to the wiki would be great!14:02
mesteryI've noticed an uptick in the number of people asking for instructions on how to run ML2, for example.14:03
*** mrunge has quit IRC14:03
mesterySo, any other questions or concerns on the wiki?14:03
*** pnavarro has quit IRC14:03
mestery#topic Blueprint Updates14:04
*** openstack changes topic to "Blueprint Updates (Meeting topic: networking_ml2)"14:04
mestery#link https://blueprints.launchpad.net/quantum/+spec/ml2-portbinding ML2 portbinding14:04
mesteryrkukura: Any updates on portbinding?14:04
rkukuraI've been bogged down with other work this past week, so have made no progress coding14:04
*** lifeless has joined #openstack-meeting14:04
*** mrodden has joined #openstack-meeting14:05
mesteryrkukura: OK, no worries, thanks for the update!14:05
rkukuraAfter today, I hope to free up some time. If I can't get started by next weeks meeting, someone else may want to pick it up14:05
mesteryThat's what I was going to suggest as well.14:05
mesteryI'll make a note of that here.14:05
*** jlucci has joined #openstack-meeting14:06
mestery#action rkukura If no progress on portbinding BP by next week, find a new owner.14:06
matrohonhi14:06
mesteryrkukura: Along these lines, are we all in sync with arosen on the host_id thread on the ML?14:06
*** kevinconway has quit IRC14:06
rkukuramestery: Can you summarize the conclusion?14:07
*** kevinconway has joined #openstack-meeting14:07
mesteryrkukura: I think the summary was everyone wants to move port create to nova-api, but compute will still call update with the host_id afterwards.14:07
*** vijendar has joined #openstack-meeting14:07
rkukurathats what I thought14:07
*** kevinconway has left #openstack-meeting14:08
mesteryWe're ok with that I believe from an ML2 perspective, right?14:08
rkukuraseems there is also talk of replacing the update with a more explicit bind operation later, which I think is a good idea14:08
*** kevinconway has joined #openstack-meeting14:08
mesteryYes, that makes sense to me as well.14:08
mesterySo the direction there looks good in general and for ML2 specifically.14:08
*** kevinconway has quit IRC14:08
rkukuraI see no issue from ml2-portbinding perspective14:08
mesteryOK, anything else on portbinding from anyone?14:09
Sukhdevcan I ask a question for clarification -14:09
mesterySukhdev: Yes, please go ahead.14:10
Sukhdevby the time ML2 driver's port_create_precommint() is invoked, we will have the host-id info, right?14:10
*** doude has joined #openstack-meeting14:10
*** kevinconway has joined #openstack-meeting14:10
*** jlucci has quit IRC14:10
*** rnirmal has joined #openstack-meeting14:11
*** henrynash has joined #openstack-meeting14:11
apechmy understanding is that we'll still be able to get it, though it might be part of the update_port call. Is that right?14:11
rkukuraSukhdev: I don't think you can count on that - the host_id will likely be supplied in a later update()14:11
SukhdevOh I see - that changes the model a bit then14:11
apechslightly14:12
apechare arosen's changes going to land for H3?14:12
Sukhdevthanks for clarification -14:12
mesteryapech: Don't know, seems like he'll start working on them soon though.14:12
apechmestery: thanks14:13
rkukuraI think ml2's port binding can occur in three places: 1) port_create if host-id supplied, 2) port_update, 3) RCP processing for the port14:13
rkukuras/RCP/RPC/14:13
*** fmanco has quit IRC14:13
mesteryrkukura: That makes sense, and the BP you're working on will handle when that happens, right?14:14
*** fmanco has joined #openstack-meeting14:14
rkukurayes14:14
mesteryOK, thanks!14:14
mesteryLets move on to the next BP.14:14
mestery#link https://blueprints.launchpad.net/neutron/+spec/ml2-multi-segment-api ML2 multi-segment-api14:15
mesteryI don't think anyone is assigned to this BP yet.14:15
*** lastidiot has joined #openstack-meeting14:15
*** thomasbiege has joined #openstack-meeting14:15
mesterySo unless someone really wants it, I can take this one.14:15
*** markmcclain has joined #openstack-meeting14:15
mesteryrkukura: This would be nice to have for Havana I think, do you agree?14:15
rkukuraI agree, especially if the extension goes in for nvp14:16
*** zehicle_at_dell has joined #openstack-meeting14:16
mestery#action mestery to assign ML2 multi-segment BP to himself and begin working on it14:16
rkukuraOnly question I have is how the new extension interacts with the current provider extension14:16
mesteryGood question, I'll explore that and see what I can come up with.14:17
rkukuraI've got some thoughts on it too, so lets discuss14:17
*** fnaval_ has joined #openstack-meeting14:17
mesteryAbsolutely!14:17
mesteryOK, moving along to the last BP to discuss today.14:18
rkukurawe should do this via email on openstack-dev, CCing arosen14:18
mesteryrkukura: Agreed, lets start a thread there. Can you start the thread since you already have some thoughts on this?14:18
rkukuraOK14:18
*** stevemar has quit IRC14:19
mestery#action rkukura to start thread on ML around multi-segment API extension and how it interacts with existing providernet extension14:19
mestery#link https://blueprints.launchpad.net/neutron/+spec/ml2-typedriver-extra-port-info ML2 TypeDriver extra port info14:19
*** mrunge has joined #openstack-meeting14:19
mesterySo, this was registered last week by Zang MingJie.14:19
ZangMingJiethis is simple one14:19
mesteryAnd code was posted, but I thought we as a team should discuss this one here.14:19
*** dkranz has quit IRC14:19
ZangMingJieI'm already on it14:19
mesteryZangMingJie: Welcome!14:19
mesteryNot sure people have had a chance to eyeball this BP yet, but wanted to make sure the ML2 team saw this.14:20
rkukuraWould this also apply to QoS?14:20
ZangMingJieI don't think there is any relation to QoS14:21
mesteryMy only concern with the patch as pushed so far is it relies on an agent_id for the query. Not all ML2 MechanismDrivers will have agents.14:22
rkukuraThere wouldn't be RPCs unless there are agents, right14:23
rkukura??14:23
mesteryrkukura: Ah, right, good call.14:23
rkukuraThe ml2-portbinding will be adding mechanism drivers for the agent-based mechansims14:24
mesteryrkukura: You mean OVS and LB?14:24
*** salv-orlando has joined #openstack-meeting14:24
rkukurayes - they will inspect the agent-db data to decide if/what segment can be bound14:24
apechi could see this being useful for non agent-based mechanisms (if what we're talking about is getting the ip multicast address associated with a VXLAN)14:25
apechso (maybe specific to this piece of info) it'd be great if this could be exposed to mechansim drivers14:26
apechthough i guess this wouldn't be a direct call to the type driver anyway14:26
rkukuraI'd been thinking we'd eventually make the segment dictionary a bit more extensible - maybe this extra info belongs there?14:26
*** leseb1 has joined #openstack-meeting14:26
apechrkukura, yeah that would work14:27
mesteryDoes Vxlan mutlicast IP belong as part of hte port or the segment? To me, I think the segment.14:27
rkukuraDo all porting bound to the segment need to use the same multicast IP?14:28
rkukuras/porting/ports/14:28
*** lastidiot has quit IRC14:28
mesteryYes14:28
mesteryEach segment can have it's own muilticast IP though14:28
rkukuraIs there good use case for different segments having different IPs?14:28
rkukuraMaybe existing provider VXLANs?14:29
apechyeah - it limits broadcast domains14:29
ZangMingJiemultiple group can reduce multicast domains14:29
mesteryYes, that is the use case I was thinking of.14:29
*** eharney has joined #openstack-meeting14:29
*** leseb has quit IRC14:29
*** eharney is now known as Guest5059514:29
*** Guest50595 is now known as eharney14:30
*** eharney has joined #openstack-meeting14:30
mesteryOK, lets continue this discussion on the ML14:30
mesteryI'd like to spend some time on a few other items now.14:30
mestery#topic Bugs14:30
*** openstack changes topic to "Bugs (Meeting topic: networking_ml2)"14:30
rkukuraagreed, and its related to the multi-segment API14:30
mestery#link https://review.openstack.org/#/c/37516/ Validate Provider networks correctly14:30
mesterymatrohon: Here?14:30
matrohonyep14:31
mesteryHey, looks like you've made some progress on this one.14:31
matrohoni was ooo at teh begining of the week14:31
mesteryOnly minor issues left and then hopefully we can get this fix in.14:31
mesteryAh, ok.14:31
matrohonwill propose a new patch tomorrow14:31
mesteryGreat!14:31
*** dkranz has joined #openstack-meeting14:31
matrohonshould be merged quickly now14:31
HenryGmatrohon: nice cleanup, thanks!14:31
mestery#link https://bugs.launchpad.net/devstack/+bug/1200767 devstack patch for ML214:32
uvirtbotLaunchpad bug 1200767 in devstack "Add support for setting extra network options for ML2 plugin" [Undecided,In progress]14:32
*** jmontemayor has joined #openstack-meeting14:32
mesteryI know rkukura has taken a look at this one, but I'd appreciate more ML2 folks looking at this too.14:32
mesteryMy goal with this patch was to make the existing simple use case for GRE tunnel networks work with ML@.14:33
mesterys/ML@/ML2/14:33
matrohonwill do soon14:33
mesteryBut also allow for advanced ML2 configuration14:33
mesteryI've been running this with multi-node and ML2 and VXLAN with no problems, FYI.14:33
*** feleouet_ has joined #openstack-meeting14:33
rkukuraSo this maintains compatability with selecting tenant network types with the other plugins, right?14:33
mesteryYes, all existing devstack config variables should work with the latest rev of hte patch.14:34
mesteryPlease have a look and test it out if you can.14:34
matrohonmestery : did you try with bothe vxlan and gre14:34
rkukuraI plan to ASAP14:34
matrohoni will test it tomorrow too14:34
mesterymatrohon: I've run with both TypeDrivers loaded, but not with both networks at the same time. Will try that out and see how it goes though.14:35
matrohonit should be ok, if you don't specify the same tunnel id14:35
mesterymatrohon: Yes, agreed.14:35
mesteryAny more devstack+ML2 questions?14:36
ZangMingJiehttps://blueprints.launchpad.net/neutron/+spec/openvswitch-kernel-vxlan14:36
ZangMingJieI have made some change of the BP14:36
mesteryZangMingJie: That wasn't on the agenda for today.14:37
mesteryZangMingJie: I'll add it to the ML2 page, but we're following the agenda on the meeting page.14:37
rkukuraMy understanding is that the linux kernel upstream Open vSwitch implementation will be using this VXLAN implementation?14:37
mesteryrkukura: Yes, work is ongoing to make the upstream OVS integrate with the upstream VXLAN implementation.14:37
mesterySo eventually we will have to collapse the Neutron OVS VXLAN work as well.14:38
ZangMingJiethe kernel implementation is different of ovs vxlan14:38
mesteryZangMingJie: For now it is, but upstream OVS is integrating with the kernel implementation.14:38
rkukuraI think the OVS tree and kernel tree differ on this14:38
ZangMingJieit doesn't need tunnel point manipulation, so no tunnel sync call14:39
mesteryFor now, yes. Work ongoing to collapse the two.14:39
mesteryZangMingJie: There are pros and cons to multicast with Vxlan.14:39
mesteryI'd like to get the meeting back to the agenda now though.14:39
*** yaguang has joined #openstack-meeting14:39
mestery#link https://blueprints.launchpad.net/neutron/+spec/l2-population L2 Population14:40
mesterymatrohon: Will you start work on this BP soon?14:40
rkukuraZangMingJie: Can you please update the BP to clarify how this relates to the current OVS VXLAN support and the planned OVS cut-over to using kernel VXLAN support?14:40
matrohonmestery: it's started14:40
mesterymatrohon: Great!14:40
mesterymatrohon: Any chance you'll have a patch for this by next week?14:41
mesteryI think this will be a nice optimization14:41
*** jcoufal has quit IRC14:41
matrohoni'll be in vacation, so my colleagues will propose a patch before the end of the next week14:41
mesteryThanks.14:41
mestery#link https://bugs.launchpad.net/neutron/+bug/1177973 OVS L2 agent polling14:42
uvirtbotLaunchpad bug 1177973 in neutron "OVS L2 agent polling is too cpu intensive (dup-of: 1194438)" [Medium,In progress]14:42
uvirtbotLaunchpad bug 1194438 in neutron/grizzly "compute node's OVS agent takes long time to scan sync all port's stat and update port security rules" [High,In progress]14:42
mesteryAlong those lines, there is this bug as well.14:42
mesterymatrohon: Your colleague was working on this one too? Francois?14:42
matrohonZangMingJie : please have a look in l2-popiulation, for vxlan14:42
mesteryBut now it's unassigned.14:42
matrohonmainly safchain14:42
feleouet_Hi14:43
mesteryfeleouet_: Hi! You are no longer working on this bug?14:43
feleouet_I used to propose a first patchset, but the bug turned out to be fixed in a duplicate...14:43
mesteryAh yes, seeing that now.14:43
rkukuraI spoke with marun, who filed the L2 agent polling bug14:44
ZangMingJiematrohon: ye, I already got that, with l2 population, the control plane will be totally managed by agent14:44
*** gongysh has joined #openstack-meeting14:45
*** alexpilotti has quit IRC14:45
*** ashestakov has joined #openstack-meeting14:45
mestery#link https://bugs.launchpad.net/neutron/+bug/119696314:45
uvirtbotLaunchpad bug 1196963 in neutron "Update the OVS agent code to program tunnels using ports instead of tunnel IDs" [Wishlist,In progress]14:45
mesterymatrohon: Is this duplicated or fixed with your L2 population work?14:45
*** ashestakov has left #openstack-meeting14:45
matrohonmestery : not really, we need a first patch to have gre and vxlan with the same id on the same agent14:46
mesterymatrohon: OK, thanks.14:46
matrohonmestery : but l2-population will improve this functionnality14:46
*** spzala has joined #openstack-meeting14:47
mesterymatrohon: Got it.14:47
mestery#topic Ported MechanismDriver Updates14:48
*** openstack changes topic to "Ported MechanismDriver Updates (Meeting topic: networking_ml2)"14:48
mesterySukhdev_: Arista driver update?14:48
*** changbl has quit IRC14:48
*** sivel has quit IRC14:49
*** sivel has joined #openstack-meeting14:49
mesteryFor the Cisco update, rcurran is still on PTO for another week, so not much to report there.14:50
apechi'm happy to update there - mostly the same as last week, working on unit tests and waiting to make the final changes on the port-binding bp14:50
mesteryapech: Thanks for the update!14:50
*** michchap has quit IRC14:50
mesteryFor OpenDaylight, the OVSDB support for ODL was approved, and we are now integrating that with our ODL MechanismDriver.14:50
mesteryWe hope to have a POC by next week which ties all of this together.14:50
mesteryasomya is working on this with me at the moment.14:51
*** MarkAtwood has joined #openstack-meeting14:51
mesteryIf Luke Gorrie is here, he can provide an update on the Tail-f NCS MechanismDriver.14:51
mestery#topic Questions?14:52
*** openstack changes topic to "Questions? (Meeting topic: networking_ml2)"14:52
mesteryAnything else ML2 related this week from anyone?14:52
fmancoHi everyone14:52
rkukuraCongrats to mestery on becoming neutron core!14:52
*** gongysh has quit IRC14:52
fmancoJust want to know if someone looked at my BP14:52
mesteryrkukura: Thanks!14:52
*** salv-orlando has quit IRC14:53
mesteryfmanco: Sorry, I think I missed that in the meeting.14:53
mestery#link https://blueprints.launchpad.net/neutron/+spec/campus-network Campus Network BP14:53
fmancomestery: no prob14:53
mesteryfmanco: I think rkukura was going to have a look at this in detail and provide feedback.14:53
fmancoAnd btw congrats for the core position14:53
mesteryfmanco: thank you!14:54
rkukurafmanco: Sorry - I have not got to this yet. Others should review as well.14:54
mesteryfmanco: Did I post the link to the correct BP?14:55
mesteryOr was there an ML2 specific one?14:55
mesteryCan you add it here if I didn't post the right one?14:55
ZangMingJiehttps://blueprints.launchpad.net/neutron/+spec/ml2-external-port this one ?14:55
fmanco#link https://blueprints.launchpad.net/quantum/+spec/ml2-external-port14:55
fmancoZangMingJie: Yes14:56
mesteryThanks ZangMingJie.14:56
mestery#action ML2 team to review https://blueprints.launchpad.net/neutron/+spec/ml2-external-port14:56
mesteryfmanco: Will provide feedback on ML.14:56
*** Mandell has joined #openstack-meeting14:57
rkukuraWe should create a "punch list" leading to ml2 becoming default plugin in devstack14:57
fmancoJust and update. I already started some code. I hope I can submit at least a sketch for review14:57
*** Gordonz has quit IRC14:57
mesteryrkukura: Yes, agreed.14:57
rkukuraneed to document ml2, get into CI, etc.14:57
mesteryrkukura: I will ping sean and dean about this as well to give them a heads up.14:57
HenryGGeneral question -- what different things do these try to accomplish: providernet, multi-segemnt, external-port ?14:58
HenryGSeems to be a lot of overlap?14:58
mesteryHenryG: Lets take that to the ML I think, we only have < 2 minutes left. :)14:59
HenryGOf course.14:59
mesteryOK, thanks folks! Remember: H3 freeze is about 4 weeks out.14:59
mesterySo lets try to finish up the ML2 BPs and bugs in the next few weeks if we can!14:59
mestery#endmeeting14:59
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Wed Jul 24 14:59:32 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_ml2/2013/networking_ml2.2013-07-24-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_ml2/2013/networking_ml2.2013-07-24-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_ml2/2013/networking_ml2.2013-07-24-14.00.log.html14:59
*** apech has quit IRC14:59
johnthetubaguy#startmeeting XenAPI15:00
openstackMeeting started Wed Jul 24 15:00:24 2013 UTC.  The chair is johnthetubaguy. 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: XenAPI)"15:00
*** matel has joined #openstack-meeting15:00
openstackThe meeting name has been set to 'xenapi'15:00
*** asomya has left #openstack-meeting15:00
johnthetubaguyhello all, show of hands for who is around?15:00
matelI am here, Bob is back in a moment.15:00
johnthetubaguyOk, will wait for Bob15:01
*** matrohon has quit IRC15:01
*** rkukura has left #openstack-meeting15:01
johnthetubaguymatel: got anything extra for the agenda?15:01
*** tanisdl has joined #openstack-meeting15:01
matelI just ran a full tepest, it seems, console is working.15:02
matel#link https://review.openstack.org/#/c/38444/15:02
BobBallBob is here!15:02
johnthetubaguyI saw your patch - thank you :)15:02
euanhI'm here15:02
BobBallYes - very pleased that full tempest is working :)15:02
BobBallHi Euan!15:02
matelI didn't say full tempest is working :-)15:02
johnthetubaguymatel: cool, nice devstack change15:02
*** alexpilotti has joined #openstack-meeting15:02
johnthetubaguyanyway, lets keep to the agenda15:02
johnthetubaguyjust collecting items for the agenda15:02
matelOkay.15:02
BobBallFull tempest isn't working yet? No holidays for you.15:02
matelI know.15:03
*** salv-orlando has joined #openstack-meeting15:03
*** lastidiot has joined #openstack-meeting15:03
*** mrunge has quit IRC15:03
BobBallThere are a few things to say - such as xenserver-core15:03
matelthis one is failing only with an error tempest.api.volume.test_volumes_actions.VolumesActionsTest.test_volume_upload15:03
*** salv-orlando has quit IRC15:03
johnthetubaguyOK15:03
matelOkay, let John drive.15:03
johnthetubaguy#topic actions from previous meetings15:04
*** openstack changes topic to "actions from previous meetings (Meeting topic: XenAPI)"15:04
johnthetubaguyBobBall: update blueprints15:04
*** dandrushko has quit IRC15:04
johnthetubaguyI think you did that right?15:04
BobBallDone that15:04
BobBallyes15:04
johnthetubaguycool15:04
BobBallprimarily just de-targeting havana15:04
johnthetubaguy#topic Blueprints15:04
*** openstack changes topic to "Blueprints (Meeting topic: XenAPI)"15:04
johnthetubaguyso, just tracking progress15:04
BobBallWe've got a major focus internally on updating both XS code and OS code to work within supported interfaces15:05
BobBallbut that's not really a blueprint15:05
johnthetubaguyH-3 is obvious the last time for features till I, and its getting very full15:05
*** whenry has joined #openstack-meeting15:05
BobBall*nod*15:05
BobBallWe've got a couple of things we're planning to target I-1 and I-2 - if things fall in the right place - and they will definitely need blueprints15:05
BobBallbut it's too early to write them15:05
johnthetubaguyOK, well you can enter blank ones so people know15:06
johnthetubaguyits quite lightweight, but up to you, obviously15:06
johnthetubaguyits worth thinking about everything for I re-talking at the summit about things15:07
*** hub_cap has left #openstack-meeting15:07
BobBallindeed15:07
BobBallwe're looking at having a couple of summit sessions15:07
BobBallhopefully!15:07
johnthetubaguywe have the oslo lib work that needs some work, and things that got dropped, would be good to chase those15:07
johnthetubaguyseveral summit sessions?15:08
BobBallI don't want to put the blueprints up yet since there are a few things I need to sort out here first15:08
BobBallon different subjects15:08
johnthetubaguyOK15:08
johnthetubaguyI have one blueprint for H-215:09
johnthetubaguyconfig drive stuff15:09
*** pleia2_ is now known as pleia215:09
*** martines_ has quit IRC15:09
johnthetubaguyits getting there15:09
johnthetubaguyso...15:10
johnthetubaguy#topic Docs15:10
*** openstack changes topic to "Docs (Meeting topic: XenAPI)"15:10
johnthetubaguyhow are we doing with docs?15:10
BobBallUhhh - are there bugs that you're thinking about?15:10
BobBallor specific improvements that you were expecting us to do?15:10
johnthetubaguynot really tracking that15:11
johnthetubaguywe kinda try to do an end of release review of the docs15:11
annegentleBobBall: there are doc bugs for Xen, is that what you're asking?15:11
BobBallahhh I see yes15:11
johnthetubaguyjust wanted to make sure something is done around that15:11
annegentleBobBall: one idea we had was to collect them all into a doc blueprint?15:11
johnthetubaguywe added quite a few15:11
johnthetubaguyannegentle: ah yes, that sounds like a good plan15:11
BobBallannegentle: I know... I meant more in terms of the agenda for today's XenAPI meeting15:12
johnthetubaguywe can track that here15:12
annegentlejohnthetubaguy: I kinda liked the idea, Steve Gordon suggested it.15:12
annegentlejohnthetubaguy: ok we'll gather 'em up15:12
johnthetubaguyannegentle: ping me if I can help with that15:12
annegentlejohnthetubaguy: will do15:12
*** feleouet_ has quit IRC15:12
BobBallSounds good to me!15:12
*** oNeToWn has joined #openstack-meeting15:12
johnthetubaguycool, keen we don't let docs slip15:12
*** nati_ueno has joined #openstack-meeting15:13
johnthetubaguysweet15:13
johnthetubaguythe install guide is a big one that hasn't been brought up for a bit I guess15:13
*** tanisdl has quit IRC15:14
johnthetubaguydoesn't really cover the openstack-nova-xcp kinda things in ubuntu, etc15:14
johnthetubaguybut thats a big topic15:14
johnthetubaguyanyway, lets talk bugs...15:14
johnthetubaguy#topic Bugs and QA15:14
*** openstack changes topic to "Bugs and QA (Meeting topic: XenAPI)"15:14
johnthetubaguyhas anyone got any bugs they want to raise15:14
BobBallyeah15:14
BobBallI think so15:14
BobBallbut I'm not totally sure15:14
BobBallI _think_ security groups doesn't work in XS15:14
matelA fresh one: #link https://bugs.launchpad.net/cinder/+bug/120455115:15
uvirtbotLaunchpad bug 1204551 in cinder "xenapi: volume upload fails" [Undecided,New]15:15
matelI am doing that.15:15
matelNot sure if it is xenserver related, but we 'll see.15:15
BobBallI suspect it used to, when the default stack was linux bridge, but with the OVS the iptables rules only get called at some points15:15
*** doude has left #openstack-meeting15:16
BobBallI think that security groups are not working on any distro that uses OVS and not NVP15:16
johnthetubaguydoes it work with NVP?15:17
BobBallI assume so - that uses a different firewall driver15:17
johnthetubaguyI guess they do there own OVS rules15:17
BobBallbut the firewall driver which is an OVS iptables hybrid just uses iptables rules15:17
johnthetubaguyright, so there are security groups by nova, and security groups by neutron I guess15:17
BobBalland I don't think they work15:17
BobBallprobably either in nova or neutron15:17
BobBallsince neutron just took that file from nova ;)15:17
*** tanisdl has joined #openstack-meeting15:17
johnthetubaguysounds like you should raise a security bug for that, just in case15:18
johnthetubaguylets not discuss that here15:18
johnthetubaguyneutron, is a different control path to trigger, but yes, may have the same "issues"15:18
johnthetubaguyOK, any more bugs?15:18
BobBallI'm not ready to raise a bug15:19
BobBallI don't know for sure that it doesn't work15:19
BobBalljust theory says it can't15:19
BobBallin practice it might be different ;)15:19
johnthetubaguyOK, but it sounds like a security issue, people can help through that channel15:19
johnthetubaguythis has public logs15:20
*** fmanco has left #openstack-meeting15:20
BobBallokies15:20
johnthetubaguyany more bugs?15:21
matelCould you re-visit #link https://review.openstack.org/#/c/36523/15:21
BobBallMate's bug15:21
johnthetubaguyewanh: https://bugs.launchpad.net/nova/+bug/1073306 think we are clashing on this15:21
BobBallwe haven't talked about that15:21
uvirtbotLaunchpad bug 1073306 in nova "xenapi migrations don't apply security group filters" [Medium,In progress]15:21
euanhI added a comment on https://bugs.launchpad.net/nova/+bug/107330615:22
matelMate just linked his bug for the record, he will just fix it, no talk needed around that.15:22
johnthetubaguyeuanh, yeah, cool, maybe raise a separate bug for live-migration15:22
euanhI was looking at it in live migration15:23
euanhso we don't clash15:23
euanhyes, plan to15:23
johnthetubaguyeuanh: cool, thats all good, thanks15:23
johnthetubaguyeuanh: might need to raise a security bug for that one15:23
johnthetubaguyOK, any more?15:25
*** sudorandom has left #openstack-meeting15:26
johnthetubaguyI wanted to ask about gating XenAPI15:26
*** JM1 has joined #openstack-meeting15:26
johnthetubaguyhow is that effort going?15:26
BobBallsure15:26
BobBallscheduled to start in earnest at the start of August15:26
BobBallwell - first full week in august15:26
BobBallthen we'll be trying to commit some code ;)15:27
johnthetubaguyOK, whats the plan?15:27
johnthetubaguysmokestack gating, using tempest?15:27
BobBallnot using tempest15:27
johnthetubaguyOK, just smokestack then?15:27
BobBallyup15:28
matellet's say torpedo15:28
BobBallwe need to make it more stable WRT how it handles packages15:28
matelIt's a bit confusing.15:28
BobBalland ensures that we can merge packages suitably15:28
johnthetubaguywhat about the tempest work today, is that planning to get into the gate?15:28
matelI don't understand.15:28
BobBallfingers crossed - but nothing as concrete for that15:28
johnthetubaguydoing nova-compute in dom0, is what I was meaning by tempest15:28
johnthetubaguymirroring the QEMU tests that are there today15:29
BobBalloh right15:29
BobBallnova-compute in dom0 - should be looking at that RSN15:29
*** jtomasek has quit IRC15:30
matelwhat is RSN?15:30
johnthetubaguyRSN?15:30
*** Mandell has quit IRC15:30
BobBallreal soon now ;)15:30
johnthetubaguyOK, so heading for both?15:30
BobBallMaking sure there is a fallback option perhas15:30
BobBallperhaps*15:30
johnthetubaguytempest and torpedo15:30
johnthetubaguyhmm, ok15:30
*** vijendar has quit IRC15:31
johnthetubaguyit does seem odd to gate on external packages15:31
BobBallwe won't gate on external packages15:31
johnthetubaguyalways went for tempest so it was easy for committers to make the required depenency changes etc15:31
BobBallif packaging fails then it won't prevent the gate15:31
johnthetubaguyOK, so an optional gate?15:31
johnthetubaguyexample: I add a xenapi plugin15:32
BobBallyes15:32
BobBallif plugin fails then it won't -2 vote15:32
*** YorikSar has joined #openstack-meeting15:32
*** kebray has joined #openstack-meeting15:32
johnthetubaguyhmm, OK15:33
*** boris-42 has quit IRC15:33
BobBallMy current hope is https://docs.google.com/presentation/d/1qTvZ8kmByOrtilYhc_BiwOhkzpN-GT0UTbniusnKohI/edit?usp=sharing15:33
*** ollie1 has joined #openstack-meeting15:33
*** ollie1 has left #openstack-meeting15:33
BobBallalthough this workflow hasn't been approved with the infra team yet15:33
*** rongze1 has joined #openstack-meeting15:33
johnthetubaguyOK, it does seem quite a change15:34
BobBallnot really15:34
BobBallgate as is runs as normal15:34
johnthetubaguymy 2 cents would be to do both, if tempest is the major test suite15:34
johnthetubaguyetc15:34
johnthetubaguybut anyways15:34
johnthetubaguysounds like there is good progress15:34
BobBallofc - tempest will remain and run the full tests etc15:34
*** danwent has joined #openstack-meeting15:34
johnthetubaguyjust be good to see tempest running on XenServer and gating commits, if its going to survive15:35
BobBallIt would indeed15:35
johnthetubaguycool15:35
johnthetubaguysounds like we are mostly agreed15:35
johnthetubaguy#topic Open Discussion15:36
*** openstack changes topic to "Open Discussion (Meeting topic: XenAPI)"15:36
johnthetubaguyso, anything more?15:37
BobBallnothing from me15:37
euanhnope15:37
johnthetubaguynor me15:37
BobBall*puts on his best Mr Burns voice* excellent15:38
johnthetubaguythanks all15:38
johnthetubaguy#endmeeting15:38
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"15:38
openstackMeeting ended Wed Jul 24 15:38:50 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-07-24-15.00.html15:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-07-24-15.00.txt15:38
openstackLog:            http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-07-24-15.00.log.html15:38
*** martines has joined #openstack-meeting15:39
*** BobBall has left #openstack-meeting15:40
*** leseb1 has quit IRC15:43
*** colinmcnamara has joined #openstack-meeting15:43
*** matel has quit IRC15:44
*** jdurgin1 has joined #openstack-meeting15:45
*** virajh has joined #openstack-meeting15:45
*** bpb has joined #openstack-meeting15:45
*** diogogmt has joined #openstack-meeting15:46
*** rongze1 has quit IRC15:46
*** litong has joined #openstack-meeting15:46
*** rongze1 has joined #openstack-meeting15:46
*** branen_ has quit IRC15:47
*** branen has joined #openstack-meeting15:47
*** bdpayne has joined #openstack-meeting15:48
*** gongysh has joined #openstack-meeting15:49
*** alexpilotti has quit IRC15:49
*** diogogmt has quit IRC15:51
*** patelna has joined #openstack-meeting15:51
*** Sukhdev has quit IRC15:52
*** zhiyan has joined #openstack-meeting15:53
*** diogogmt has joined #openstack-meeting15:53
*** vincent_hou has joined #openstack-meeting15:54
*** pschaef_t has joined #openstack-meeting15:56
*** colinmcnamara has quit IRC15:57
*** vijendar has joined #openstack-meeting15:57
*** colinmcnamara has joined #openstack-meeting15:58
*** bswartz has joined #openstack-meeting15:58
*** joel-coffman has joined #openstack-meeting15:59
*** winston-1 has joined #openstack-meeting15:59
*** thingee_ has joined #openstack-meeting15:59
*** avishay has joined #openstack-meeting16:00
*** xyang_ has joined #openstack-meeting16:00
*** dontalton has joined #openstack-meeting16:01
winston-1hey, all16:01
YorikSarHi16:01
xyang_hi16:01
avishayhi16:01
*** mdomsch has joined #openstack-meeting16:01
kmartinhello16:01
*** changbl has joined #openstack-meeting16:02
*** jasondotstar has quit IRC16:04
*** danwent has quit IRC16:04
jgriffith#startmeeting openstack16:04
openstackMeeting started Wed Jul 24 16:04:41 2013 UTC.  The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot.16:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:04
*** openstack changes topic to " (Meeting topic: openstack)"16:04
openstackThe meeting name has been set to 'openstack'16:04
jgriffith#endmeeting16:04
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"16:04
openstackMeeting ended Wed Jul 24 16:04:50 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:04
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack/2013/openstack.2013-07-24-16.04.html16:04
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack/2013/openstack.2013-07-24-16.04.txt16:04
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack/2013/openstack.2013-07-24-16.04.log.html16:04
jgriffith#startmeeting cinder16:04
openstackMeeting started Wed Jul 24 16:04:59 2013 UTC.  The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot.16:05
*** alexb_ has joined #openstack-meeting16:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:05
*** openstack changes topic to " (Meeting topic: cinder)"16:05
openstackThe meeting name has been set to 'cinder'16:05
jgriffithgeesh!16:05
thingee_o/16:05
avishay:)16:05
winston-1\o16:05
eharneyhi16:05
jgriffithOk... hey everyone16:05
JM1hi16:05
zhiyanhi16:05
* bswartz is not on a plane or a train16:05
xyang_hi16:05
kmartinhello16:05
jgriffithSo to start I have a request....16:05
*** danwent has joined #openstack-meeting16:05
DuncanT-Hey16:05
*** jasondotstar has joined #openstack-meeting16:05
*** dkranz has quit IRC16:05
jgriffithI've updated the meetings wiki to include an *ask* that if you post a topic also please put your name or irc nick so we know who the interested party is :)16:05
*** kartikaditya has joined #openstack-meeting16:06
jgriffithso on that note, is the owner of topic 1 around?16:06
*** alexpilotti has joined #openstack-meeting16:06
jgriffithok16:07
*** mkerrin has joined #openstack-meeting16:07
jgriffithonward16:07
avishay(1. optional iscsi support for non-iscsi drivers)16:07
*** zehicle_at_dell has quit IRC16:07
winston-1dosboy here?16:07
winston-1dosaboy: ping16:07
jgriffithOk... we'll circle back16:07
jgriffiththe VMWare topic?16:07
jgriffithkartikaditya: that you?16:08
*** ollie1 has joined #openstack-meeting16:08
kartikadityaYep I for the vmware plugin16:08
kartikadityabut I am workign on the code so nothing much to ask16:08
jgriffithkartikaditya: cool16:08
kartikadityajgriffith: Removed the topic, since work is in progress16:08
jgriffithso more of  a heads up16:08
jgriffith:)16:09
jgriffithkartikaditya: looking forward to seeing it16:09
DuncanT-dosaboy is on his way16:09
kartikadityajgriffith: Yep, having an internal round before sending it out16:09
jgriffithsnapshotting generic block dev?16:09
dosaboyi'm here16:09
YorikSarHere16:09
jgriffithanybody here for that?16:09
jgriffithOk...16:09
dosaboysorry was in another meeting16:09
jgriffithYorikSar: let's start with you16:09
jgriffith#topic generic block dev driver snapshot support16:10
*** openstack changes topic to "generic block dev driver snapshot support (Meeting topic: cinder)"16:10
YorikSarThe problem is that we have snapshotting in minimum requirements but it's not feasible to implement it for generic block device driver.16:10
* thingee_ added driver dev doc to agenda16:10
*** thingee_ is now known as thingee16:10
YorikSarSo we should either agree on exception for this driver or... smth else16:10
*** ndipanov is now known as ndipanov_gone16:11
jgriffithYorikSar: I'm not convinced we can't come up with something on this16:11
dosaboywinston-1: wassup?16:11
*** galstrom_zzz is now known as galstrom16:11
*** slavayssiere has quit IRC16:11
winston-1dosaboy: i guess you were the owner of today's topic 1?16:11
jgriffithYorikSar: however I think the use cases for the local disk one would warrant an exception16:12
YorikSarjgriffith: Yes.16:12
jgriffithYorikSar: do you have a proposal of some sort?16:12
*** Serge_ has joined #openstack-meeting16:12
YorikSarIt came from Savanna and they don't need snapshotting. They don't care if it's lost or corrupted - Hadoop will just forget about that node and move on.16:13
dosaboywinston-1: i did not add that but it is my bp16:13
*** marun has joined #openstack-meeting16:13
bswartzYorikSar: that sounds like ephemeral storage -- similar to what nova does16:13
YorikSarSo I don't see if some generic snapshotting mechanism should be sone here.16:13
jgriffithYorikSar: yeah  TBH it's been low on my list anyway16:14
avishaybswartz: it uses a full disk partition as a volume16:14
YorikSarbswartz: They need block devices not occupied by other IO. They need all iops they can get for HDFS16:14
jgriffithYorikSar: I did want to change the patch the last time I looked though16:14
winston-1YorikSar: so it's hadoop block device driver instead of generic ?16:14
jgriffithYorikSar: IIRC it's currently using an entire disk and I proposed it should do partitions16:15
* thingee is switching to bus, bbl16:15
jgriffithbut anyway... that's an entire different conversation16:15
YorikSarwinston-1: No, it's generic. Hadoop and Savannah are just the first usecases for it.16:15
jgriffithspeaking of this and thingee16:15
jgriffithhttps://review.openstack.org/#/c/38383/16:15
jgriffithWe've put min driver requirements in the docs now :)16:15
eharneycan you not pass in partitions as the available_devices?16:15
YorikSarjgriffith: I'm not sure if Nova can attach multiple HDs to one instance the way Savanna wants it.16:16
winston-1YorikSar: if it's generic, maybe snpashot is needed for other use cases.16:16
YorikSarwinston-1: Yes, but I don't see any generic way to do snapshots in this case.16:17
avishayis implementing snapshots using 'dd' useful to anyone?16:17
eharneyavishay: that would just result in offline clones here, right?16:17
avishayeharney: yes.  i personally don't think it's useful, but maybe others disagree.  i can't think of any other solution off-hand.16:18
zhiyanYorikSar: dm-snapshot?16:18
eharneyavishay: well it already has clone support so i'm not sure i see the value..16:18
*** CaptTofu has joined #openstack-meeting16:18
YorikSaravishay: I don't believe it will. Since we'll have to either use one more HD for 'snapshot' that won't be consistent...16:18
*** maurosr- is now known as maurosr16:18
*** dkranz has joined #openstack-meeting16:18
avishayblock device driver has another limitation here that it can't set sizes, so it will need to snapshot to a partition of >= size16:19
dosaboywinston-1: i did add that agenda item ;)16:19
med_wiki history rarely lies...16:19
*** gyee has joined #openstack-meeting16:19
avishayeharney: agreed16:20
*** MarkAtwood has quit IRC16:20
YorikSarWe can (almost) alias snapshot and clone just to make that check in the list of drivers...16:20
JM1is there a clear definition of clones somewhere?16:21
jgriffithJM1: yeah16:21
jgriffithJM1: an independent copy of a volume that is a new volume16:21
JM1ok16:21
eharneyjgriffith: a note on that...16:21
dosaboyjgriffith: what are ramifications on min driver reqs?16:21
jgriffitheharney: haha16:21
eharneyi haven't seen it specified whether offline only counts or if minimum is to support online16:22
dosaboy...if drivers do not meet min16:22
*** jeblair_ is now known as jeblair16:22
jgriffithlet's have a topic on that so as not to get confused :)16:22
jgriffith#topic min driver reqs16:22
*** openstack changes topic to "min driver reqs (Meeting topic: cinder)"16:22
YorikSarBut what's the decision on block device driver?16:22
*** nati_ueno has quit IRC16:22
jgriffithYorikSar: TBH I'm not overly concerned about it right now and it may be a sepcial case exception16:22
JM1for a driver that has no specific support, snapshots and clones are just copies, and can be slow, right?16:23
YorikSarjgriffith: ok16:23
jgriffithYorikSar: I have no problem with it being an exception as it's not a "voume" device per say16:23
jgriffithYorikSar: it's just raw disk16:23
YorikSarJM1: yes16:23
jgriffithYorikSar: but if that becomes an excuse or a problem we'll have to change it16:23
JM1YorikSar: ok :)16:23
kmartindosaboy: thingee will send you an email with the missing feature(s) and the driver is at risk of being pulled out of cinder16:23
jgriffithYorikSar: and as silly as it might seem we'll just use the clone16:23
jgriffithie the clone coe16:24
jgriffithcode16:24
YorikSarjgriffith: Ok, great.16:24
jgriffithas we've all said before we don't care how it's implemented just so that the expected behavior is achieved16:24
jgriffithSo... back to min driver reqas16:25
jgriffithrequirements16:25
*** jungleboyj has joined #openstack-meeting16:25
jgriffithgeesh... can't type this am16:25
dosaboykmartin: sheesh16:25
dosaboyso, current topic?16:25
dosaboyi guess it has been answered16:26
jgriffithdosaboy: min drier reqs16:26
jgriffithdriver!!16:26
jgriffithbahhh16:26
eharneyso... offline or online clone is required?16:26
* jgriffith is going to give up16:26
jgriffitheharney: I don't really know what that distinction means16:26
dosaboyjgriffith: deep breath, shot of espresso16:26
jgriffitheharney: sorry... could you explain?16:26
jgriffithdosaboy: ahhh... that's it, no coffee yet :)16:26
eharneyyeah, and this will kidn of segue into my current work which maybe should be another topic16:27
avishayi guess online means instantaneous crash-consistent snapshot, which is not required?16:27
eharneyso a driver like generic block dev driver (or gluster) can easily do offline clones just by dd'ing data around16:27
jgriffitheharney: ahhh... got ya16:27
*** alexb_ has quit IRC16:27
eharneybut it falls down w/o snapshot capabilities for online clones16:27
* med_ walks a new keyboard and coffee over to jgriffith16:28
jgriffithso the problem is that say you have two volumes on a multi-backend system16:28
DuncanT-I'd suggest online snapshots need not be in the minimum spec16:28
eharney(i'd like to go over gluster work a bit once we decide we're done w/ the current topic)16:28
jgriffithboth vols are in-use16:28
jgriffith"cinder create-snapshot vol-1" succeeds16:29
jgriffith"cinder create-snapshot vol-2" fails because it's in-use16:29
jgriffithfrom a user perspective that sucks16:29
jgriffithDuncanT-: wow... really?16:29
*** slavayssiere has joined #openstack-meeting16:30
bswartzjgriffith, what if it didn't fail, it just make a snapshot that was non crash consistent?16:30
avishayagreed, as long as the user doesn't pass the -force flag and gets a useless snapshot - we need to make sure that's documented well16:30
*** hemnafk is now known as hemna16:30
DuncanT-jgriffith: I'm not that bothered TBH16:30
jgriffithbswartz: that seems fine to me16:30
eharneywhy would you want a non crash-consistent snapshot?16:30
jgriffithDuncanT-: TBH me neither :)16:31
* thingee is back16:31
JM1eharney: I don't see how it would be useful either16:31
avishaythat's not too fine for me, but it's with the -force flag today...i think we need to find a way to fix this long-term16:31
bswartzeharney, you might be able to arrange on the guest VM for all the I/O to that block device to be quiesced16:31
jgriffitheharney: JM1 the only thing that might be useful is that it's implemented16:31
jgriffitheharney: JM1 meaning consistency in the API16:31
JM1bswartz: well then what your are doing is an offline snapshot16:32
bswartzyeah but from cinder's perspective it's online16:32
DuncanT-jgriffith: Unless you're using an instantanious snapshot, the sematics are a bit useless anyway16:32
*** kiall has joined #openstack-meeting16:32
thingeekmartin: emails for drivers missing some features have been sent16:32
jgriffithDuncanT-: don't necessarily disagree16:32
thingeeI also sent an email to the openstack dev ML16:32
YorikSarthingee: I have one question about it, btw16:33
jgriffithDuncanT-: sadly I thought much of this sort of discussion was behind us16:33
jgriffithsadly it seems it is not16:33
*** alexb_ has joined #openstack-meeting16:33
avishayI think we all agree that dd'ing an attached volume is useless, but i don't see us solving that for havana16:33
thingeeYorikSar: sure16:33
*** rongze1 has quit IRC16:33
DuncanT-jgriffith: I suspect it will pop up at least once per release16:33
*** garyk has quit IRC16:33
jgriffithDuncanT-: indeed16:33
kmartinthingee: yep, I got mine :) A question was raised regarding what would happen if a driver did not meet the min driver features16:33
YorikSarthingee: I can't actively support Nexenta driver now. So we've forwarded your email to Nexenta people.16:33
eharneythingee: so... who is on the hook for the NFS driver?16:34
YorikSarthingee: What whould happen if they can't provide missing features?16:34
avishaykmartin: it will be shot from a cannon :)16:34
*** koolhead17 has quit IRC16:34
jgriffithOk, this is less than productive16:34
jgriffithwe're reviewing previous discussions16:34
thingeeYorikSar, kmartin: so far, it has been agreed the driver wouldn't be in the release that's missing it's minimum features.16:35
DuncanT-YorikSar: Potentially the driver would be removed before the final cut16:35
dosaboythingee: so exisiting drivers could be pulled from H?16:35
YorikSarthingee, DuncanT-: thanks. I'll rush them then.16:35
thingeethere has been positive responses from driver maintainers so far on getting these requirements fulfilled in time, which was my main concern16:35
bswartzeharney, thingee: if there are issues w/ the NFS driver send the nastygrams to me16:36
DuncanT-dosaboy: Yes. See old minutes16:36
eharneybswartz: well.  i have some plans i'm scheming up for it w/ my current work.  lemme go over that in a minute16:36
YorikSarI probably can find some people who were doing NFS driver as well...16:36
*** yjiang5 has quit IRC16:36
jgriffithdo we need to keep on this topic or should we move along?16:37
DuncanT-Move along16:37
*** SumitNaiksatam has quit IRC16:38
*** dkranz has quit IRC16:38
thingeeI say move along. this can be discussed anytime with core on #openstack-cinder16:38
winston-1yeah, what's next?16:38
jgriffithkk16:38
dosaboyshall I do my original topic?16:38
dosaboyoptional iscsi?16:38
*** sarob has joined #openstack-meeting16:38
jgriffith#topic optional iscsi-support for non-iscsi drivers16:38
*** openstack changes topic to "optional iscsi-support for non-iscsi drivers (Meeting topic: cinder)"16:38
jgriffithdosaboy: k16:38
dosaboyyay16:38
dosaboyok so this was already discussed soemwhat after last meeting16:39
dosaboybasically the idea16:39
dosaboy(not heavily thought through yet)16:39
dosaboyis to add otpional iscsi support to non-iscsi drivers16:39
dosaboye.g. rbd driver16:39
dosaboyor gluster16:39
avishaynon-iscsi == file system , right?16:39
dosaboyso that hpervisors that do not support those protocols natively16:40
*** vincent_hou has quit IRC16:40
dosaboycan still use those backends16:40
winston-1avishay: not really16:40
dosaboyavishay: it is simple to allow e.g. rbd drive to export rbd as iscsi volume16:40
jdurgin1avishay: no, e.g. rbd and sheepdog use their own protocols16:40
dosaboyso yeah this would apply to, off the top of my head16:41
jgriffithdosaboy: so an optional iscsi wrapper around non-iscsi drivers16:41
dosaboyrbd, gluster,16:41
dosaboyexcato16:41
jgriffithdosaboy: is something I think we've talked about over the years16:41
dosaboyexacto16:41
zhiyandosaboy: i agree with you to give iscsi-support to those drivers for maximum compatibility for hypervisors, but for long term, i think adding native driver in nova side for non-libvirt hypervisors will be better.16:41
jgriffithdosaboy: that was actually a recommendation for doing Fibre Channel at one point :)16:41
dosaboyit would not necessarily be performant16:41
eharneyso cinder would end up in the data path between a remote storage node and a remote compute node, serving iSCSI?16:41
jgriffithdosaboy: so FC to a cinder node and export as iSCSI16:41
jgriffithfolks hated me for suggesting it IIRC16:42
*** Tross has quit IRC16:42
dosaboyjgriffith: yep thats one possible option16:42
avishayinteresting16:42
dosaboyidea is to make it as generic as possible16:42
dosaboyso e.g.16:42
dosaboynova now suppirts vware hv16:42
dosaboybut vmdk suppoprt it not there yet16:43
dosaboyso for the interim, an iscsi option could be provided fro non-iscsi backends16:43
* med_ walks a new keyboard and coffee over the atlantic to dosaboy too16:43
*** Tross has joined #openstack-meeting16:43
hemnahuh16:43
hemnamount an FC volume and export it as iSCSI ?16:43
hemnathat's interesting16:43
winston-1anything can be officially supported by tgt/iet that comes from ubuntu/RHEL/CentOS/Fedora is fine16:43
avishaydosaboy: will this code go into hemna's brick work?16:44
jgriffithlet's not get distracted16:44
hemna:P16:44
jgriffithdosaboy:  think you have something pretty specific in mind16:44
guitarzandosaboy: what is generic about it?16:44
dosaboyit would be a generic option for all non-iscsi drivers16:44
*** gokrokve has joined #openstack-meeting16:44
dosaboyi'm taking rbd as example16:44
dosaboybut there are others of course16:45
*** gongysh has quit IRC16:45
*** Haitao_ has joined #openstack-meeting16:45
*** SergeyLukjanov has quit IRC16:45
jgriffithdosaboy: so IMO this i smore a call for jdurgin1 and folks that have to support RBD16:45
med_ie, make iscsi an even playing field ...16:45
med_(for any hypervisor, any storage)16:45
dosaboyjgriffith: there are 2 options here16:45
dosaboy1. implement this for rbd driver only16:45
jgriffithdosaboy: I mean, personally like I said this was something I thought would be an option a while back16:45
dosaboy2. implement this as more common option for anyone who wants to use it16:46
dosaboyit is easy enough to implement for rbd since tgt now has native support16:46
jdurgin1jgriffith: I'm fine with it as long as it's clear that it's not meant to be the best for performance or HA. I agree with zhiyan that it's a short term solution16:46
DuncanT-If you can get a common version working, sees daft to do it any other way16:46
zhiyanmed_: IMO iscsi can give maximum compatibility for consumer side, but I don't think it's a good enough idea. adding native driver to hypervisor will be better.16:46
*** stevemar has joined #openstack-meeting16:46
*** koolhead17 has joined #openstack-meeting16:46
*** koolhead17 has joined #openstack-meeting16:46
avishaydosaboy: instead of doing rbd only, maybe add it to brick which can already connect, and then export brick connections?16:46
*** sarob has quit IRC16:47
winston-1i prefer 2. otherwise, that code will have to heavily refactored to work with others16:47
dosaboyavishay: yep, i need to familiarise myself with brick stuff tbh16:47
*** sarob has joined #openstack-meeting16:47
thingee+1 we'll have copypasta later I'm sure16:47
*** darksinclair has joined #openstack-meeting16:47
jgriffithdosaboy: sounds cool16:47
jgriffithdosaboy: I've done it in our lab with FC to iscsi to openstack16:48
jgriffithdosaboy: it's a descent model IMO16:48
med_where is "brick" documented avishay16:48
bswartzjgriffith: what kind of performance did you see?16:48
jgriffithdosaboy: agree with jdurgin1 though that we need to point out it may not be the ideal option16:48
*** kevinconway has quit IRC16:48
dosaboyjgriffith: totally agree16:48
avishaymed_: i'm not sure the specific code i'm talking about is documented16:48
jgriffithbswartz: wasn't too far off from what FC throughputs were16:48
med_avishay, nod, that's kind of what I thought.16:49
thingeeavishay: It's not...yet :)16:49
dosaboyit is just to sort out people using hypervisors that don't yet pair up16:49
winston-1bswartz: bad per my experience on sheepdog16:49
jgriffithbswartz: in most cases it was the same, but I needed some tweaking16:49
avishaythingee: :)16:49
*** kevinconway has joined #openstack-meeting16:49
jgriffithbswartz: and I was using a dedicated 10G network for iSCSI data16:49
dosaboyok i'll try to get a POC done16:49
jgriffithOk... anything else?16:50
*** gokrokve has quit IRC16:50
dosaboynot from me16:50
thingee10 min warning16:50
eharneyi'd like to touch on assisted snaps for a minute16:50
jgriffiththingee: :) I'm actaully going to try and wrap early16:50
jgriffith#topic assisted snaps16:50
*** openstack changes topic to "assisted snaps (Meeting topic: cinder)"16:50
jgriffitheharney: have at it16:50
eharneyso i posted the cinder side of this work16:51
eharneyhttps://review.openstack.org/#/q/topic:bp/qemu-assisted-snapshots,n,z16:51
eharneythis is about supporting snapshots for drivers like GlusterFS that don't have storage backend snapshot support16:51
eharneysnapshotting is done via qcow2 files on the file system, and is handled by Cinder in the online case and Nova (coordinating with Cinder) in the online case16:51
*** dkranz has joined #openstack-meeting16:51
DuncanT-eharney: I've not read the code, but how does cinder ask nova to do the assistance?16:52
JM1eharney: maybe you mean "by cinder in the offline case" ?16:52
eharneyDuncanT-: currently, the snapshot process is initiated by Nova16:52
DuncanT-eharney: So this isn't a normal cinder snapshot-create --force??16:53
eharneyDuncanT-: there will be follow-up to hava Cinder initiate Nova's snapshotting since this is required to do a live snap for online clone16:53
*** dontalton has quit IRC16:53
eharneyno16:53
eharneywhen the volume is attached, Nova/libvirt will quiesce and create a snapshot via libvirt/qemu16:53
winston-1eharney: that nova initiated snapshot sounds like instance-snapshot instead of volume snapshot?16:53
eharneythis is coordinated with cinder by creating a snapshot record w/o calling the driver snapshot code16:54
eharneyJM1: not attached16:54
JM1eharney: ok16:54
*** ZhangChao has joined #openstack-meeting16:54
eharneywinston-1: no, it is volume snapshots, but you get features like a) VM is snapped so all volume snapshots are at the same time b) VM is quiesced16:55
jgriffithwinston-1: +116:55
*** stevemar2 has joined #openstack-meeting16:55
eharneynot sure i follow16:56
winston-1eharney: curious how does cinder notify nova to quiesces all IO on that volume16:56
eharneywinston-1: currently, Nova initiates the snapshot process and calls cinderclient to create the snaps16:56
eharneywinston-1: in the future Cinder will need to be able to call into Nova via a new API16:56
eharneysince we need cinder to notify nova for cases like cinder volume clone16:56
winston-1eharney: no, volume snapshot is initiated by cinder16:56
jgriffitheharney: so I have an off question I'd like to ask folks here16:56
*** SumitNaiksatam has joined #openstack-meeting16:57
jgriffitheharney: this is really something specific to Gluster and possibly NFS shared/fs systems no?16:57
DuncanT-winston-1: I think he's doing it the other way as a PoC16:57
eharneyDuncanT-: right16:57
eharneyjgriffith: it's specific to remote file systems that you mount16:57
eharneyjgriffith: so, i'm starting on gluster16:57
*** Guest43078 is now known as Vivek16:57
eharneybut this should be ported to the NFS driver and other similar ones as well16:58
*** Vivek has quit IRC16:58
*** Vivek has joined #openstack-meeting16:58
bswartzjgriffith: VMware/VMFS too perhaps16:58
*** stevemar has quit IRC16:58
jgriffitheharney: so...16:58
eharneywhich is why i was asking earlier who we think is on the hook for NFS minimum feature reqs16:58
jgriffithbswartz: what's the deal with shares project?16:58
bswartzjgriffith: we're still working on launching it16:58
jgriffithsighh16:58
bswartzwe haven't been able to choose a name yet and that's blocking some things16:59
jgriffithhaha!16:59
jgriffithbswartz: are you guys working with anybody else on this16:59
hemna:)16:59
thingeebswartz: caring - sharing is caring16:59
jgriffithbswartz: ie like eharney ?16:59
bswartzright now it's mostly RedHat and NetApp16:59
eharneyi'd like for anyone interested to check out https://review.openstack.org/#/c/38225/ and see if i'm crazy16:59
jgriffiththingee: nice!16:59
JM1and as we all know, naming things is a tough problem in CS16:59
bswartzwe're trying to get IBM involved16:59
jgriffitheharney: sorry... wasn't intending to derail your topic16:59
bswartzonce we have a name we can get a IRC channel and start holding meetings and all those nice things16:59
*** nati_ueno has joined #openstack-meeting16:59
hemnathat's why I usually end up with variable names like 'ass'  for a while.16:59
thingeetime's up17:00
jgriffitheharney: real quick17:00
eharneybut yes it is on my plate to work on shares service w.r.t. gluster support, but i haven't been active on it lately17:00
*** thingee has left #openstack-meeting17:00
jgriffitheharney: so I'm ok with moving forward obviously (we've talked)17:00
jgriffitheharney: but we need to figure something out long term17:00
jgriffitheharney: more and more of these things are going to come up17:00
med_"Sharing is Caring"17:01
jgriffitheharney: for now I say extensions for them are probably fine etc17:01
*** alexb_ has quit IRC17:01
jgriffithok17:01
jgriffithguess we'll end17:01
eharneyjgriffith: nothing about this is gluster-specific really. i think it makes sense for the class of remote-mounted file system drivers17:01
jgriffith#end meeting cinder17:01
eskerthingee:  do you indemnify us from any trademarks you hold on "caring" if we go w/ that?17:01
jgriffitheharney: ohhh... I agree with that17:01
avishaybye all!17:02
jgriffitheharney: I mean shared, not Gluster specfic17:02
jgriffith#endmeeting cinder17:02
winston-1avishay: bye17:02
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"17:02
openstackMeeting ended Wed Jul 24 17:02:14 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-07-24-16.04.html17:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-07-24-16.04.txt17:02
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-07-24-16.04.log.html17:02
*** avishay has left #openstack-meeting17:02
*** bswartz has left #openstack-meeting17:02
VivekNice meeting you all17:02
VivekI am Vivek Cherian17:02
*** bpb has quit IRC17:02
*** jungleboyj has left #openstack-meeting17:02
*** joel-coffman has quit IRC17:02
*** ZhangChao has quit IRC17:02
*** JM1 has left #openstack-meeting17:03
*** pschaef_t has left #openstack-meeting17:03
*** ollie1 has left #openstack-meeting17:03
*** dprince has quit IRC17:04
*** SergeyLukjanov has joined #openstack-meeting17:04
*** winston-1 has left #openstack-meeting17:05
*** kartikaditya has quit IRC17:05
*** sarob has quit IRC17:06
*** shang has quit IRC17:06
*** sarob has joined #openstack-meeting17:06
*** MarkAtwood has joined #openstack-meeting17:08
*** branen_ has joined #openstack-meeting17:09
*** branen has quit IRC17:13
*** lpabon has joined #openstack-meeting17:17
*** shang has joined #openstack-meeting17:19
*** sarob has quit IRC17:21
*** sarob has joined #openstack-meeting17:22
*** Mandell has joined #openstack-meeting17:23
*** garyk has joined #openstack-meeting17:25
*** jdurgin1 has quit IRC17:26
*** zehicle_at_dell has joined #openstack-meeting17:27
*** dprince has joined #openstack-meeting17:27
*** sarob has quit IRC17:28
*** MarkAtwood has quit IRC17:32
*** egallen has quit IRC17:32
*** egallen has joined #openstack-meeting17:33
*** nachi has joined #openstack-meeting17:37
*** markvan has quit IRC17:41
*** jhenner1 has quit IRC17:41
*** jhenner has joined #openstack-meeting17:42
*** boris-42 has joined #openstack-meeting17:45
*** egallen has quit IRC17:46
*** xyang_ has quit IRC17:47
*** Mandell has quit IRC17:47
*** benonsoftware has quit IRC17:48
*** Yada has quit IRC17:48
*** Yada_ has joined #openstack-meeting17:48
*** darksinclair has quit IRC17:50
*** markwash has joined #openstack-meeting17:50
*** jmontemayor has quit IRC17:51
*** YorikSar has quit IRC17:52
*** jhenner has quit IRC17:52
*** Mandell has joined #openstack-meeting17:57
*** jmontemayor has joined #openstack-meeting17:58
*** nachi has quit IRC17:59
*** nati_ueno_2 has joined #openstack-meeting18:00
*** colinmcnamara has quit IRC18:00
*** krtaylor has quit IRC18:01
*** yaguang has quit IRC18:02
*** benonsoftware has joined #openstack-meeting18:06
*** colinmcnamara has joined #openstack-meeting18:07
*** nachi has joined #openstack-meeting18:08
*** nachi_ has joined #openstack-meeting18:08
*** nachi_ has left #openstack-meeting18:09
*** nachi has left #openstack-meeting18:09
*** Yada_ has quit IRC18:11
*** novas0x2a|laptop has quit IRC18:12
*** kebray has quit IRC18:23
*** zehicle_at_dell has quit IRC18:26
*** MarkAtwood has joined #openstack-meeting18:26
*** dcramer_ has joined #openstack-meeting18:28
*** zehicle_at_dell has joined #openstack-meeting18:35
*** nati_ueno_2 has quit IRC18:37
*** sarob has joined #openstack-meeting18:39
*** dcramer_ has quit IRC18:39
*** sarob has quit IRC18:42
*** sarob has joined #openstack-meeting18:42
*** rohit404 has quit IRC18:48
*** novas0x2a|laptop has joined #openstack-meeting18:48
*** peluse has joined #openstack-meeting18:49
*** slavayssiere has quit IRC18:53
*** zaitcev has joined #openstack-meeting18:53
*** sarob has quit IRC18:56
*** sarob has joined #openstack-meeting18:57
*** canadianchris has quit IRC18:58
*** shri2 has joined #openstack-meeting18:58
*** vvechkanov has joined #openstack-meeting18:59
notmynameswift meeting time. anyone here?19:00
* creiht is here but a bit distracted19:00
torgomaticyo19:00
peluseyup19:00
notmynamecreiht: no worries. I'm sitting in the middle of the expo hall at oscon ;-)19:00
notmyname#startmeeting swift19:00
openstackMeeting started Wed Jul 24 19:00:48 2013 UTC.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: swift)"19:00
openstackThe meeting name has been set to 'swift'19:00
davidhadashi19:00
notmynamewelcome19:01
notmynameglad you can make it19:01
notmyname(and I hope there are more here than the 4 that responded)19:01
yuanznotmyname, hi19:01
notmynametopics to discuss this week: https://wiki.openstack.org/wiki/Meetings/Swift19:01
notmyname(not in order)19:01
notmynameso first up, a swift hackathon19:01
* swifterdarrell is here19:02
*** sarob has quit IRC19:02
notmynamesince so many of the swift contributors will not be able to make it to hong kong, we're going to have a swift hackathon in Austin in Octobor19:02
pelusehow's the humidity in Austin in Oct?19:02
notmynamethe purpose is for coding on swift, not for presentations19:02
notmynamepeluse: worse than phoenix :-)19:02
pelusewell, I guess we'll make it anyway :)19:03
portantehere19:03
notmynameit will be pretty small (~30 people total)19:03
*** egallen has joined #openstack-meeting19:03
creihtOctober is usually pretty nice in Texas19:03
* portante scrounges around to find a big texas hat19:04
notmynameI'll have a public link and invite for the next meeting. I wanted to let people know it's coming though :-)19:04
* creiht doesn't have a big texas hat19:04
notmynameI'm also hoping that since it's in austin, several (all?) of the rax contributors will be able to make it19:04
* portante found my wife's 40th birthday pink texas hat, puts it back right away ...19:04
notmynamesince they don't like going to openstack summits ;-)19:04
notmynameportante: yikes19:04
*** cschwede has joined #openstack-meeting19:05
notmynameswiftstack will be sponsoring it. we'll provide a place, some tables, whiteboards, wifi, and some food.19:05
* creiht can make no promises ;)19:05
portantewill you have specific coding topics?19:05
torgomaticto be fair, the annoyance of travel is super-linear in the duration of the journey19:05
notmynameportante: "make swift better" :-)19:06
*** sushils has quit IRC19:06
*** zhiyan has left #openstack-meeting19:06
notmynameok, moving on19:06
swifterdarrellnotmyname: portante: presumably tasks which require/benefit from collaboration would be ideal19:06
peluseI've not been to one of these things, what are the basic logistics (duration, agenda, etc) or you can just cover that in the invite if you're ready to move on to the next topic19:06
notmynamepeluse: it'll be covered in an invite19:07
notmyname#topic enable versioned writes19:07
*** openstack changes topic to "enable versioned writes (Meeting topic: swift)"19:07
notmynameEnable versioned writes by default? https://review.openstack.org/#/c/36979/19:07
creihtno19:07
creiht:)19:07
notmynamethis patch was submitted to allow versioned writes to be turned on by default19:07
creihtso my question was why not configure devstack to enable it, if they want to test it?19:07
notmynameI don't care about the devstack question in the patch comments19:07
pelusebrief recap of pros vs cons?19:07
swifterdarrell+1 on not enabling it by default; deployers can turn it on if users want it, right?19:08
notmynamethe larger question was raised about when if ever should a feature be changed to be enabled or disabled19:08
portanteswifterdarrell: agreed19:08
torgomaticI like the idea; I'm not a fan of software that has a bunch of options you have to set in order to get the goodies19:08
notmynamepros: people tend to use defautls19:08
cschwede+1 not on by default19:08
notmynamecons: it's not currently on, so by doing nothing deployers who upgrade will get a new feature19:08
creihtcons: people tend to not read release notes19:08
swifterdarrellthe defaults of the codebase don't (shouldn't) exist to enforce some kind of policy on deployers;  (I guess you could say deployers NOT wanting it could opt out... but I think it's better for existing deployments to be opt-in for changes)19:08
notmynameswifterdarrell: which is exactly why it was disabled to start with19:09
portanteyes, and for this feature, if it ends up miss-used it could use up a lot of storage, right?19:09
notmynameportante: ya19:09
notmyname"could"19:09
portantecould, agreed19:09
peluseI'm not versed on the feature but what siwftdarrell says sure makes sense19:10
zaitcevPresumably owners of large clusters are more careful than that, but having to adjust configs for updates is unpleasnt.19:10
notmynamezaitcev: one would think so ;-)19:10
notmynamezaitcev: maybe creiht doesn't read release notes ;-)19:10
notmynamebut "well they should have read the notes" isn't a good reason19:10
* creiht is just observing human nature19:11
swifterdarrellIf defaults aren't meant to be used, then don't have them--require every setting to have a specified value.  If defaults ARE meant to be used, don't change them on deployers19:11
* notmyname is just teasing creiht19:11
swifterdarrellHow hard is that?19:11
davidhadasI think it would make sense to keep this one disabled by default - whoever enables it should know what he is doing19:11
swifterdarrellreallly19:11
*** YorikSar has joined #openstack-meeting19:11
creihtbut then if we decide to do that, we would have to go through and first define what a "default" cluster should be first19:11
* portante still fascinated by a pink texas hat ...19:11
creiht:)19:11
cschwededavidhadas: exactly!19:11
zaitcevDefault cluster is RAX19:11
notmynamecreiht: don't you mean your "evil chuck" face?19:11
zaitcevOr even "Historic CF"19:12
notmynamezaitcev: I hope not19:12
*** redbo has joined #openstack-meeting19:12
*** dfg has joined #openstack-meeting19:12
*** tsg has joined #openstack-meeting19:12
notmynamedfg: redbo: any opinion on enabling versioned writes by default?19:12
redboNo real opinion.  We run with it on already.19:13
*** gholt has joined #openstack-meeting19:14
notmynameok19:14
notmynamethanks19:14
dfgum- i think we run it. why would that feature be on and non of the others? except dlobjects i guess19:14
dfgi think both of those would be better as middleware though19:14
dfgbut no strong opinions19:14
dfgis there a reason for it?19:15
dfgto be on by default?19:15
notmynamedfg: that people use defaults, and turning it on means that more people will use it. the question was raised in a patch19:15
torgomaticdoes anyone know if it's on in the sample configs?19:15
notmynametorgomatic: the samples reflect the defaults19:16
dfgif they want to start using it wouldn't they jsut turn it on?19:16
creihtthe sample configs should all have the defaults as examples19:16
swifterdarrell#link https://review.openstack.org/#/c/36979/119:16
creihtI think it is a lot safer for a deployer to find out they don't have a feature deployed, but they can just enable it19:17
dfgcan we vote as to whether obj versioning and dynamic large object should be yanked out of the proxy server and made middleware? the proxy server code is really complicated and that would help clen it up some19:17
dfgs/some/a lot19:17
creihtrather than for a deployer that knows they don't have it enabled, suddenly have it enabled19:17
notmynamedfg: I think that vote comes as the review on the patch to do it :-)19:17
swifterdarrellcreiht: ++19:17
notmynamedfg: but I'd support that19:17
davidhadasnotmyname: more pepole will be facing capacity problems by this without undertsanding why putting same objects again and agin eats up capacity.19:18
notmynamecreiht: ya, which is why I originally marked it as -1.19:18
dfgnot really- it would inform this decision. making obj versioning on by default makes splitting it out a bigger change19:18
notmynamedfg: middleware isn't a feature flag, though (although it can kinda be used for that)19:19
*** MarkAtwood has quit IRC19:19
notmynamedfg: but it seems that the question goes away since most of us are leaning to not enabling it19:19
dfgok19:19
notmynameok, thanks for that19:20
creihtchanging config defaults shouldn't happen, except for a very good reason19:20
notmyname#topic json19:20
notmynameGet rid of simplejson and use stdlib json? Apparently the APIs are slightly different; see https://gist.github.com/smerritt/6066977 and https://review.openstack.org/38014 for details.19:20
*** openstack changes topic to "json (Meeting topic: swift)"19:20
notmynametorgomatic: ^19:20
creihtno19:20
creiht:)19:20
creihtshort story is: the built in json never got the c speedups that are in simplejson19:20
torgomaticsimplejson doesn't work with PyPy19:20
portantecreiht: we want pypy19:20
gholtCan't we support both? I thought we had been all this time?19:21
creihtso I don't think the answer is to make cpython use the slower library19:21
portanteis the json stuff on the common path?19:21
portantedo we really need them?19:21
torgomaticgholt: kind of?19:21
torgomaticall the tests run against simplejson all the time19:21
creihtseems like there should be a better way to fix it19:21
dfgya- i like keeping simplejson too19:22
portantebut what about the majority of requests that swift handle?19:22
torgomaticalso, I don't like simplejson's api19:22
creihttorgomatic: wait, what?  json *is* and older version of simplejson19:22
dfgseems like a lot of cost for a small gain19:22
torgomaticsometimes you get str, sometimes you get unicode... hope your code is okay with both types19:22
creihtoh that part19:22
torgomaticcreiht: they diverged, unfortunately19:22
portanteif we need simplejson for performance, worth the discussion, but if we keep pypy out because of simplejson, we are dropping potential performance improvements on the floor19:23
torgomaticat least stdlib json gives you the same type all the time19:23
torgomaticotherwise you get bugs where something 500s when a param is non-ASCII UTF-819:23
creihtor we could fix simplejson if it is an issue?19:23
gholtcreiht: By recompiling the C code? ;)19:23
redboI think we should use ujson19:24
creihtlol19:24
*** spzala has quit IRC19:24
* portante bites, googles ujson19:24
*** jmontemayor has quit IRC19:25
swifterdarrellwould an API adapter in swift which presents a common API w/either stdlib or simplejson under the hood be too crazy?19:25
portantedoes ujson work with pypy?19:25
dfglets do what we always do- write our own json parser !!19:25
redbono idea, I just wanted to be different19:25
torgomaticswifterdarrell: it might work, but only if that adapter doesn't make things slower than just using stdlib json19:25
dfg:)19:25
redboswifterdarrell: that seems like the way to go19:26
swifterdarrelltorgomatic: you would avoid, for instance, looking at all the data and making sure it's Unicode for consistency19:26
dfgswifterdarrell: +1 i'd think it wouldn't be too hard to do right?19:26
swifterdarrelltorgomatic: that's API ugliness, but I'd make that trade-off for speed (or, rather, keep making it)19:27
portanteseems like extra work for what kind of performance gain for cpython?19:27
creihtswifterdarrell: isn't there something like that in oslo? :)19:27
swifterdarrelllololol19:27
creihtor how about we help patch simplejson to fix api issues19:28
gholtIf the performance sucks that bad for us, I guess we can maintain a fork. But I totally do NOT want to do that.19:28
creihtthen we can run with either simplejson or json as is19:28
*** topol has quit IRC19:28
torgomaticcreiht: you think the simplejson guys will take API-changing patches? seems like that could hose their users pretty effectively19:28
torgomaticbut then, I don't know if they're sticklers for that sort of thing19:29
swifterdarrellportante: Good question... but who's going to spend the time collecting solid numbers?  the folks who want to keep what we have or the folks who want to make it some unknown amount slower?19:29
creihttorgomatic: if it makes it the same as json? not sure how that would be bad19:29
creihtit doesn't hurt to try19:29
*** sarob has joined #openstack-meeting19:29
creihtand seems like the least sucky if you can19:29
torgomaticcreiht: ask the guy getting errors when running w/stdlib json under pypy :)19:29
zaitcevLook at Alex' patch, Chuck. It's not something you can patch. The problem is that they have gone to the approved Python 3 model of handing strings. Once there nobody's going back and they'll continue returning unicode strings.19:29
dfghas anybody shown that pypy would really even be that much faster?19:29
creihttorgomatic: not my problem, everything works for me :)19:29
notmynameseems like a bad attitude to have19:30
creihtI think running pypy with swift is neat, it doesn't warrent bending over backwards (at the cost of the normal implementation) to fix19:30
dfgcreiht: +119:30
creihtzaitcev: ahh that's a completly different issue then19:30
dfglike- don't we have bigger fish to fry?19:31
torgomaticalso, we've got code in utils that imports simplejson, then falls back to json19:31
torgomaticif we're not going to work with stdlib json, let's rip that bit out19:31
portanteare we concerned with json parsing or generating speed?19:31
torgomatic"uses A or B except that it crashes with B" is crappy19:31
*** epim has joined #openstack-meeting19:31
notmynametorgomatic: +1 that's bad19:32
creihttorgomatic: that was done a long time ago (likely when the json api and simplejson api probably didn't diverge)19:32
notmynamecreiht: so the question is do we rip out json?19:32
torgomaticcreiht: I'19:32
torgomaticm sure it was fine when it was done, but it rotted19:32
*** zehicle_at_dell has quit IRC19:32
creihtI'm just providing context19:32
torgomaticsure19:33
notmynameportante: from what I see the issue is the it breaks with json right now19:33
portantebut we can fix that19:33
torgomaticso, if we go with stdlib json, it makes things easier in N years' time when Swift ends up supporting python 3, as I don't think simplejson works w/py319:33
creihtif someone has that itch, let them scratch it :)19:33
creihtfor now, I can't see how we can ditch simplejson19:34
creihttorgomatic: there are going to me *so* many more difficult issues when it comes to supporting python319:34
torgomaticcreiht: absolutely true19:34
torgomaticbut I'd rather not pile on any others if we can help it19:34
notmynameso the options are either patching simplejson or writing an adaptor layer, right? did I miss another one?19:35
*** jmontemayor has joined #openstack-meeting19:35
creihtthat's fine with me as long as it doesn't come at a cost for the current implementation19:35
redbowe'll need to eventually make every string in swift into unicode instead of utf-819:35
redbowell, except where it's dealing with actual file data19:36
*** SumitNaiksatam has quit IRC19:36
*** SumitNaiksatam has joined #openstack-meeting19:37
zaitcevThat's the Python 3 model19:37
torgomaticalright, I'll hack up an adapter layer thing and do some synthetic benchmarks19:37
notmynameok19:38
zaitcevIt breaks down in WSGI so bad, you would've belive19:38
notmynametorgomatic: thanks19:38
notmynamemoving on..19:38
portantetorgomatic: can you also engage Alex_Gaynor to check against pypy speed?19:38
notmyname#topic erasure codes questions19:38
*** openstack changes topic to "erasure codes questions (Meeting topic: swift)"19:38
redboit's not a bad python 2 model either.  the wsgi part isn't that bad, the problem is just how much code we'll have to verify works okay when unicodes start appearing where theere used to be strs.19:38
torgomaticportante: for json stuff? sure, once I have the benchmarks written19:39
portantegreat19:39
portantethx19:39
notmynamesince our last meeting, we've talked more about erasure codes. are there questions that need to be discussed here (rather than just "normal" IRC questions)?19:39
*** colinmcnamara has quit IRC19:39
yuanznotmyname, can we merge this patch(Forklift the DiskFile interface into it's own module) into the EC branch?19:39
notmynameyuanz: ya, I can do that19:40
zaitcevWhy not. As I understand EC does not place unusual demands on DiskFile.19:40
notmynameyuanz: I'll do it as soon as the meeting is done19:40
notmynamezaitcev: the hope is that master will get merged into the ec branch frequently so they don't diverge19:41
zaitcevah, ok19:41
pelusenotmyname:  I was going to about "frequency", weekly?19:41
notmynamepeluse: it's a matter of me pressing a button. I haven't set up a schedule for it. IMo it should be at lest weekly, if not more often19:42
vvechkanovnotmyname: Can I ask about our plans for reduce cross region replication traffic?19:42
notmynamevvechkanov: ya, just a minute19:42
notmynameanything else on ec?19:42
zaitcevEC is fascinating, but as I understand Joe Arnold has already arrayed significant forces against it alread, so I don't feel compelled to help along. It's bound to happen in due time...19:42
*** sarob_ has joined #openstack-meeting19:42
notmynamezaitcev: against?19:43
portantewho is joe arnold and why should we care?19:43
notmynamezaitcev: we're pushing it and writing it :-)19:43
zaitcevYea, I mean like attacking the problem19:43
*** Fdot has joined #openstack-meeting19:43
notmyname#topic open discussion19:43
*** openstack changes topic to "open discussion (Meeting topic: swift)"19:43
notmynamevvechkanov: go ahead19:43
vvechkanovHello all. I have a question about swift replication. I think it is good idea to reduce traffic between regions. For that we can modify replication to prefer replicate in local region, than in foreighn one.19:44
notmynamevvechkanov: like the read and write affinity?19:44
vvechkanovYes.19:44
* portante sheepishly crawls back under his pink texas hat19:44
notmynameseems like it makes sense to me19:45
notmynamevvechkanov: it would depend on the particular patch, I'd think19:45
notmynamevvechkanov: but the point of the replication is to provide the high durability19:45
notmynamehmm...I withdraw my previous statement abotu it making sense19:46
*** salv-orlando has joined #openstack-meeting19:46
notmynameif you are looking at it from a "replicate to the copies in the same region instead of using the WAN link" that makes sense to me19:46
torgomaticseems to me that if you're going to replicate data, you should replicate it to where the proxy will look for it, not to some other place19:46
*** sarob has quit IRC19:46
notmynamekeeping all replicas in a region doesn't19:46
notmynametorgomatic: ya, a 2 region, 3 replica system maybe should prefer to keep the 2 copies on the one region in sync with each other?19:47
*** sarob_ has quit IRC19:47
*** redbo has left #openstack-meeting19:47
notmynamefor the data move (not checks)19:47
dfgshouldn't this be a subject for a different time?19:47
dfglike when i'm not around :)19:47
vvechkanovWe planning to replicate every step in one regions and one in some, for example 10 steps replicate to other regions.19:48
torgomatic./kick dfg problem solved ;)19:48
swifterdarrellheh, there's already enough confusion about what happens to PUTs to one region with write affinity enabled... I can't imagine how bad it'd be with cross-region replication further interfered with..19:48
* swifterdarrell shrugs19:48
notmynamevvechkanov: I don't understand what that means19:48
notmynamevvechkanov: since replication is pushed base and doesn't share state between the nodes, I'm not sure how it would work19:49
*** therve has joined #openstack-meeting19:49
dfgoh- i missed the open-discussion tag. sorry :)19:49
vvechkanovI mean replication in region will be more often then cross-region replication.19:50
zaitcevWhat is Havana schedule?19:50
notmynamezaitcev: october-ish?19:50
ogelbukhnotmyname: filter out nodes from foreign regions in replicator for every run except every 10th19:51
zaitcevI really need to know how aggressive I need to be with DB broker, because if LFS misses Havana, then I'm fired19:51
notmynameogelbukh: ah ok19:51
ogelbukhbasically that's a simpliest(?) approach we could imagine19:51
zaitcevPeter seems good with DiskFile, he's gonna make it by October I'm sure19:51
ogelbukhor may be just easiest19:52
*** Fdot has quit IRC19:52
ogelbukhas in easy vs simple19:52
notmynameogelbukh: sounds like it would work. I'm not sure if it's a good idea or not. I don't think I'd be too comfortable running that way. others may be19:52
zaitcevSimple, but seems asking for tweaking the ratio, which is an extra knob.19:53
swifterdarrellogelbukh: vvechkanov: couldn't you achieve similar results with network-level QoS/shaping on a separate cross-region replication network, possibly with a higher object-replicator concurrency level?19:53
*** colinmcnamara has joined #openstack-meeting19:54
*** jlucci has joined #openstack-meeting19:54
swifterdarrellogelbukh: vvechkanov: I thought the point of the sep. replication network was to allow control of that traffic flow outside of Swift19:54
*** cschwede has quit IRC19:55
ogelbukhswifterdarrell: it was and it still is19:55
*** shardy has joined #openstack-meeting19:55
swifterdarrellsweet! no patch needed19:56
ogelbukh)19:56
notmynameanything else in the last 4 minutes?19:56
swifterdarrellI'll +2 almost any zero-line patch19:56
*** vvechkanov has quit IRC19:57
notmynameif you're looking for reviews, the acount-acls one could use some eyes19:57
notmynamethere's a ton of others too19:57
zaitcevThat one is complex.19:57
notmynamethanks for your time19:57
notmynameya19:58
*** spzala has joined #openstack-meeting19:58
notmyname#endmeeting19:58
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"19:58
openstackMeeting ended Wed Jul 24 19:58:25 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-07-24-19.00.html19:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-07-24-19.00.txt19:58
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-07-24-19.00.log.html19:58
*** zaitcev has left #openstack-meeting19:58
*** timductive has joined #openstack-meeting19:58
*** zaneb has joined #openstack-meeting19:59
*** randallburt has joined #openstack-meeting19:59
*** tspatzier has joined #openstack-meeting20:00
shardy#startmeeting heat20:00
openstackMeeting started Wed Jul 24 20:00:16 2013 UTC.  The chair is shardy. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: heat)"20:00
openstackThe meeting name has been set to 'heat'20:00
shardy#topic rollcall20:00
*** openstack changes topic to "rollcall (Meeting topic: heat)"20:00
zanebo/20:00
stevebakeryop20:00
shardyHi all, who's around :)20:00
*** RightScale-RyanO has joined #openstack-meeting20:00
randallburthi20:00
asalkeldo/20:00
tspatzierHi20:00
timductiveHi20:00
*** spenceratx has joined #openstack-meeting20:01
shardysdake, therve, jpeeler?20:01
therveHi!20:01
stevebakerSpamapS?20:01
shardygood catch stevebaker ;)20:02
shardyOh well, lets make a start20:02
*** peluse has quit IRC20:02
shardy#topic Review last week's actions20:02
*** openstack changes topic to "Review last week's actions (Meeting topic: heat)"20:02
*** leseb has joined #openstack-meeting20:03
shardySo thanks to stevebaker for doing meetings etc while I was away :)20:03
radixoh, heya20:03
jpeeleroh hi20:03
shardy#link http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-07-17-20.00.html20:03
*** topol has joined #openstack-meeting20:03
shardy#info action stevebaker to start mission discussion on list20:03
*** jasond has joined #openstack-meeting20:03
shardystevebaker: did that happen, I didn't spot it but behind on the ML backlog..20:04
stevebakerI have a draft, should we have a quick bikeshed here https://etherpad.openstack.org/heat-mission20:04
shardyI missed the context on this, who's asking for this?20:04
*** stevemar2 has quit IRC20:04
stevebakerthe board, heat is now the OpenStack Orchestration program20:05
topolshort and sweet :-)20:05
*** dfg has left #openstack-meeting20:05
asalkelddo we need to mention templates?20:05
stevebakerall programs need to come up with a mission statement20:05
shardy#link https://etherpad.openstack.org/heat-mission20:05
*** liang has joined #openstack-meeting20:06
zanebstevebaker: orly? can we call ourselves OpenStack(TM) Orchestration now?20:06
*** gholt has left #openstack-meeting20:06
stevebakerwhich I'm interpreting to mean define "what we do", not "what value do we offer"20:06
randallburtadded some small input for clarity, but looks good to me20:06
topolwhy couldnt we before?20:06
stevebakerheat is a project within the OpenStack Orchestration program20:06
asalkeldprogram is what people do, not what they produce20:07
stevebakerI'd like to get something about the lifecycle of applications in there, heat is not just launch and forget20:07
topolI like your mission statement20:07
*** wirehead_ has joined #openstack-meeting20:07
*** marun has quit IRC20:07
randallburtstevebaker:  how about that?20:08
*** marun has joined #openstack-meeting20:08
stevebakermaybe "configuration" is redundant?20:08
topolI like that you explicitly call out configuration. Thats a big deal20:08
radixstevebaker: what does "openstack resources" mean in this context?20:08
asalkeldI think is ok20:09
asalkeldit is20:09
topol+120:09
*** Tross1 has joined #openstack-meeting20:09
stevebakerradix: anything that can be invoked via an openstack API20:09
*** rpothier_ has joined #openstack-meeting20:09
stevebakerthat looks good to me20:10
*** Tross has quit IRC20:10
*** dprince has quit IRC20:10
stevebakerarg20:10
*** zaro has quit IRC20:10
randallburtneeds more commas20:10
*** derekh has quit IRC20:10
shardy"management of applications on those resources" could just be "management of those resources"20:10
stevebaker,,,,,,,,,,,,,,,,,20:10
randallburtthanks ;)20:10
shardysince we're IaaS focussed20:10
radixshardy: different meaning of resources, I think20:10
*** echohead1 has quit IRC20:11
shardyI just want to avoid saying we're an application (PaaS) management solution20:11
radixdoes heat orchestrate openstack, or applications on top of openstack?20:11
shardybut otherwise looks good20:11
randallburtone could argue that "configuration" would include software, but I'm not fussed20:11
shardyradix: depends on your definition of applications I guess20:11
topolradix, Im hoping both20:11
randallburtradix:  if SpamapS and OOO has their way, the answer is "yes"20:12
radixlike when I see "enable the orchestration of OpenStack resources" it seems like that could be misinterpreted as what OOO is20:12
stevebaker"support the..." implies that we can pass off to some other configuration mechanism20:12
radixrandallburt: well, yes, but isn't that a separate program?20:12
*** andrew_plunk has joined #openstack-meeting20:12
therve+1 for sending and ML discussion20:12
shardythe main think is, internally, Heat doesn't care about what you deploy, whereas a PaaS has to, due to e.g versions for the application containers it provides20:12
radix:)20:12
stevebakeryup, shardy want to send it?20:12
randallburtradix:  well, yes. and Heat would just be a means to an end for them.20:12
shardyYeah, lets move on and pick it up on the ML20:13
randallburttherve:  +120:13
radixrandallburt: right, I understand. so we need our program descriptions to be distinct20:13
shardystevebaker: can do, sure20:13
radixyeah, this conversation is getting sprawly20:13
shardy#action shardy to send mission ML statement20:13
stevebakeryay for etherpad though20:13
shardyYeah, thanks stevebaker for getting things rolling20:13
shardy#topic Documentation20:13
*** openstack changes topic to "Documentation (Meeting topic: heat)"20:14
stevebakertoday I will learn how to write a sphinx extension20:14
radixwoo20:14
shardySo I see this is carried over from last meeting - need to get the docs sprint organised20:14
stevebakerfor resource doc generation20:14
shardyAnyone got anything to raise re Docs other than we need to write lots of them very soon? ;)20:15
stevebakershardy: set it for after h-3, since we'll be in some form of feature freeze after that20:15
therveCan we get rid of the docs directory?20:15
*** MarkAtwood has joined #openstack-meeting20:15
annegentleo/20:15
randallburthow is the wadl maintained? is it manual?20:15
shardystevebaker: agree, we've got too much in h3 already20:15
randallburtwe said "docs" too many times ;)20:16
stevebakerrandallburt: I believe so20:16
shardyannegentle: hi20:16
annegentlerandallburt: manual is typical for all the other projects. Neutron had an attempt at automation but the manual way was quicker and more accurate20:16
annegentleheh20:16
asalkeldannegentle, any reason heat is missing from here: http://docs.openstack.org/developer/openstack-projects.html20:16
stevebakerour api is too simple to justify automatic generation20:17
annegentleasalkeld: just patch openstack-manuals/www/developer/index.html20:17
annegentlestevebaker: +120:17
asalkeldok20:17
randallburtannegentle:  cool. figured that was the case. Just wondered if we needed a task to make sure its still accurate and new things were added20:17
shardyIt would be nice if there was some way to automatically generate API docs and resource schema documentation20:17
topolannegentle, I noticed a lot of the architecture pictures have not been updated to have heat and ceilometer20:17
topolas core20:17
stevebakershardy: that is what I am working on today20:17
annegentleshardy: sure would be but then which would be truth? :)20:17
shardyannegentle: If it's generated from code then the docs always match the code, surely?20:18
annegentletopol: I have been thinking about that a lot, and I'm going to send an OpenStack program description for docs to the -dev list today20:18
shardystevebaker: awesome :)20:18
stevebakerzaneb has written api docs, it just needs to be merged into api-site20:18
annegentlein it, I have to draw a line between core and integrated. So I'm not sure how to address things like arch diagrams maintenance and updates.20:18
annegentleshardy: but what if the code is wrong?20:18
zanebsomeone should probably compile them first too ;)20:18
shardyannegentle: auto-generated docs != specification, but yea I see your point20:19
stevebakerzaneb: maybe gating compiles it for you?20:19
shardyall that java stuff is really hideous20:19
zanebstevebaker: let's go with that :)20:19
*** SergeyLukjanov has quit IRC20:20
shardyAnyway, any other docs stuff before we move on?20:20
*** YorikSar has quit IRC20:20
annegentleshardy: thanks for having docs on the agenda!20:20
*** krtaylor has joined #openstack-meeting20:21
shardyannegentle: thanks for pointing us in the right direction, hopefully we'll start making progress after h320:21
shardy#topic h3 blueprint milestone and priority20:21
*** openstack changes topic to "h3 blueprint milestone and priority (Meeting topic: heat)"20:21
annegentleoh one other note, there are changes to the Heat cli docs at https://review.openstack.org/#/c/37328/20:21
annegentlenothing major, but want to point out they are being maintained/freshened20:22
shardy#link https://launchpad.net/heat/+milestone/havana-320:22
radixI am pushing to have a WIP review up for my instance-group refactor today20:22
*** lbragstad has quit IRC20:22
shardyradix: sounds good20:23
shardyso we really have a lot of BPs compared to h1 and h220:23
*** cody-somerville has joined #openstack-meeting20:24
*** lbragstad has joined #openstack-meeting20:24
shardyguess we'll all be busy, but if things are going to slip, best to flag it early and start untargetting them20:24
shardyAnyone have any issues re h3 bp or bugs they want to raise?20:25
randallburtasalkeld, zaneb should we go another round on https://review.openstack.org/#/c/36744/ or can I move on to https://blueprints.launchpad.net/heat/+spec/update-stack-new-resource-state20:25
therveI've been thinking about load balancer lately20:25
therveI wonder if we could squeeze improvements to it in h3?20:25
SpamapSo/20:25
SpamapSsorry lunch went long20:25
shardytherve: I thought we were going to move to the neutron lbaas rather than polishing what we have?20:26
zanebrandallburt: you were going to fix up the Output.* stuff20:26
therveshardy, That's one side of it, yeah. It's not in h3 either, though20:26
randallburt+1 on neutron lbaas over tweaking AWS resource20:26
randallburtzaneb:  oh, yes. I have that in a branch but forgot because I've been out/busy on other stuff. I'll get that submitted before COB today20:27
shardytherve: If people are prepared to work on stuff, and they can realistically deliver it then we can consider putting it in h320:27
therveI've been looking at it, but neutron makes me angry20:27
therveshardy, Cool, thanks20:27
randallburttherve:  lol. indeed20:27
zanebrandallburt: ok, when that is done I think I am happy20:27
stevebakerI'd like something that can be tempest tested. building the image that the nested stack uses is a barrier right now20:27
randallburtzaneb:  roger that, and thanks!20:27
asalkeldrandallburt, I'll work on this too sometime https://review.openstack.org/#/c/38285/20:27
shardythe lbaas stuff I didn't put in havana because I was not really sure if it's mature enough to integrate with yet20:27
randallburtasalkeld:  awesome. I really like the concept there.20:28
SpamapSstevebaker: I believe we will be pushing to host several different images for infra as we move pieces of tripleo into the gate20:28
zanebrandallburt: but quit with the double underscores anyway ;)20:28
therveYeah I don't know about the implementation. The interface ought to be, though20:28
asalkeldwe really need to have a way of marking resources (deprecated, prototype, supported)20:28
randallburtzaneb:  understood ;D20:28
stevebakerSpamapS: can you keep me up to date on that? I'll be getting devstack to generate images as soon as I can package dib20:29
randallburtasalkeld would that be something to do with stevebaker's sphinx extension?20:29
asalkeldnot sure20:29
randallburtor would you want it as something query-able via the api?20:29
randallburtprobably both, I'd assume20:29
asalkeldI think both20:29
stevebakeronce the metadata is there it can be exposed however20:30
therveAs a result of API calls would be even better20:30
asalkeldnice to have a an arg --only-use-production-ready-resources20:30
stevebakerwe need a way of flagging which type is the primary one too, OS::Quantum:: vs OS::Neutron20:30
*** marun has quit IRC20:31
*** zaro has joined #openstack-meeting20:31
randallburtIIRC there are already bps around a "catalog" of resources; cba to remember specifics atm, but might be worth a look20:31
*** marun has joined #openstack-meeting20:31
asalkeld(maybe yet another blueprint)20:31
*** henrynash_ has joined #openstack-meeting20:32
randallburtand probably not h3, yes?20:32
randallburtconsidering the existing backlog and all20:32
asalkeldyea20:32
shardyIMO there are more pressing things to do in h320:32
*** abaron has quit IRC20:33
*** lbragstad has quit IRC20:33
*** henrynash has quit IRC20:33
*** henrynash_ is now known as henrynash20:33
asalkeldeveryone has their own priorities20:33
shardyOk, one last thing, if anyone has too much assigned to them, please unassign yourself, then if people are looking for stuff to do they can pick it up20:33
shardyasalkeld: yea true20:33
randallburtagreed, but I can take an action to groom the bp backlog around this topic if you like20:34
stevebakergroom away!20:34
shardy#action randallburt bp grooming20:34
shardyanything else on h3?20:34
randallburtaround the resource catalog, I mean ;)20:34
shardy#topic #undo20:35
*** openstack changes topic to "#undo (Meeting topic: heat)"20:35
*** dkranz has quit IRC20:35
*** kmartin has quit IRC20:35
shardy#action randallburt resource catalog bp grooming20:35
randallburtthanks ;)20:35
shardy#topic Removal/moving of heat-boto/heat-cfn/heat-watch client tools20:35
*** openstack changes topic to "Removal/moving of heat-boto/heat-cfn/heat-watch client tools (Meeting topic: heat)"20:35
stevebakerso20:35
shardysdake: around?20:36
shardystevebaker: go for it ;)20:36
stevebakerI've submitted that heat-cfnclient be a new repo to house heat-cfn, heat-boto, heat-watch20:36
stevebakerand moved them out of the core repo20:36
asalkeldI think sdake was against putting in a separate project20:37
shardystevebaker: I don't really mind where they live provided they still exist20:37
shardysdake had some strong opinions on the matter yesterday20:37
SpamapSthey're just tools for testing the cfn apis?20:37
jpeelerwhat's the reason to move it?20:37
stevebakermy position is that they should still exist, they should have python releases, but we should encourage distro packages not to package them20:37
shardySpamapS: yep20:37
* SpamapS has never used them20:37
shardystevebaker: that sounds fine - sdake seemed to indicated if we moved them to a separate repo that downstream distros would be somehow obligated to package and document them20:38
shardyI didn't quite get to the bottom of why20:38
*** jlucci has quit IRC20:38
SpamapSthey sound like decent things to have in heat proper as sort of contrib/test/helpful bits to make sure the cfn api is working.. ?20:38
stevebakertempest already has boto tests for ec2 compat. I think the primary way to confirm our cfn compatibility is to add to these. These would not require heat-cfnclient at all20:38
shardySpamapS: Yeah, that would work too, and just not package them20:39
shardystevebaker: Agree, there was a functional test previously which did exactly that20:39
SpamapSAgreed to have tempest do api calls directly.20:39
zanebjpeeler: clients are generally not kept in the same repo, so it's incongruous to have those ones there20:40
stevebakerto me, it is madness that clients were packaged in server packages anyway - but I don't know distro policies on removing executables from packages20:40
shardyand there was an argument about removing heat-boto vs heat-cfn, but they are actually the same tool, one symlinks to the other, it just selects a different client wrapper20:40
shardyie the duplication is not significant and they can both be useful20:40
*** markvan has joined #openstack-meeting20:40
SpamapSYeah, I think its fine to have them in another repo, but I wouldn't call their presence in heat anything more than a low priority bug.20:41
shardyI definitely agree (despite occasional version pain) that we should keep testing the cfn api with boto instead of our own client lib20:41
stevebakerheat-boto is not working for me right now, but I may have old copies of keystoneclient20:41
*** jhenner has joined #openstack-meeting20:41
zanebstevebaker: it made some sense to me because when you change the api you also have to change the client20:41
shardystevebaker: Yeah >=0.9.1 needs my patch to keystoneclient Ec2Signer20:41
shardyhttps://review.openstack.org/#/c/35945/20:42
stevebakerso how is heat-cfntools not broken?20:42
shardysorry boto 2.9.220:42
shardystevebaker: the jeos images don't use bleeding edge boto20:43
shardye.g F18 is still 2.6.020:43
stevebakerok20:43
* SpamapS would just like to note that boto is the devil20:43
asalkeldhaha20:43
stevebakerso, the delete change is here https://review.openstack.org/#/c/38228/20:44
stevebakerimport repo is here https://github.com/steveb/heat-cfnclient20:44
topolboto 666.  the version never changes20:44
stevebakerlaunchpad and pypi are set up and ready to go20:44
*** YorikSar has joined #openstack-meeting20:44
zanebSpamapS: but if anybody is ever going to use the cfn-api again, they'll almost certainly be using boto to do it20:44
SpamapSzaneb: I wrote my own cfn calls for os-collect-config20:45
shardystevebaker: what do we gain by moving to a new repo, vs just moving to a subdir in heat master?20:45
SpamapSand just used keystoneclient for ec2signer20:45
stevebakerremoving a bunch of client specific code from "common"20:45
stevebakerthe only thing really common between client, api and engine is exceptions20:45
zanebSpamapS: yeah, the in-instance side is a different story20:45
shardystevebaker: Ok, well if you can get past sdake's objections, I'm not opposed to it20:46
SpamapShttps://github.com/stackforge/os-collect-config/blob/master/os_collect_config/cfn.py20:46
zanebSpamapS: from the API perspective, you're either migrating from AWS and therefore using boto, or not and you should just jump straight to the native api20:46
stevebakerusing boto is not mandatory though20:47
shardyYeah, we've found a lot of CFN incompatibilities by using boto for testing20:47
asalkeldec2signer20:47
asalkeldzane for in-instance calls20:47
shardybut nobody is saying users have to use it, and the upstream is pretty unresponsive at times20:47
stevebakeranother thing, if we can outright kill heat-cfn then authtoken middleware can be removed from the cfn pipeline. <-- I would really like to do that20:48
zanebthe point is, if we're going to have a compatibility api, it should be compatible20:48
topolstevebaker, what would replace authtoken middelware if you remove it?20:48
stevebakereither kill heat-cfn or implement an ec2token auth strategy for it20:48
asalkeldstevebaker, you mean just use boto20:48
*** koolhead17 has quit IRC20:49
shardystevebaker: I'd be more in favor of killing heat-cfn than heat-boto20:49
zanebI'm all for killing heat-cfn and just keeping heat-boto20:49
stevebakertopol: ec2token provides auth for ec2 signed requests, like boto and heat-cfntools does20:49
shardy(even though they are the same code at the top level)20:49
topolstevebaker, gotcha. thanks20:49
zanebshardy: right, but there's a whole client.py file we can delete20:50
shardyzaneb: woohoo20:50
shardyheat-watch will die after the ceilometer migration is complete too20:50
shardyOk, lets move on20:51
shardy#topic open discussion20:51
*** openstack changes topic to "open discussion (Meeting topic: heat)"20:51
*** shri2 has left #openstack-meeting20:51
shardy9 minutes, anyone have anything to raise20:51
asalkeldsomeone on #heat didn't want to use *any* aws api20:51
*** johnthetubaguy has quit IRC20:52
asalkeldincluding ec2signers20:52
asalkeldalarming now depends on ec2signers20:52
asalkeldis that a problem20:52
stevebakeryes, deployers are disabling all ec2 features on advice of legal :/20:52
randallburtasalkeld:  not an unreasonable request considering20:52
shardyasalkeld: I think long term it would be nice to make the cfn API optional, but the signing scheme is separate from that20:52
SpamapSI think until keystone has oauth, or we embrace trusts... ec2 signer is it.20:52
topolstevebaker, wow when did that advice come down?20:52
shardyie couldn't we just allow the pre-signed URL mechanism to also work via the ReST API?20:52
stevebakershardy: not according to the lawyers20:53
SpamapSstevebaker: s/deployers/a single deployer/20:53
stevebakerSpamapS: yes20:53
stevebakerto our knowledge20:53
randallburtnot true <.< >.>20:53
SpamapSMany other orgs have come to the opposite conclusion regarding the legality of using AWS apis.20:53
shardystevebaker: sigh, so we have to reinvent something new and probably less secure, huurah20:53
asalkeldat the moment there is not really a nice alternative20:53
SpamapSs/a single deployer/a subset of deployers/20:53
stevebakerrenaming the endpoint and the class would probably do ;)20:54
randallburtlols. they are only lawyers after all :D20:54
shardySpamapS: trusts still does not provide any mechanism for signing requests20:54
SpamapSasalkeld: oauth or trusts will work fine.20:54
SpamapSdon't need to sign the req20:54
topol+1 on oauth!20:54
asalkeldis that ready yet?20:54
asalkeld(oauth)20:54
SpamapSYou have been authorized for the API call.20:54
randallburtthe lack of os native key escrow is a pita too20:55
topolasalkeld, getting close. still out for reviews20:55
zaneboauth sounds like the Right Thing20:55
shardySpamapS: the whole point of pre-signing is to avoid deploying credentials in the instance (or elsewhere, e.g to another service)20:55
topolstevemar loves feedback20:55
*** lbragstad has joined #openstack-meeting20:56
*** jlucci has joined #openstack-meeting20:56
asalkeldso what I am getting at is do I have to rework my ceilo patches20:56
shardySpamapS: so trusts may work, but we'd need to use other means to lock down the request (role based policy, and even then we can't restrict the content of the request20:56
SpamapSshardy: agreed that that is superior to oauth.20:56
asalkeld(and ceilometer)20:56
*** sushils has joined #openstack-meeting20:56
stevebakerasalkeld: not yet, there is no alternative yet20:56
shardyI just think if we're going to reinvent a new solution it should be at least as secure, definitely not less secure, otherwise what's the point?20:56
asalkeldok, well I'll leave as is for now20:57
asalkeldissue raised ...20:57
SpamapSSounds like a feature to push for soon. The right answer may be to copy whatever swift does for its signed urls.20:57
shardyYeah we can keep mulling the alternatives :)20:57
*** colinmcnamara has quit IRC20:58
*** epim has quit IRC20:58
*** boris-42 has quit IRC20:58
*** colinmcnamara has joined #openstack-meeting20:58
topolis there a use case where heat benefits from oauth?20:58
shardyOk nearly out of time, anything else or are we done?20:59
topolthought the plan was to use trust?20:59
topols20:59
shardyout of time, thanks all!20:59
*** jrodom has quit IRC20:59
shardy#endmeeting20:59
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"20:59
openstackMeeting ended Wed Jul 24 20:59:26 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-07-24-20.00.html20:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-07-24-20.00.txt20:59
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-07-24-20.00.log.html20:59
asalkeldI believe oauth is better than trusts topol20:59
*** jasond has left #openstack-meeting20:59
*** randallburt has left #openstack-meeting20:59
*** spenceratx has left #openstack-meeting20:59
*** zehicle_at_dell has joined #openstack-meeting20:59
*** therve has left #openstack-meeting20:59
*** rpothier_ has quit IRC21:00
*** sushils has quit IRC21:01
*** RightScale-RyanO has quit IRC21:01
*** sushils has joined #openstack-meeting21:02
*** timductive has left #openstack-meeting21:03
*** egallen has quit IRC21:03
*** markwash has quit IRC21:03
*** tspatzier has left #openstack-meeting21:04
*** epim has joined #openstack-meeting21:06
*** egallen has joined #openstack-meeting21:06
*** mrodden has quit IRC21:06
*** markwash has joined #openstack-meeting21:07
*** epim has quit IRC21:10
*** zehicle_at_dell has quit IRC21:10
*** numero8 has joined #openstack-meeting21:10
*** markvan has quit IRC21:14
*** alexpilotti has quit IRC21:18
*** mrodden has joined #openstack-meeting21:18
*** wirehead_ has left #openstack-meeting21:19
*** pcm_ has quit IRC21:21
*** cody-somerville has quit IRC21:21
*** andrew_plunk has left #openstack-meeting21:22
*** krtaylor has quit IRC21:24
*** MarkAtwood has quit IRC21:25
*** egallen has quit IRC21:25
*** edmund has joined #openstack-meeting21:26
*** gyee has quit IRC21:29
*** jasondotstar has quit IRC21:31
*** dkranz has joined #openstack-meeting21:33
*** neelashah has quit IRC21:34
*** glikson has joined #openstack-meeting21:36
*** spenceratx has joined #openstack-meeting21:36
*** vipul is now known as vipul-away21:37
*** MarkAtwood has joined #openstack-meeting21:39
*** vipul-away is now known as vipul21:40
*** vijendar has quit IRC21:41
*** topol has quit IRC21:43
*** markvan has joined #openstack-meeting21:44
*** marun has quit IRC21:47
*** leseb has quit IRC21:49
*** zehicle_at_dell has joined #openstack-meeting21:51
*** alexpilotti has joined #openstack-meeting21:52
*** numero8 has quit IRC21:55
*** kevinconway has quit IRC21:57
*** danwent has quit IRC22:02
*** leseb has joined #openstack-meeting22:04
*** cschwede has joined #openstack-meeting22:04
*** burt has quit IRC22:07
*** cschwede has quit IRC22:09
*** pentameter has quit IRC22:11
*** ivasev has quit IRC22:13
*** markvan has quit IRC22:13
*** rnirmal has quit IRC22:14
*** jlucci has quit IRC22:14
*** lastidiot has quit IRC22:16
*** mdomsch has quit IRC22:17
*** epim has joined #openstack-meeting22:19
*** diogogmt has quit IRC22:19
*** leseb has quit IRC22:20
*** MarkAtwood has quit IRC22:24
*** lifeless has quit IRC22:26
*** changbl has quit IRC22:28
*** esker has quit IRC22:28
*** krtaylor has joined #openstack-meeting22:30
*** Haitao_ has quit IRC22:34
*** zehicle_at_dell has quit IRC22:34
*** lifeless has joined #openstack-meeting22:35
*** johnthetubaguy has joined #openstack-meeting22:39
*** spzala has quit IRC22:39
*** jhenner has quit IRC22:40
*** woodspa_ has quit IRC22:40
*** nachi_ has joined #openstack-meeting22:41
*** nachi_ has quit IRC22:41
*** marun has joined #openstack-meeting22:42
*** henrynash has quit IRC22:44
*** glikson has quit IRC22:46
*** nati_ueno_2 has joined #openstack-meeting22:49
*** ffive has joined #openstack-meeting22:50
*** johnthetubaguy has quit IRC22:52
*** ffive has quit IRC22:52
*** galstrom is now known as galstrom_zzz22:53
*** kmartin has joined #openstack-meeting22:54
*** jmontemayor has quit IRC22:58
*** eharney has quit IRC22:58
*** danwent has joined #openstack-meeting22:58
*** brucer has joined #openstack-meeting22:59
*** colinmcnamara has quit IRC23:06
*** vipul is now known as vipul-away23:12
*** vipul-away is now known as vipul23:14
*** jrodom has joined #openstack-meeting23:16
*** michchap has joined #openstack-meeting23:16
*** litong has quit IRC23:16
*** novas0x2a|laptop has quit IRC23:18
*** colinmcnamara has joined #openstack-meeting23:20
*** novas0x2a|laptop has joined #openstack-meeting23:20
*** lastidiot has joined #openstack-meeting23:21
*** fnaval_ has quit IRC23:21
*** MarkAtwood has joined #openstack-meeting23:26
*** edmund has quit IRC23:27
*** jrodom has quit IRC23:28
*** changbl has joined #openstack-meeting23:28
*** hemna is now known as hemnafk23:31
*** sushils has quit IRC23:32
*** ryanpetrello has quit IRC23:34
*** gyee has joined #openstack-meeting23:40
*** esker has joined #openstack-meeting23:41
*** salv-orlando has quit IRC23:42
*** gongysh has joined #openstack-meeting23:43
*** rods has quit IRC23:47
*** rwsu is now known as rwsu-away23:48
*** colinmcnamara has quit IRC23:49
*** esker has quit IRC23:51
*** marun has quit IRC23:56
*** colinmcnamara has joined #openstack-meeting23:58
*** colinmcnamara has quit IRC23:58
*** lpabon_ has joined #openstack-meeting23:59

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