Tuesday, 2015-06-16

*** vnod has quit IRC00:07
*** yamamoto has quit IRC00:17
*** Sukhdev has quit IRC00:17
*** stevemar has joined #openstack-meeting-300:18
*** natorious is now known as zz_natorious00:20
*** david-lyle has quit IRC00:24
*** Swami has quit IRC00:30
*** zz_natorious is now known as natorious00:31
*** dims has quit IRC00:33
*** jckasper has joined #openstack-meeting-300:37
*** fallenpegasus has quit IRC00:40
*** mwang2_ has quit IRC00:42
*** dims has joined #openstack-meeting-300:46
*** baoli has joined #openstack-meeting-300:51
*** fallenpegasus has joined #openstack-meeting-300:55
*** yamamoto has joined #openstack-meeting-300:57
*** bpokorny has quit IRC01:00
*** banix has joined #openstack-meeting-301:01
*** Poornima has joined #openstack-meeting-301:13
*** tobe has joined #openstack-meeting-301:19
*** sigmavirus24 is now known as sigmavirus24_awa01:20
*** tqtran has quit IRC01:22
*** carl_baldwin has quit IRC01:27
*** Longgeek has joined #openstack-meeting-301:32
*** stanzgy has joined #openstack-meeting-301:35
*** natorious is now known as zz_natorious01:42
*** fallenpegasus has quit IRC01:42
*** banix has quit IRC01:45
*** dims has quit IRC01:50
*** Longgeek has quit IRC01:52
*** zz_natorious is now known as natorious01:54
*** banix has joined #openstack-meeting-301:56
*** hichihara has quit IRC01:58
*** hichihara has joined #openstack-meeting-302:01
*** amotoki has joined #openstack-meeting-302:04
*** david-lyle has joined #openstack-meeting-302:08
*** sankarshan_away is now known as sankarshan_02:09
*** nati_ueno has joined #openstack-meeting-302:11
*** jpomero has quit IRC02:13
*** amotoki has quit IRC02:20
*** amotoki has joined #openstack-meeting-302:31
*** bradjones has quit IRC02:35
*** bradjones has joined #openstack-meeting-302:35
*** bradjones has quit IRC02:35
*** bradjones has joined #openstack-meeting-302:35
*** amotoki has quit IRC02:39
*** amotoki has joined #openstack-meeting-302:39
*** baoli has quit IRC02:42
*** banix has quit IRC02:43
*** baoli has joined #openstack-meeting-302:43
*** Longgeek has joined #openstack-meeting-302:49
*** bryan_att has quit IRC02:53
*** amotoki has quit IRC03:01
*** banix has joined #openstack-meeting-303:05
*** pballand has quit IRC03:06
*** stevemar has quit IRC03:06
*** pballand has joined #openstack-meeting-303:08
*** Piet has quit IRC03:09
*** Longgeek has quit IRC03:17
*** tobe has quit IRC03:20
*** tobe has joined #openstack-meeting-303:23
*** amotoki has joined #openstack-meeting-303:24
*** reed has quit IRC03:31
*** banix has quit IRC03:31
*** marios has quit IRC03:32
*** sdake has quit IRC03:32
*** marios has joined #openstack-meeting-303:32
*** reed has joined #openstack-meeting-303:33
*** coolsvap|afk is now known as coolsvap03:41
*** fallenpegasus has joined #openstack-meeting-303:44
*** baoli has quit IRC03:44
*** pballand has quit IRC03:45
*** dims has joined #openstack-meeting-303:46
*** nati_ueno has quit IRC03:46
*** nati_ueno has joined #openstack-meeting-303:47
*** nati_ueno has quit IRC03:47
*** dims has quit IRC03:51
*** ivar-lazzaro has quit IRC03:54
*** ivar-lazzaro has joined #openstack-meeting-303:55
*** redrobot has quit IRC03:55
*** ivar-lazzaro has quit IRC03:59
*** radek_ has joined #openstack-meeting-304:14
*** Longgeek has joined #openstack-meeting-304:14
*** radek__ has quit IRC04:15
*** sdake has joined #openstack-meeting-304:17
*** belmoreira has joined #openstack-meeting-304:26
*** Sukhdev has joined #openstack-meeting-304:31
*** belmoreira has quit IRC04:31
*** irenab has quit IRC04:32
*** nati_ueno has joined #openstack-meeting-304:39
*** Longgeek has quit IRC04:41
*** yuikotakada has joined #openstack-meeting-304:47
*** tobe has quit IRC04:47
*** mrmartin has joined #openstack-meeting-304:50
*** amotoki has quit IRC04:59
*** tobe has joined #openstack-meeting-305:07
*** nkrinner has joined #openstack-meeting-305:18
*** zz_jgrimm is now known as jgrimm05:20
*** sridhar_ram has joined #openstack-meeting-305:20
*** amotoki has joined #openstack-meeting-305:21
*** irenab has joined #openstack-meeting-305:21
*** lazy_prince has joined #openstack-meeting-305:24
*** yamahata has joined #openstack-meeting-305:28
*** mrmartin has quit IRC05:29
*** stevemar has joined #openstack-meeting-305:30
*** sridhar_ram has quit IRC05:31
*** aswadr has joined #openstack-meeting-305:35
*** tobe has quit IRC05:37
*** armax has quit IRC05:38
*** Longgeek has joined #openstack-meeting-305:38
*** Longgeek has quit IRC05:47
*** Longgeek has joined #openstack-meeting-305:48
*** asrangne has joined #openstack-meeting-305:50
*** aswadr has quit IRC05:51
*** ihrachyshka has joined #openstack-meeting-305:55
*** belmoreira has joined #openstack-meeting-305:55
*** jtomasek has joined #openstack-meeting-305:57
*** ihrachyshka has quit IRC06:01
*** tobe has joined #openstack-meeting-306:02
*** asrangne has quit IRC06:04
*** mrunge has joined #openstack-meeting-306:06
*** mrmartin has joined #openstack-meeting-306:07
*** sdake has quit IRC06:14
*** hichihara has quit IRC06:17
*** ramanjaneya has joined #openstack-meeting-306:30
*** Sukhdev has quit IRC06:31
*** mrmartin has quit IRC06:34
*** belmoreira has quit IRC06:36
*** zhenguo has joined #openstack-meeting-306:40
*** salv-orlando has joined #openstack-meeting-306:44
*** salv-orl_ has joined #openstack-meeting-306:46
*** fallenpegasus has quit IRC06:48
*** salv-orlando has quit IRC06:49
*** ihrachyshka has joined #openstack-meeting-306:50
*** mrmartin has joined #openstack-meeting-306:56
*** matrohon has joined #openstack-meeting-307:01
*** natorious is now known as zz_natorious07:02
*** mrmartin has quit IRC07:13
*** woodster_ has quit IRC07:21
*** bradjones has quit IRC07:30
*** bradjones has joined #openstack-meeting-307:36
*** bradjones has quit IRC07:36
*** bradjones has joined #openstack-meeting-307:36
*** zz_ttrifonov is now known as ttrifonov07:39
*** devvesa has joined #openstack-meeting-307:40
*** tobe has quit IRC07:40
*** tobe has joined #openstack-meeting-307:47
*** nati_ueno has quit IRC07:49
*** nati_ueno has joined #openstack-meeting-307:49
*** stanzgy__ has joined #openstack-meeting-307:50
*** stanzgy has quit IRC07:51
*** belmoreira has joined #openstack-meeting-307:54
*** nati_ueno has quit IRC07:54
*** nati_ueno has joined #openstack-meeting-307:57
*** jcoufal has joined #openstack-meeting-308:00
*** safchain has joined #openstack-meeting-308:03
*** tobe has quit IRC08:06
*** tobe has joined #openstack-meeting-308:16
*** nati_ueno has quit IRC08:21
*** nati_ueno has joined #openstack-meeting-308:22
*** nati_ueno has quit IRC08:26
*** yamahata has quit IRC08:29
*** nati_ueno has joined #openstack-meeting-308:32
*** btully has quit IRC08:37
*** btully has joined #openstack-meeting-308:39
*** rushiagr_away is now known as rushiagr08:44
*** nati_ueno has quit IRC08:51
*** yamahata has joined #openstack-meeting-308:52
*** stevemar has quit IRC08:52
*** nati_ueno has joined #openstack-meeting-308:54
*** yamahata has quit IRC08:57
*** yamamoto has quit IRC08:58
*** yamamoto has joined #openstack-meeting-308:58
*** e0ne has joined #openstack-meeting-309:12
*** dims has joined #openstack-meeting-309:18
*** e0ne is now known as e0ne_09:21
*** dims has quit IRC09:23
*** e0ne_ has quit IRC09:25
*** e0ne has joined #openstack-meeting-309:28
*** john-davidge has joined #openstack-meeting-309:43
*** tobe has quit IRC09:46
*** john-davidge_ has joined #openstack-meeting-309:48
*** john-davidge has quit IRC09:48
*** john-davidge_ is now known as john-davidge09:48
*** nati_ueno has quit IRC09:49
*** tobe has joined #openstack-meeting-309:56
*** e0ne is now known as e0ne_10:06
*** e0ne_ has quit IRC10:12
*** Poornima has quit IRC10:12
*** e0ne has joined #openstack-meeting-310:17
*** Longgeek_ has joined #openstack-meeting-310:25
*** Longgeek has quit IRC10:28
*** hichihara has joined #openstack-meeting-310:33
*** john-davidge has quit IRC10:50
*** john-davidge_ has joined #openstack-meeting-310:50
*** tobe has quit IRC10:50
*** yuikotakada is now known as yuikot_dinner10:51
*** yuikot_dinner has quit IRC10:51
*** tobe has joined #openstack-meeting-310:51
*** stanzgy__ has quit IRC10:53
*** tobe has quit IRC10:56
*** ihrachyshka has left #openstack-meeting-311:06
*** salv-orl_ has quit IRC11:09
*** e0ne is now known as e0ne_11:12
*** dims has joined #openstack-meeting-311:20
*** devvesa has quit IRC11:21
*** coolsvap is now known as coolsvap|afk11:23
*** e0ne_ has quit IRC11:23
*** dims has quit IRC11:25
*** coolsvap|afk is now known as coolsvap11:26
*** dims has joined #openstack-meeting-311:29
*** coolsvap is now known as coolsvap|afk11:30
*** coolsvap|afk is now known as coolsvap11:31
*** salv-orlando has joined #openstack-meeting-311:32
*** jcoufal has quit IRC11:35
*** e0ne has joined #openstack-meeting-311:37
*** Longgeek_ has quit IRC11:40
*** Longgeek has joined #openstack-meeting-311:40
*** salv-orlando has quit IRC11:43
*** baoli has joined #openstack-meeting-311:45
*** mrunge has quit IRC11:48
*** coolsvap is now known as coolsvap|afk11:52
*** mrunge has joined #openstack-meeting-311:54
*** banix has joined #openstack-meeting-311:56
*** yamamoto has quit IRC11:57
*** banix has quit IRC11:58
*** baoli has quit IRC12:04
*** hichihara has quit IRC12:14
*** salv-orlando has joined #openstack-meeting-312:15
*** VW has joined #openstack-meeting-312:16
*** bknudson has quit IRC12:22
*** baoli has joined #openstack-meeting-312:33
*** alexpilotti has joined #openstack-meeting-312:38
*** hichihara has joined #openstack-meeting-312:39
*** VW has quit IRC12:41
*** redrobot has joined #openstack-meeting-312:42
*** redrobot is now known as Guest7499312:42
*** Guest74993 is now known as el_robot_rojo12:43
*** el_robot_rojo is now known as redrobot12:44
*** bknudson has joined #openstack-meeting-312:50
*** jckasper has quit IRC12:55
*** nati_ueno has joined #openstack-meeting-312:56
*** amotoki has quit IRC12:56
*** edleafe has quit IRC12:57
*** yamamoto has joined #openstack-meeting-312:58
*** edleafe has joined #openstack-meeting-312:59
*** stendulker has joined #openstack-meeting-313:00
*** yamahata has joined #openstack-meeting-313:01
*** yamamoto_ has joined #openstack-meeting-313:02
*** mrunge has quit IRC13:04
*** VW has joined #openstack-meeting-313:05
*** yamamoto has quit IRC13:05
*** john-davidge has joined #openstack-meeting-313:09
*** john-davidge_ has quit IRC13:10
*** rushiagr is now known as rushiagr_away13:10
*** banix has joined #openstack-meeting-313:11
*** vgridnev has joined #openstack-meeting-313:19
*** marun has joined #openstack-meeting-313:19
*** marun has quit IRC13:20
*** julim has joined #openstack-meeting-313:21
*** VW has quit IRC13:23
*** cbader has joined #openstack-meeting-313:23
*** VW has joined #openstack-meeting-313:25
*** peristeri has joined #openstack-meeting-313:29
*** john-davidge has left #openstack-meeting-313:31
*** lblanchard has joined #openstack-meeting-313:31
*** sdake has joined #openstack-meeting-313:32
*** sdake has quit IRC13:32
*** VW has quit IRC13:33
*** sdake has joined #openstack-meeting-313:33
*** singlethink has joined #openstack-meeting-313:34
*** banix has quit IRC13:46
*** e0ne is now known as e0ne_13:51
*** armax has joined #openstack-meeting-313:53
*** lazy_prince has quit IRC13:54
*** e0ne_ is now known as e0ne13:54
*** Sukhdev has joined #openstack-meeting-313:56
*** jckasper has joined #openstack-meeting-313:56
*** carl_baldwin has joined #openstack-meeting-313:59
*** cbouch has joined #openstack-meeting-313:59
*** bryan_att has joined #openstack-meeting-313:59
*** amotoki has joined #openstack-meeting-314:00
*** ajmiller has joined #openstack-meeting-314:05
*** woodster_ has joined #openstack-meeting-314:09
*** qwebirc35267 has joined #openstack-meeting-314:12
*** sigmavirus24_awa is now known as sigmavirus2414:16
*** nkrinner has quit IRC14:19
*** zz_natorious is now known as natorious14:21
*** mattgriffin has joined #openstack-meeting-314:24
*** irenab has quit IRC14:26
*** lazy_prince has joined #openstack-meeting-314:30
*** nati_ueno has quit IRC14:32
*** Piet has joined #openstack-meeting-314:35
*** ttrifonov is now known as zz_ttrifonov14:37
*** aswadr has joined #openstack-meeting-314:39
*** aswadr has quit IRC14:40
*** aswadr has joined #openstack-meeting-314:40
*** carl_baldwin has quit IRC14:42
*** obondarev has quit IRC14:45
*** obondarev has joined #openstack-meeting-314:46
*** e0ne is now known as e0ne_14:47
*** e0ne_ is now known as e0ne14:47
*** VW has joined #openstack-meeting-314:47
*** stevemar has joined #openstack-meeting-314:50
*** stendulker has quit IRC14:50
*** wojdev has joined #openstack-meeting-314:53
*** egallen has joined #openstack-meeting-314:55
*** coolsvap|afk is now known as coolsvap14:56
*** cbouch has quit IRC14:57
*** stendulker has joined #openstack-meeting-314:59
*** carl_baldwin has joined #openstack-meeting-314:59
*** VW has quit IRC15:02
*** VW has joined #openstack-meeting-315:03
*** VW has quit IRC15:04
*** jcoufal has joined #openstack-meeting-315:04
*** belmoreira has quit IRC15:05
*** fallenpegasus has joined #openstack-meeting-315:06
*** jaypipes has quit IRC15:06
*** VW has joined #openstack-meeting-315:12
*** yamahata has quit IRC15:12
*** wojdev has quit IRC15:14
*** banix has joined #openstack-meeting-315:16
*** etoews has joined #openstack-meeting-315:16
*** asrangne has joined #openstack-meeting-315:20
*** banix has quit IRC15:21
*** bpokorny has joined #openstack-meeting-315:22
*** banix has joined #openstack-meeting-315:22
*** aswadr has quit IRC15:23
*** puranamr has joined #openstack-meeting-315:23
*** puranamr has quit IRC15:26
*** ajmiller has quit IRC15:27
*** ajmiller has joined #openstack-meeting-315:27
*** vgridnev has quit IRC15:29
*** sridhar_ram has joined #openstack-meeting-315:29
*** asrangne__ has joined #openstack-meeting-315:29
*** dhruv has quit IRC15:30
*** asrangne has quit IRC15:31
*** zz_ttrifonov is now known as ttrifonov15:33
*** puranamr has joined #openstack-meeting-315:35
*** singlethink has quit IRC15:36
*** krtaylor has quit IRC15:40
*** jgrimm is now known as zz_jgrimm15:41
*** peristeri has quit IRC15:45
*** john-davidge has joined #openstack-meeting-315:46
*** absubram has joined #openstack-meeting-315:46
*** zz_jgrimm is now known as jgrimm15:46
*** hichihara has quit IRC15:46
*** pavel_bondar is now known as pavel_bondar_afk15:47
*** john-davidge has quit IRC15:48
*** puranamr has quit IRC15:50
*** gsagie has joined #openstack-meeting-315:51
*** puranamr has joined #openstack-meeting-315:51
*** krtaylor has joined #openstack-meeting-315:54
*** gsagie has left #openstack-meeting-315:56
*** Sukhdev has quit IRC15:56
*** ttrifonov is now known as zz_ttrifonov15:56
*** mhanif has joined #openstack-meeting-316:00
*** VW has quit IRC16:00
*** pc_m has joined #openstack-meeting-316:00
*** yanping has joined #openstack-meeting-316:00
mhanifpc_m: Hi Paul16:00
ajmillerGood Day!16:01
pc_mmhanif: sridhar_ram: yanping: ramanjaneya: ajmiller: matrohon hi!16:01
pc_mwill start ina  min.16:01
*** tholtzen has joined #openstack-meeting-316:01
pc_m#startmeeting vpnaas16:02
openstackMeeting started Tue Jun 16 16:02:09 2015 UTC and is due to finish in 60 minutes.  The chair is pc_m. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: vpnaas)"16:02
openstackThe meeting name has been set to 'vpnaas'16:02
pc_mThe agenda is on the Wiki: https://wiki.openstack.org/wiki/Meetings/VPNaaS16:02
pc_mLot's to cover today...16:02
pc_mNeutron Mid-cycle is next week.16:03
pc_mI'll be travelling and won't be able to run meeting. Anyone want to run the meeting, or do we want to skip a week?16:03
*** john_a_joyce has joined #openstack-meeting-316:04
sridhar_rampc_m: I can run the mtg if there an Agenda16:04
pc_msridhar_ram: Thanks! We can fill out agenda items for you.16:05
sridhar_rampc_m: sure16:05
pc_mAnyone have any other announcements w.r.t. VPNaaS?16:05
pc_m#action sridhar_ram will chair meeting next week (6/23)16:05
pc_m#topic Multiple local subnets16:06
*** openstack changes topic to "Multiple local subnets (Meeting topic: vpnaas)"16:06
pc_mI've made up Dev Ref pages for this feature and it is out for review #link https://review.openstack.org/#/c/191944/216:06
pc_mPlease look at this, which has some design ideas for the multiple local subnet.16:07
pc_mOf big importance, is a proposal  to break the connection API into two, one for the IPSec connection details (as is currently), and one for the endpoint pairs.16:07
pc_mThe latter is intended to separate the "what" gets connected from the "how" to connect. The goal here is that we could use this for other VPN types.16:08
*** asrangne__ has quit IRC16:08
pc_mWould like to see community opinion on this ASAP, so we can start on it.16:09
john_a_joycepc_m:  I like the proposal although have not added the comment yet16:09
pc_mjohn_a_joyce: cool. Looking forward to feedback.16:09
pc_mWould like to see if this could be used for BGP VPN too.16:09
sridhar_rampc_m: will add it to my review queue.. overall agree w/ the approach16:09
*** singlethink has joined #openstack-meeting-316:11
pc_msridhar_ram: Thanks. mhanif, matrohon, and other BGP and edge VPN folks check it out!16:11
pc_m#topic certificates16:11
*** openstack changes topic to "certificates (Meeting topic: vpnaas)"16:11
*** wojdev has joined #openstack-meeting-316:11
matrohonpc_m : I'll do, thanks16:11
*** VW has joined #openstack-meeting-316:11
pc_mmatrohon: Thanks!16:11
pc_mI did the action item and posted a ML question on certificates. No response yet. :(16:11
pc_mThis one too, I'm proposing breaking out an API for auth credentials, so that it can be used by other VPN flavors.16:12
pc_mSo, instead of the connection specifying a PSK or UUID of a certificate, it would specify an auth credential UUID, and that credential would have all the info. Could share it by multiple connections too.16:13
sridhar_rampc_m: do we have a liason or point of contact in Barbican who can help to consult on this ?16:13
pc_mOnly have a bug on this, no dev ref yet.  https://bugs.launchpad.net/neutron/+bug/145942716:14
openstackLaunchpad bug 1459427 in neutron "VPNaaS: Certificate support for IPSec" [Undecided,Triaged]16:14
pc_msridhar_ram: I've talked to Brandon and Doug. I think there is a person named Phil as well to contact.16:14
ajmillerpc_m I am interested in the certificate question but am woefully behind on email.16:14
pc_mThere was a summit talk on Barbican users, and LBaaS team spoke of what they did.16:15
ajmillerpc_m That would be Phil Toohill (ptoohill in IRC).  He did much of the LBaaS barbican integration.16:16
pc_mI suspect that, out of the gate, we'll do X.509 certificates.16:16
pc_majmiller: Thanks16:16
pc_mSummit link... https://www.youtube.com/watch?v=ihsQJL-tFxI&t=8m42s16:17
ajmiller#link  https://www.youtube.com/watch?v=ihsQJL-tFxI&t=8m42s16:17
ajmiller^^that will post the link in the meeting minutes.16:17
pc_mEssentially one creates the certificate  and container in Barbican and then can use it in VPN.16:18
pc_majmiller: Thanks. I forgot the link16:18
*** pballand has joined #openstack-meeting-316:18
pc_mAnyone interested in working on the certificate stuff, let me know.16:19
* pc_m working on, leading, helping, etc...16:19
pc_m#topic DM VPN16:19
*** openstack changes topic to "DM VPN (Meeting topic: vpnaas)"16:19
*** mattgriffin has quit IRC16:20
pc_mThere was an action item for yanping on network-id being able to use tunnel-key. yanping?16:20
pc_mIs that resolved (I think so)?16:20
yanpingcorrect. Think it is solved in the spec review16:20
*** angela-s has joined #openstack-meeting-316:21
sridhar_rampc_m: yanping: yeah, we took care of it in the spec16:21
pc_mEveryone please help review https://review.openstack.org/#/c/181563/16:21
pc_msridhar_ram: anything else on DM VPN?16:21
sridhar_ramsridhar_ram: Similar to certificate, I'd like to invite folks interested to participate in the implementation16:22
sridhar_rampc_m: nothing else from the spec point of view16:23
pc_msridhar_ram: okey dokey16:23
pc_m#topic BGP/MPLS and Edge VPN.16:23
*** openstack changes topic to "BGP/MPLS and Edge VPN. (Meeting topic: vpnaas)"16:23
pc_mThere were a few action items from last week. matrohon did you get a chance to do a drawing for bagpipe?16:23
matrohonI did not make any progress on the drawing, sorry, but I still have that in my todo list!16:24
pc_mmatrohon: super. looking forward to it.16:24
pc_mI'll open the floor to continuation on discussion on this.  I'd be interested in hearing about whether we can separate out the what and how for VPN and use it for different flavors of VPN.16:25
*** mrmartin has joined #openstack-meeting-316:26
pc_mThe endpoint pair proposal is one thought on that. I'd like to hear others and see if there is some commonality there.16:26
mhanifFolks, at a high level, for L2/L3 VPNs we have two distinct functionalities to address16:26
mhanifOne is provisioning of a VPN and other is to bind a Neutron network to it.  Agreed?16:27
*** jcoufal has quit IRC16:28
mhanifIn that sense, should we try to combine our efforts to address them in a manner which resolves all use cases16:28
*** amotoki has quit IRC16:28
john_a_joyceI think pc_m proposal in https://review.openstack.org/#/c/191944/2 might be a start along those lines16:29
pc_mmhanif:  Can you add that to the etherpad #link  https://etherpad.openstack.org/p/vpn-flavors16:29
john_a_joyceit breaks it up in two16:29
mhanifI see the provisioning as an admin task while binding task could be handed over to the tenant as well16:29
pc_mmhanif: at your leisure.16:29
john_a_joyceI believe as you were thinking although in that case it is IPSEC for the tunnel16:29
mhanifpc_m: I have added to the vpn-flavors.  Will make it more clear there16:30
*** baoli has quit IRC16:30
pc_mmhanif: thanks! good to know the use cases.16:30
*** singleth_ has joined #openstack-meeting-316:30
*** john-a-joyce has joined #openstack-meeting-316:31
pc_mmhanif: Take a look at https://review.openstack.org/#/c/191944/2/doc/source/devref/multiple-local-subnets.rst, option B.16:31
*** banix has quit IRC16:31
*** baoli_ has joined #openstack-meeting-316:31
mhanifpc_m: Sure will do.16:31
pc_mmhanif: I'm hoping it may be massaged to work for your binding case.16:31
mhanifHence, I would like to propose that we have generic APIs to address what I just described16:31
*** tqtran has joined #openstack-meeting-316:32
matrohondo you see the Edge vpn API as a way to provision and the BGPVPN API a way to bind networks?16:32
mhanifAPIs which are not limited to one type of VPN or any one of Neutron network16:32
mhanifmatrohon:  Edge VPN API spec addresses both16:33
mhanifI need to separate them out and make them two spec16:33
matrohonmhanif : ok, make sense16:33
*** singlethink has quit IRC16:33
mhanifThe other spec will be inline with what BGP VPN spec talks about16:33
*** john_a_joyce has quit IRC16:34
*** tsbot_ has joined #openstack-meeting-316:34
*** wojdev has quit IRC16:35
*** tsbot_ has left #openstack-meeting-316:35
*** stendulker has quit IRC16:35
mhanifpc_m: The binding spec will again be addressing all varieties of networks16:35
john-a-joycecool - so it seems like we pretty much have a consensus on the functional split16:35
john-a-joycewe just need to hammer out the details so all the use cases can be hit16:35
*** tsbot_ has joined #openstack-meeting-316:35
pc_mmatrohon: mhanif: Let me know if you think the vpn-endpoint-pair API could handle the binding.16:36
sridhar_ram+1 for split it this way16:36
*** banix has joined #openstack-meeting-316:36
*** wojdev has joined #openstack-meeting-316:36
mhanifjohn-a-joyce: agreed16:36
matrohonpc_m : your current proposal attach vpn services to a router16:37
pc_mI was trying to adapt the vpn-endpoint-pair for the binding and the ipsec-site-connection for IPSec provisioning.16:38
pc_mmatrohon: only because that was the original approach. Trying to modify that, in a backward compatible way (hopefully).16:39
pc_mThe vpn-endpoint-pair API would allow routers, networks, cidrs, vlan, route-targets, etc. as endpoints.16:39
*** banix_ has joined #openstack-meeting-316:40
*** banix has quit IRC16:40
*** banix_ is now known as banix16:40
* sridhar_ram makes a note to read endpoint-pair spec w/ all VPNs in mind16:41
matrohonpc_m : I'm not sure it is useful; I don't really see how endpoitns pair match bgp vpns16:42
mhanifpc_m: sridhar_ram:  Edge VPN calls it an attachment circuit in its spec16:42
sridhar_rammhanif: I see16:43
*** rushiagr_away is now known as rushiagr16:43
pc_mmhanif: Would that make sense for naming with IPSec or other VPN types? I was trying to pick something generic. Would like to hear suggestions in the review comments.16:44
pc_mmatrohon: Could we create an endpoint pair, with the peer being route targets (imported)?16:45
mhanifThe VPN construct becomes the provider/keeper of the circuit/endpoint.16:45
*** mwang2 has joined #openstack-meeting-316:46
mhanifpc_m: Sure.  Will review the spec and provide comments16:46
matrohonpc_m : I have to think about it;16:46
*** Swami has joined #openstack-meeting-316:47
matrohonpc_m : I feel that API would result in a complex matrix with type supported by only few of connection types16:47
*** banix has quit IRC16:47
mhanifConnection type can be abstracted out as a UUID16:48
pc_mI think the goals in the review are.... A) is it better to try to split out the what from the how, as part of the multiple local subnet work, B) would that work for other VPN types, and C) do we have a reasonable naming and capabilities with it.16:48
john-a-joycematrohon: I guess that is the tradeoff we have to decide16:48
*** e0ne has quit IRC16:48
*** Longgeek has quit IRC16:49
sridhar_rampc_m: agree, striking the right abstraction to accommodate different "type" of VPN is the goal16:49
john-a-joycedo we want a more common API and the connection types would support all the cases16:49
john-a-joyceor have APIs for each different type of connection16:49
*** absubram has left #openstack-meeting-316:50
sridhar_rammatrohon: mhanif: pc_am: can we abstract current implicit assumption that VPN is associated with neutron-router16:50
pc_mjohn-a-joyce: good summary16:51
matrohonsridhar_ram : may be by putting the router in the local type?16:52
*** puranamr has quit IRC16:52
sridhar_raminstead associate with a generic "vpn-target"16:52
sridhar_ramneutron-router-id being one of the target or PE-router-id where the "vpn" got created16:53
*** puranamr has joined #openstack-meeting-316:53
*** safchain has quit IRC16:53
pc_mmatrohon: the local type would be cidr for IPSec to indicate the near end subnet(s).16:54
*** sridhar_ram has quit IRC16:54
matrohonpc_m : I see16:55
mhanifsridhar_ram: The router where VPN is created may not have been abstracted out in Neutron16:55
matrohonmhanif : +116:55
*** sarob has joined #openstack-meeting-316:55
pc_mmatrohon: For IPSec you'd have local and peer subnets describing the what.16:55
*** sridhar_ram has joined #openstack-meeting-316:56
*** Longgeek has joined #openstack-meeting-316:56
pc_mAlso, the router is at a little higher level, as it applies to all connections for the service.16:56
*** Longgeek has quit IRC16:56
* sridhar_ram is back16:56
pc_mDo we need the vpn-service API for IPSec as a container for the connections (and specify the router)?16:56
*** thinrichs has joined #openstack-meeting-316:57
*** wojdev has quit IRC16:58
*** sridhar_ram has quit IRC16:58
pc_mIn any case, we're about out of time. Please comment on the review, which although is for multiple local subnets, is trying to do so in a manner that is looking ahead, if possible. If not, we can do option A, but I'd like to try to do more (and not have to churn on the API later).16:58
*** masahito has joined #openstack-meeting-316:58
pc_mThanks for the great discussion on this!16:58
matrohonpc_m : not sure to understand : you mean moving the router_id in ipsec-site-connection-create16:59
matrohonok thanks16:59
*** alexsyip has joined #openstack-meeting-316:59
*** egallen has quit IRC16:59
*** angela-s has quit IRC16:59
pc_mmatrohon: no, was thinking to keep it on the vpn-service API and use that as a container for connections (which it sort of is today) for IPSec.16:59
pc_mmatrohon: Lt's continue on neutron IRC...16:59
*** sridhar_ram has joined #openstack-meeting-317:00
*** sarob has quit IRC17:00
*** puranamr has quit IRC17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Tue Jun 16 17:00:12 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vpnaas/2015/vpnaas.2015-06-16-16.02.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vpnaas/2015/vpnaas.2015-06-16-16.02.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/vpnaas/2015/vpnaas.2015-06-16-16.02.log.html17:00
*** pc_m has left #openstack-meeting-317:00
thinrichsHi all.  Time for the Congress meeting.17:00
*** mhanif has quit IRC17:01
thinrichs#startmeeting CongressTeamMeeting17:01
openstackMeeting started Tue Jun 16 17:01:09 2015 UTC and is due to finish in 60 minutes.  The chair is thinrichs. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: CongressTeamMeeting)"17:01
openstackThe meeting name has been set to 'congressteammeeting'17:01
*** tholtzen has left #openstack-meeting-317:01
*** mrunge has joined #openstack-meeting-317:01
*** yanping has left #openstack-meeting-317:01
*** sarob has joined #openstack-meeting-317:02
*** sridhar_ram has quit IRC17:02
thinrichsWe'll get started as usual with status updates.17:02
thinrichs#topic status17:02
*** openstack changes topic to "status (Meeting topic: CongressTeamMeeting)"17:02
thinrichsalexsyip: want to start?17:02
*** puranamr has joined #openstack-meeting-317:02
thinrichsmasahito: how about you?17:03
alexsyipI was working a bit on the tempest tests, but have been working on something else for a little while.17:03
*** john-a-joyce has quit IRC17:03
alexsyipI want to return to working on HA this week.17:03
thinrichsmasahito: hang on—alexsyip is here17:03
thinrichsalexsyip: that patch to get the python client into global requirements hasn't merged.17:04
alexsyipyeah I saw that.17:04
thinrichsIt got a +2 and then someone else changed the line above ours, and so there was a merge conflict.17:04
alexsyipAre you just waiting for a code review?17:05
alexsyipMaybe you can prod someone on IRC to do a quick review.  You need two reviews.17:05
thinrichsYep.  For everyone else… we were trying to get the tempest tests working, but the congress-python client wasn't getting installed.17:05
thinrichsSo we tried adding it to the requirements.txt to see if the tempest tests would start running properly in gate.17:06
alexsyipI’m going to take a shot when we finally get the tempest test working again.17:06
thinrichsBut the client wasn't on the approved requirements list, so it failed.17:06
thinrichsNow we're waiting on getting the client approved to the requirements list.  In the meantime we should be trying to figure out how to get the client installed with devstack properly.17:07
thinrichsalexsyip: I'm not even sure who to ping.17:07
thinrichsMaybe infra?17:07
thinrichsOr is that the TC?  Anyone know?17:07
alexsyipYeah, I would try that IRC room first.17:07
alexsyipinfra would know who needs to review it.17:08
thinrichsI'll work on that again today.17:08
thinrichs#action thinrich will work on getting python-congressclient approved for general-requirements17:08
thinrichsalexsyip: anything else?17:09
alexsyipNo, not much this week.17:09
*** praveens has joined #openstack-meeting-317:09
thinrichsmasahito: want to give a status update?17:10
masahitoI pushed unit tests of api directory.17:10
*** amotoki has joined #openstack-meeting-317:11
masahitoI'll make a patch to correct nova:host datasources17:11
thinrichsmasahito: those were great tests!  Much better coverage than we previously had.17:12
masahitoThe table doesn't show host information now. It only shows nova service list.17:12
*** john_a_joyce has joined #openstack-meeting-317:12
thinrichsmasahito: sounds good17:13
thinrichsmasahito: need anything from us?17:13
masahitothinrichs: thanks. I found some strange behavior in responses, so I'll also patch it.17:14
masahitoeverything is now ok.17:14
thinrichsIt'd be great if you could file a bug for those so it's easy to see what problems you're fixing.17:14
thinrichsmasahito: the other thing we talked about in #congress after last week's meeting was a mid-cycle code sprint.17:15
thinrichsmasahito: want to summarize for everyone what we discussed?17:15
masahitook. I try it.17:16
masahitowe discussed mid-cycle code sprint which foucus to add scaling-out features to congress.17:18
*** sdake has quit IRC17:19
*** sdake_ has joined #openstack-meeting-317:19
*** peristeri has joined #openstack-meeting-317:19
masahitofirst of all, I think we seems to change DSE to using RPC to get scaling feature.17:20
*** matrohon has quit IRC17:21
masahitoMy idea is that we'll disscous the details of the change and write code of it in the code sprint.17:22
thinrichsHow does that sound to everyone?17:23
thinrichsalexsyip: pballand: ping17:24
*** rushiagr is now known as rushiagr_away17:25
alexsyipI’m in favor of replacing the DSE bus.17:25
thinrichsalexsyip: I am in favor of augmenting the functionality of our message bus to work both within the process and outside the process.17:26
thinrichsIt would be good to make the bus work fast within the process, which DSE is fine at.17:27
thinrichsBut I don't care if we keep DSE itself and add inter-process messages, or we replace DSE entirely (as long as messages within the same process are fast).17:27
pballandthinrichs: hey - sorry17:27
alexsyipIf we switch to using RPC for same-machine communication, the server will benefit by having multiple processes.17:27
pballandI’m also in favor of replacing DSE17:28
thinrichsalexsyip: good point17:28
alexsyipI don’t think there’s much cost to using RPC over the shared queue in a single process.17:28
alexsyipUsing RPC will require us to manage two processes though.  Today there is just one process to manage.17:28
pballandlong-term, scaling out is the necessary path, so going RPC makes sense17:29
pballandagree that there should be minimal overhead for in-process RPC17:29
thinrichsWould it make sense to use RPCs to have multiple DSEs communicate?17:29
thinrichsThat is, put one DSE in one process and another DSE in another process (or on a different box), and use RPC to communicate?17:30
thinrichsWe might be able to implement that by adding a new DSE node to each of the DSEs.17:30
pballanddon’t care wheter we call it DSE, but each process needs a message bus and an broker17:30
thinrichsThose new DSE nodes just happen to get their data over RPC/HTTP/whatever.17:30
alexsyipsplitting out every DSE process will require even more management.17:30
thinrichsOk.  Seems there's a lot to consider here.17:31
alexsyipMaybe it wouldn’t be that bad.17:31
pballandsuggest we keep multiple greenthreads communicating over bus in a single process, but add broker to external processes17:31
alexsyipOne process for each driver, and one process for each policy engine.17:31
*** mwang2 has quit IRC17:31
thinrichsIs a mid-cycle sprint the right way to come to agreement and get the code written?17:31
pballandthat allows single-process runtime in the simple case17:32
pballandthinrichs: that makes sense to me17:32
*** john-a-joyce has joined #openstack-meeting-317:32
alexsyipthinrichs: do you mean a summit?17:34
thinrichsalexsyip: yep but in the middle of the cycle with just the Congress team17:34
alexsyipYes, I think we can make a decision there.17:34
thinrichs1-2 days where we huddle around the whiteboard, get the design ironed out, and hopefully even get the code written17:34
thinrichsSo we'll need to figure out logistics: where and when.  Let's do that via the mailing list.17:35
thinrichsAnyone want to spearhead the logistics?17:35
*** john_a_joyce has quit IRC17:36
*** yamahata has joined #openstack-meeting-317:36
*** Piet has quit IRC17:36
masahitofor the change?17:36
*** jaypipes has joined #openstack-meeting-317:37
thinrichsmasahito: to email the list, guage interest, figure out where and when to host it17:37
thinrichsok.  I'll take care of it.17:38
thinrichs#action thinrichs will email the ML to ask about the mid-cycle code sprint17:39
thinrichsrunning a bit short on time.17:39
thinrichspballand: status update?17:39
*** vnod has joined #openstack-meeting-317:39
pballandnot much to report - one bug fix out for review17:40
pballandhave a +2, just trying to get devstack to work (again) before pushing17:40
pballandworking on API validation17:41
pballandthat’s it for me17:41
thinrichsIf anyone wants to take a look at that code, do it soon.  We'll push it in in the next day or two.17:41
thinrichspballand: thanks.17:41
*** sridhar_ram has joined #openstack-meeting-317:42
thinrichsI'll do a quick status update.17:42
thinrichsI was looking at the datasource driver code and had a quick question.17:42
*** yamamoto_ has quit IRC17:42
thinrichsWhen translating an API result into tables using our translator-language, do we have the ability to pass a function that returns an ID for an object?17:43
*** praveens has quit IRC17:43
*** natorious is now known as zz_natorious17:43
thinrichsI didn't see one, so I was thinking about adding it.17:44
thinrichsAny reason not to?  alexsyip17:44
*** jpomero has joined #openstack-meeting-317:45
alexsyipDoes extract-fn work?17:45
thinrichsNot sure.  Maybe I missed that.17:45
thinrichsDoes that only apply when extracting a Value?17:46
alexsyipextract-fn operates on a single value17:47
alexsyipSo if the object is a dict, extract-fn would operate on obj[‘fieldname’]17:47
alexsyipDo you want something that operates on obj or obj[‘fieldname’] ?17:47
thinrichsSomething that operates on obj17:47
*** puranamr has quit IRC17:47
alexsyipDoes obj also have other fields ?17:48
alexsyipthat you want to extract ?17:48
thinrichsI basically want to construct the ID for the object as the combination of some of its fields.17:48
alexsyipI don’t think extract-fn would apply then.17:48
thinrichsThat was my take too.17:48
alexsyipIt makes sense to add something else then.17:49
thinrichsOk.  Just wanted to make sure I wasn't missing something.17:49
thinrichsBack to my status report.17:49
*** praveens has joined #openstack-meeting-317:49
thinrichsI'm planning to start working on look at integrating Congress with CloudFoundry.17:50
thinrichsI have no clue what is involved with that, so it'll be exploratory for sure.17:50
thinrichsBy 'integrating' I mean integrating proactive enforcement...17:51
thinrichsso that API calls into CloudFoundry can be gated on Congress.17:51
*** sridhar_ram1 has joined #openstack-meeting-317:51
thinrichsThe other thing that's happening next week is a 15 minute video Congress update.17:52
*** ivar-lazzaro has joined #openstack-meeting-317:52
*** puranamr has joined #openstack-meeting-317:52
thinrichsFrom what I understand, all the PTLs are doing it.  We're all being scheduled.17:52
thinrichsWe're supposed to focus on the upcoming features for Liberty.17:53
thinrichsI figured a 2 minute overview, followed by an update would be good.17:53
thinrichsHere is the list of things that people have signed up for and that I think we should be doing.17:53
*** sridhar_ram has quit IRC17:53
thinrichs◦Reactive enforcement (protection, action-listing, more interface implementations)17:54
thinrichs◦HA, performance17:54
thinrichs◦Delegation (to Keystone), Cloudfoundry: https://blueprints.launchpad.net/congress17:54
thinrichs◦datasource rule contribs: https://blueprints.launchpad.net/congress/+spec/datasource-rule-contributions17:54
thinrichs◦oslo.messaging https://blueprints.launchpad.net/congress/+spec/integrate-oslo-messaging17:54
thinrichsThe oslo.messaging one conceptually includes our discussion about DSE earlier in the meeting.17:54
*** s3wong has joined #openstack-meeting-317:55
thinrichsThe datasource rule contribs blueprint is not really worth mentioning, I suppose, since it's so low-level compared to the others.17:55
*** VW has quit IRC17:55
thinrichsThe Delegation one is the biggest questionmark.17:55
*** mwang2 has joined #openstack-meeting-317:56
*** puranamr has quit IRC17:56
thinrichsPerhaps that should be called 'Integration with other systems'.17:56
*** puranamr has joined #openstack-meeting-317:56
thinrichsIs there anything else we should include on the list?17:56
*** sridhar_ram has joined #openstack-meeting-317:57
*** sridhar_ram1 has quit IRC17:58
*** baoli_ has quit IRC17:59
*** VW has joined #openstack-meeting-317:59
thinrichsOkay, we're out of time.  If there are features missing from that list that we should highlight, let me know.17:59
thinrichsThanks all!18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Tue Jun 16 18:00:04 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/congressteammeeting/2015/congressteammeeting.2015-06-16-17.01.html18:00
*** puranamr has quit IRC18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/congressteammeeting/2015/congressteammeeting.2015-06-16-17.01.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/congressteammeeting/2015/congressteammeeting.2015-06-16-17.01.log.html18:00
*** VW has quit IRC18:00
*** baoli_ has joined #openstack-meeting-318:00
*** puranamr has joined #openstack-meeting-318:01
*** VW has joined #openstack-meeting-318:01
*** thinrichs has left #openstack-meeting-318:01
*** masahito has left #openstack-meeting-318:01
*** matrohon has joined #openstack-meeting-318:01
*** puranamr has quit IRC18:03
*** praveens has quit IRC18:03
*** praveens has joined #openstack-meeting-318:04
*** sridhar_ram has quit IRC18:05
*** sridhar_ram has joined #openstack-meeting-318:07
*** lazy_prince has quit IRC18:07
*** wojdev has joined #openstack-meeting-318:09
*** mattgriffin has joined #openstack-meeting-318:10
*** sarob has quit IRC18:12
*** john-a-joyce has quit IRC18:13
*** coolsvap is now known as coolsvap|afk18:16
*** sarob has joined #openstack-meeting-318:16
*** wojdev has quit IRC18:20
*** sarob has quit IRC18:22
*** john_a_joyce has joined #openstack-meeting-318:22
*** banix has joined #openstack-meeting-318:27
*** puranamr has joined #openstack-meeting-318:29
*** banix_ has joined #openstack-meeting-318:30
*** praveens has quit IRC18:32
*** banix has quit IRC18:32
*** banix_ is now known as banix18:32
*** tpatil has joined #openstack-meeting-318:33
*** puranamr has quit IRC18:34
*** Sukhdev has joined #openstack-meeting-318:34
*** vnod has quit IRC18:40
*** wojdev has joined #openstack-meeting-318:44
*** b3nt_pin is now known as beagles18:45
*** terrylhowe has joined #openstack-meeting-318:46
*** e0ne has joined #openstack-meeting-318:47
*** amotoki has quit IRC18:49
briancurtin#startmeeting python-openstacksdk19:00
openstackMeeting started Tue Jun 16 19:00:15 2015 UTC and is due to finish in 60 minutes.  The chair is briancurtin. 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: python-openstacksdk)"19:00
openstackThe meeting name has been set to 'python_openstacksdk'19:00
briancurtinif you're here for the SDK meeting, say hi19:00
*** tqtran is now known as tqtran_afk19:01
*** tqtran_afk is now known as tqtran19:01
*** mrunge_ has joined #openstack-meeting-319:01
briancurtin#topic Expose 'get_x_openstack_request_id' method in all OpenStack clients api bindings19:01
*** openstack changes topic to "Expose 'get_x_openstack_request_id' method in all OpenStack clients api bindings (Meeting topic: python-openstacksdk)"19:01
tpatil#link: https://blueprints.launchpad.net/python-openstacksdk/+spec/expose-get-x-openstack-request-id19:02
briancurtinso tpatil first thing with this is that we dont work on any of the projects you listed19:02
briancurtinso we can maybe do something about this within SDK, but you'd have to talk to those projects to get them to do anything about it19:02
tpatilin the last meeting, Doug suggested to talk with SDK team to get this done in the python-*clients.19:02
briancurtinyeah that's not us19:02
*** mrunge_ has quit IRC19:03
briancurtintpatil: for example, if you want python-cinderclient changed, you'll have to talk to the cinder team19:03
terrylhowebest I can think is the last request id gets saved in the session19:03
*** wojdev has quit IRC19:03
tpatilwe want to add this support to all clients, so do you recommend we should talk with all respective team to get this job done.19:04
briancurtintpatil: yes19:04
terrylhoweyou could tslk to us as well though19:04
tpatilok,I will do that. Thanks.19:04
briancurtintpatil: i mean we can do this for OpenStack SDK, but if you want other projects changed you'll have to talk to them19:05
etoewswe're a pretty good starting point though19:05
tpatilOk, Let me explain19:05
tpatilright now, X-openstack-request-id is not returned by the client to the caller.19:05
*** mrunge has quit IRC19:06
tpatilIf X-openstack-request-id is available with the user, it will be easy for the service provider to trace any issue by looking at the log messages and respond user quickly with appropriate reasoning19:06
*** yamahata has quit IRC19:06
briancurtintpatil: yep, i read the blueprint, and we can do that in our project, but it doesn't seem to be the one you're actually looking for19:06
*** john_a_joyce has quit IRC19:07
tpatilbraincurtin: To get this started, what do you recommend we should be doing?19:07
briancurtintpatil: i would start by talking to the projects that you would like to have modified19:07
*** puranamr has joined #openstack-meeting-319:09
tpatilbriancurtin: Ok, I will create blueprint for each of the project and talk with the team individually then.19:09
briancurtintpatil: sounds good. we'll keep an eye on the one you submitted and can probably add the feature fairly easily. we already had something similar logging transaction ids for object storage19:09
briancurtin#topic Roadmap to 1.019:10
*** openstack changes topic to "Roadmap to 1.0 (Meeting topic: python-openstacksdk)"19:10
briancurtin#link https://etherpad.openstack.org/p/sdk_road_to_1.019:10
openstackLaunchpad bug 1465817 in OpenStack SDK "Provide method to get latest request id" [Undecided,New]19:10
terrylhoweso it is tracked19:10
*** sridhar_ram has quit IRC19:10
briancurtintpatil: ^19:10
briancurtinin order to keep track of all of the things we're planning on doing, and making sure they get done, i started throwing together all of the things I think we want to get nailed down in order to call ourselves a 1.019:11
tpatilbriancurtin: sounds good. I will follow up with this bug19:11
briancurtinif anyone has stuff to add, feel free. it's mostly a topic list for right now, and then we can talk about prioritizing once we have everything on the table19:11
tpatilI will include all projects to this bug and start submitting patches, is that ok?19:12
terrylhoweI plan to be done with the functional tests this week.  Of course it will take a little while to work thought the pipe19:12
terrylhowesure thing tpatil thanks19:12
*** sridhar_ram has joined #openstack-meeting-319:13
etoewsdo we also want to start taking the steps towards becoming part of the "big tent"?19:13
*** sdake_ is now known as sdake19:13
tpatilterrylhowe: Good, thanks19:13
briancurtinetoews: is tehre any good reading on what that actually means?19:13
etoewsi was going to go have a look for that right now.19:14
briancurtini know the repo changes from stackforge to openstack but i couldnt care less about that19:14
terrylhoweas far as big tent, I’d like to see some POC first probably starting with OSC19:15
*** sdake has quit IRC19:15
terrylhoweOnce I get the functional tests done, I should be free to try something19:15
etoewsbriancurtin: i know it's not a big deal to you but it's a visibility thing for the project.19:15
*** arunrajan has joined #openstack-meeting-319:15
*** sdake has joined #openstack-meeting-319:16
etoewswhat i've found so far #link http://governance.openstack.org/reference/new-projects-requirements.html19:16
briancurtinetoews: i can put aside my non-caring for governance if it actually matters, but i guess i just havent seen that it does19:16
*** arunrajan has left #openstack-meeting-319:16
*** Rockyg has joined #openstack-meeting-319:16
etoewsimo, it's just one piece of the puzzle. is it an absolute necessity? probably not but i think it would be good to have that piece for a more complete picture.19:19
briancurtinterrylhowe: one thing i'm going to start hacking on soon is building support into Ansible that uses SDK instead of pyrax. i had talked to jesse keating a bit after our talk at the summit and he wants to see that as well (i think he's the maintainer of ansible openstack/rackspace support)19:19
etoews the more important stuff is what's on the roadmap.19:20
terrylhoweansible would be a good one briancurtin19:20
etoewsbriancurtin: is that a pre or post 1.0 thing?19:21
etoewsanything that gets used in ansible should be a priority to be functional tested.19:22
briancurtinetoews: pre, at least to see where we're at so we build a nice 1.0 beyond building it based on the toy-ish apps we've been using to test out apis and whatnot19:22
briancurtinand yeah, should be functionally tested19:22
terrylhoweI guess as a final step to the functional tests, I need to finish up generalizing them so they can run in many environments19:23
briancurtinonce we get caught up on functional tests, any code change should require both unit and functional tests. and docs too, so those don't lag behind either19:23
*** absubram has joined #openstack-meeting-319:24
etoewsshould we take a stab at prioritizing the work in the roadmap?19:25
briancurtinterrylhowe: i wonder if we can setup a coverage job to compare functional tests to the proxies?19:25
terrylhowethat would be nice, no idea how to do that19:26
briancurtinetoews: is everything in that list that you all want to have prioritized?19:26
terrylhowesome things are not going to be practical for automated tests19:26
briancurtinI just threw what I know and want to see worked on19:26
briancurtinAnd now I'm on mobile because my home internet is flaking out...19:27
briancurtinterrylhowe: which things?19:27
terrylhowesome operations might be too difficult to functional test, like will we have an instance big enough to fire up a database for example19:28
terrylhoweI’m not sure19:28
etoewsterrylhowe: that's why it will be nice to be able to have it run in many envs, including hp and rackspace.19:30
terrylhoweyes, definitely19:30
terrylhowepart of the config I’d like to have for the tests is enable/disable for some tests19:30
etoewshaving a full public cloud behind it will make doing more complicated/intensive things easier than with devstack.19:30
briancurtinetoews terrylhowe as for prioritizing things, my first thought was to turn that list into launchpad bugs targeted at 1.0 and just use the importance categories. then if you're going to work on one, assign it to yourself -- we haven't been using assignments or importance very much19:30
*** yamamoto has joined #openstack-meeting-319:31
terrylhowesounds good briancurtin19:31
terrylhoweI find the bugs easier to go through than blueprints19:31
terrylhoweatm we don’t have too many relatively19:31
briancurtini'm going to look up how we can switch to numbered milestones instead of the names, and keep the niceties that doug mentioned about the release script closing out bugs and whatnot19:33
briancurtinthat'll make this stuff easier to track to match up with versions we're actually releasing19:33
*** puranamr has quit IRC19:33
*** yamamoto has quit IRC19:36
*** sankarshan_ is now known as sankarshan_away19:38
briancurtinterrylhowe: im going to check with -infra if we can just tag a release and go and have it just work fine. this should probably be 0.6 since we've changed a bunch of names around. is there anything else we want to get in there?19:39
briancurtinone more renaming that i might want to squeeze in is volume to block_store (https://review.openstack.org/#/c/190233/) but it's in a merge conflict so i'll adjust it right after this19:40
briancurtinwe still have the keystore/keymanager/keywhatever to think about as well19:41
terrylhoweyeh I was about to mention keymanager19:41
terrylhoweand maybe https://bugs.launchpad.net/python-openstacksdk/+bug/146581319:41
openstackLaunchpad bug 1465813 in OpenStack SDK "Neutron docs say router:external by implementations use router_type" [Undecided,New]19:41
terrylhowewrong thing there19:41
terrylhoweI meant https://review.openstack.org/#/c/188622/19:41
*** john_a_joyce has joined #openstack-meeting-319:41
briancurtinyep, etoews that one's good, just needs an update ^19:42
etoewsi'm trying to figure out what the hell i did there and why it's in merge conflict.19:43
etoewsi think i based it on another branch of mine but i haven't tracked that other branch down yet.19:44
etoewsi'll figure it out right after this.19:44
terrylhowenot all of that is required and most other things can wait I think19:45
*** jgrimm is now known as zz_jgrimm19:46
briancurtinterrylhowe: what should we do on key manager? im not really worried about consistency with what other things call this type of thing when we have to worry about we call everything else in the openstack space19:46
*** tmorin has joined #openstack-meeting-319:48
etoewswith the rename of the project...it that just for python packaging or are we renaming the git repo and launchpad site too?19:48
terrylhoweI’m flexible on the key-manager vs key-management thing19:48
briancurtinetoews: just the PyPI package name for right now. it might make sense to rename the git repo but i would just save that for if we ever have to move the git repo, such as under /openstack19:49
briancurtinterrylhowe: key_management follows that projects.yaml file, but it still reads fine as "the key manager service". i don't love key_manager but it's not really confusing anything by having it19:50
terrylhowein the context of git, I think it makes some sense to have python-19:50
*** krtaylor has quit IRC19:50
briancurtinas long as its clearly identifiable what the service is, and it's not a code name, and it's at least very close to formal definitions of what the thing is, it's probably fine19:51
etoewsmy preference is to go with naming similar to what's in https://github.com/openstack/governance/blob/master/reference/projects.yaml19:53
briancurtinetoews: we started with key_manager as requested by doug from barbican, but i suggested key_management per that file and terry updated it, but doug then -1'ed that change set19:54
etoewsit's the closest thing we have to a source of truth19:55
briancurtinetoews: https://review.openstack.org/#/c/187716/19:55
*** mattgri__ has joined #openstack-meeting-319:55
etoewsi guess we can see if doug wants to update projects.yaml...19:56
etoewsotherwise it just inconsistent for no good reason19:56
*** jcoufal has joined #openstack-meeting-319:57
terrylhowesounds reasonable to me19:57
briancurtinyeah. if we're creating this to give people consistency, we really should stick with it. if we have to concede this isn't the end of the world in a naming sense, so it's not terrible, but i'll follow up there19:57
*** mattgriffin has quit IRC19:59
*** julim has quit IRC20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:01
openstackMeeting ended Tue Jun 16 20:01:17 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/python_openstacksdk/2015/python_openstacksdk.2015-06-16-19.00.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2015/python_openstacksdk.2015-06-16-19.00.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/python_openstacksdk/2015/python_openstacksdk.2015-06-16-19.00.log.html20:01
*** mattgri__ has quit IRC20:01
*** krtaylor has joined #openstack-meeting-320:02
*** mattgriffin has joined #openstack-meeting-320:02
*** sridhar_ram1 has joined #openstack-meeting-320:06
*** baoli_ has quit IRC20:07
*** john_a_joyce has quit IRC20:07
*** sridhar_ram has quit IRC20:08
*** tpatil has quit IRC20:08
*** mattgriffin has quit IRC20:09
*** mwang2 has quit IRC20:10
*** krtaylor has quit IRC20:14
*** sdake_ has joined #openstack-meeting-320:16
*** julim has joined #openstack-meeting-320:18
*** zz_natorious is now known as natorious20:19
*** mattgriffin has joined #openstack-meeting-320:19
*** sdake has quit IRC20:20
*** jcoufal has quit IRC20:23
*** natorious is now known as zz_natorious20:24
*** krtaylor has joined #openstack-meeting-320:27
*** ajmiller_ has joined #openstack-meeting-320:27
*** zz_natorious is now known as natorious20:28
*** radek_ has quit IRC20:30
*** ajmiller has quit IRC20:31
*** mattgriffin has quit IRC20:32
*** puranamr has joined #openstack-meeting-320:34
*** Sukhdev has quit IRC20:34
*** mwang2 has joined #openstack-meeting-320:37
*** banix has quit IRC20:38
*** puranamr has quit IRC20:38
*** lblanchard has quit IRC20:40
*** mattgriffin has joined #openstack-meeting-320:42
*** mattgriffin has quit IRC20:42
*** VW has quit IRC20:47
*** VW has joined #openstack-meeting-320:47
*** sridhar_ram1 is now known as sridhar_ram20:48
*** tqtran is now known as tqtran_afk20:51
*** kztsv_mbp has joined #openstack-meeting-320:52
*** e0ne has quit IRC20:53
*** sridhar_ram has quit IRC21:00
*** banix has joined #openstack-meeting-321:01
*** puranamr has joined #openstack-meeting-321:01
*** mrmartin has quit IRC21:01
*** pshige has joined #openstack-meeting-321:03
*** peristeri has quit IRC21:04
*** sridhar_ram has joined #openstack-meeting-321:04
*** tqtran_afk is now known as tqtran21:16
*** VW has quit IRC21:21
*** julim has quit IRC21:21
*** persia has quit IRC21:23
*** persia_ has joined #openstack-meeting-321:24
*** persia_ has quit IRC21:24
*** sarob has joined #openstack-meeting-321:24
*** singlethink has joined #openstack-meeting-321:24
*** persia has joined #openstack-meeting-321:25
*** puranamr has quit IRC21:26
*** puranamr has joined #openstack-meeting-321:27
*** singleth_ has quit IRC21:28
*** singlethink has quit IRC21:29
*** zz_jgrimm is now known as jgrimm21:29
*** vnod has joined #openstack-meeting-321:32
*** fallenpegasus has quit IRC21:32
*** puranamr has quit IRC21:34
*** tmorin has quit IRC21:36
*** VW has joined #openstack-meeting-321:46
*** pballand has quit IRC21:52
*** shwetaap has joined #openstack-meeting-321:59
*** sdake_ is now known as sdake22:02
*** ivar-laz_ has joined #openstack-meeting-322:06
*** ivar-lazzaro has quit IRC22:10
*** bknudson has quit IRC22:13
*** jckasper has quit IRC22:16
*** alexpilotti has quit IRC22:21
*** persia has quit IRC22:23
*** 21WACGOA9 has joined #openstack-meeting-322:25
*** pballand has joined #openstack-meeting-322:25
*** jgrimm is now known as zz_jgrimm22:28
*** ajmiller_ is now known as ajmiller22:30
*** 21WACGOA9 is now known as persia22:30
*** persia has quit IRC22:31
*** persia has joined #openstack-meeting-322:31
*** sridhar_ram has quit IRC22:31
*** banix has quit IRC22:32
*** sridhar_ram1 has joined #openstack-meeting-322:35
*** pballand has quit IRC22:35
*** armax has quit IRC22:37
*** puranamr has joined #openstack-meeting-322:38
*** cbader has quit IRC22:44
*** puranamr has quit IRC22:46
*** Swami has quit IRC22:50
*** sridhar_ram1 is now known as sridhar_ram22:54
*** ivar-laz_ has quit IRC22:58
*** ivar-lazzaro has joined #openstack-meeting-322:58
*** VW has quit IRC22:59
*** puranamr has joined #openstack-meeting-322:59
*** puranamr has quit IRC23:02
*** carl_baldwin has quit IRC23:05
*** puranamr has joined #openstack-meeting-323:09
*** matrohon has quit IRC23:09
*** puranamr has quit IRC23:11
*** sdague has quit IRC23:12
*** yamamoto has joined #openstack-meeting-323:22
*** sdague has joined #openstack-meeting-323:24
*** mwang2 has quit IRC23:24
*** Rockyg has quit IRC23:26
*** yamamoto has quit IRC23:26
*** tqtran has quit IRC23:27
*** aleksandr_null has quit IRC23:28
*** tqtran has joined #openstack-meeting-323:28
*** aleksandr_null has joined #openstack-meeting-323:30
*** absubram has quit IRC23:31
*** yamamoto has joined #openstack-meeting-323:32
*** yamamoto has quit IRC23:34
*** natorious is now known as zz_natorious23:35
*** sigmavirus24 is now known as sigmavirus24_awa23:42
*** stevemar has quit IRC23:44
*** stevemar has joined #openstack-meeting-323:44
*** puranamr has joined #openstack-meeting-323:52
*** ajmiller has quit IRC23:53
*** puranamr has quit IRC23:56
*** puranamr has joined #openstack-meeting-323:56

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