Thursday, 2015-03-19

cyeoho/00:01
elmikoanyone here for api-wg?00:01
elmikohehe00:01
*** alexpilotti has quit IRC00:01
elmikocyeoh: haven't started yet, etoews said he couldn't make it00:01
elmikowas looking for someone to start the meeting00:01
*** jrist has joined #openstack-meeting-300:02
cyeohok I'm just logging in to everything etc, but will start the meeting00:02
cyeoh#startmeeting00:02
openstackcyeoh: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'00:02
elmikook, cool00:02
cyeoh#startmeeting nova api wg00:02
openstackMeeting started Thu Mar 19 00:02:32 2015 UTC and is due to finish in 60 minutes.  The chair is cyeoh. Information about MeetBot at http://wiki.debian.org/MeetBot.00:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.00:02
*** openstack changes topic to " (Meeting topic: nova api wg)"00:02
openstackThe meeting name has been set to 'nova_api_wg'00:02
elmikoso far i think it's just you and i00:02
*** alexpilotti has joined #openstack-meeting-300:02
cyeohah ok big meeting then :-)00:02
cyeohsince there is just the two of us on what is the most important thing on your mind?00:03
*** alexpilotti has quit IRC00:03
*** yamamoto has joined #openstack-meeting-300:04
*** rolandchan has quit IRC00:04
elmikohmm00:04
elmikonothing big api-wise for me this week00:04
elmikobiggest issue for sahara team atm is the api-ref wadl stuff00:04
*** alexpilotti has joined #openstack-meeting-300:04
elmikobut i think we've got it under control00:05
elmikohow about you?00:05
cyeohstandardisation-wise probably just project-client issues because I'm trying to get a new novaclient out that we can use microversions00:06
*** alexpilotti has quit IRC00:06
elmikodo you have a review to link?00:06
cyeohbut most of it at this stage is primarily making it up as i go along as we'll see how it works - since its all a bit new00:06
elmikoah, ok00:06
cyeohhttps://review.openstack.org/#/c/152569/1700:07
* elmiko looks00:07
cyeohthat one is andrew's. Im planning on splitting it up into smaller changesets to make it easier to review (eg - some for cleanup first etc) and then a series of small patches that only add a bit of functionality at a time00:08
elmikonice00:08
elmikothe microversion stuff is represented all throught header?00:08
cyeoheg since we have 2 API implementations and theoretically 4 apis need to be able to select them from novaclient00:08
cyeohyes, so its all gets boiled down to one header. Whether its there or not and then what its value is00:09
elmikoand the major version part is represented in the uri?00:09
*** wojdev has quit IRC00:09
cyeohcurrently it does, but in the future we will be moving away from that and it will be solely header dependent00:10
cyeohhttps://etherpad.openstack.org/p/novaclient_microversions_design00:11
*** SumitNaiksatam has quit IRC00:11
elmikoah, thanks00:11
cyeohthis is a bit of a high level look I've been working on00:11
elmikoi don't have a strong opinion on the version in header vs in uri, but it seemed to draw out a good conversation00:12
cyeohwe do want to move url discovery out of keystone (eg no more compute and computev3 etc00:12
elmikonice00:12
*** mrmartin has quit IRC00:12
cyeohyea there are lots of opinions out there - but with microversions and lots of version bumping putting versions in the url path would be a lot of overhead for clients eventually00:13
elmikoyea00:13
cyeohso is the api-ref wadl for sahara intended to be automated?00:15
elmikounfortunately no00:15
cyeohbackground goal for us in Nova is automation of api ref docs.00:15
cyeohah ok.00:15
elmikoi'd like to work towards automation as well, but i don't think wadl is the format for it00:15
elmikoi've been investigating swagger a bunch with our codebase and the barbican code00:16
elmikothe wadl in api-ref seems like it needs a bunch of hand tweaking to really get it thorough00:16
elmikoi think a big issue with automation across the board will be projects that use pecan00:17
cyeohyea and soon as manual intervention is required we get errors.00:17
elmikoright, plus the maintenance costs00:18
elmikoi think a good step would be partial automation to start with00:18
elmikobut i think the doc team doesn't want full automation, with good reason00:18
*** absubram has joined #openstack-meeting-300:18
cyeohyea I'm happy with that. I just want things like paramter names/types automated. Still found those sorts of errors just 2-3 months ago00:19
*** badveli has quit IRC00:19
elmikoagreed00:19
elmikoit'll be interesting to see where this goes00:20
elmikoi feel like the swagger json format is much more friendly to interact with than the wadl xml00:20
elmikoso you could generate a skeleton, and fill in the details00:20
cyeohBoo to XML!00:20
elmikohehe00:21
cyeohyep sounds like we could still reverify ocassionally too so an updated skeleton still fits what we publish00:22
elmikoright00:22
cyeohand we don't have doco for features which actually don't exist anymore :-)00:22
elmikoexactly00:23
elmikoi have a feeling next meeting we will discuss meeting times ;)00:24
cyeohmeeting times are hard :-(00:25
elmikohehe00:25
cyeohthis and the nova api meeting is the only one I have that is NOT between 12am and 6am00:25
elmikoouch00:25
cyeohand I really can't do those sorts of really early times for a while00:25
elmikothankfully i don't have any in that range00:26
cyeohyea I'm fine with the other meeting week moving to a beter US/EU time, but I'd like to keep something that works for Aust/NZ/Asia00:27
elmiko+100:27
*** clu_ has quit IRC00:27
elmikoi'm in the US, where are you at?00:28
cyeohI'm in Adelaide Australia (GMT+10:30)00:28
elmikocool00:28
*** wojdev has joined #openstack-meeting-300:28
cyeohso this time actually works really well ;-)00:29
elmikoyea00:29
elmikoi'm GMT-4 currently, i think00:29
elmikoyea -400:29
cyeohheh my meetings with US people are generally at interesting times for at least one of us00:29
elmikolol, i'll bet00:29
elmikoi wonder how many folks we have from Aust/NZ/Asia who participate in the api-wg00:30
*** pavel_bondar has quit IRC00:30
cyeoha couple from Japan at least, and then at least one from China (but that will probably grow)00:31
*** pavel_bondar has joined #openstack-meeting-300:31
elmikonice00:31
elmikothe sahara team has had a recent influx of folks from asia, it's nice to have more hands onboard =)00:32
*** MarkAtwood has quit IRC00:32
cyeohyea definitely! Sorry just got pinged by my manager so am going to have to go. Will be back later00:33
elmikocyeoh: end the meeting before you go00:34
*** Sukhdev has quit IRC00:34
cyeoh#endmeeting00:35
*** openstack changes topic to "OpenStack Meetings"00:35
openstackMeeting ended Thu Mar 19 00:35:00 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)00:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api_wg/2015/nova_api_wg.2015-03-19-00.02.html00:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api_wg/2015/nova_api_wg.2015-03-19-00.02.txt00:35
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api_wg/2015/nova_api_wg.2015-03-19-00.02.log.html00:35
elmikocyeoh: thanks! later00:35
*** absubram has quit IRC00:36
*** markvoelker has quit IRC00:37
*** elmiko has left #openstack-meeting-300:38
*** e0ne has quit IRC00:38
*** wojdev has quit IRC00:41
*** baoli has quit IRC00:43
*** marun has quit IRC00:45
*** wojdev has joined #openstack-meeting-300:48
*** yamamoto has quit IRC00:53
*** gugl has quit IRC00:55
*** Rockyg has quit IRC00:56
*** isq has quit IRC00:57
*** tqtran has left #openstack-meeting-300:59
*** sbalukoff has quit IRC01:00
*** bknudson has joined #openstack-meeting-301:00
*** Sukhdev has joined #openstack-meeting-301:00
*** absubram has joined #openstack-meeting-301:01
*** wojdev has quit IRC01:05
*** Longgeek has joined #openstack-meeting-301:09
*** isq has joined #openstack-meeting-301:11
*** stendulker has joined #openstack-meeting-301:12
*** markvoelker has joined #openstack-meeting-301:17
*** markvoelker has quit IRC01:22
*** wojdev has joined #openstack-meeting-301:22
*** mwagner_lap has joined #openstack-meeting-301:22
*** s3wong has quit IRC01:26
*** mwagner_lap has quit IRC01:27
*** stendulker has quit IRC01:32
*** stanzgy has joined #openstack-meeting-301:33
*** stanzgy_ has joined #openstack-meeting-301:33
*** Daisy_ has joined #openstack-meeting-301:34
*** Daisy__ has joined #openstack-meeting-301:39
*** mwagner_lap has joined #openstack-meeting-301:40
*** Daisy_ has quit IRC01:42
*** ivar-laz_ has joined #openstack-meeting-301:43
*** ivar-lazzaro has quit IRC01:46
*** wojdev has quit IRC01:47
*** ivar-laz_ has quit IRC01:47
*** isq has quit IRC01:48
*** ChuckC has joined #openstack-meeting-301:49
*** megm_ has joined #openstack-meeting-301:55
*** isq has joined #openstack-meeting-301:55
*** megm has quit IRC01:56
*** marun has joined #openstack-meeting-301:56
*** mwagner_lap has quit IRC01:58
*** SumitNaiksatam has joined #openstack-meeting-302:00
*** marun has quit IRC02:01
*** wojdev has joined #openstack-meeting-302:09
*** mwagner_lap has joined #openstack-meeting-302:11
*** Sukhdev has quit IRC02:11
*** markvoelker has joined #openstack-meeting-302:18
*** vishwanathj has joined #openstack-meeting-302:18
*** reed has quit IRC02:20
*** markvoelker has quit IRC02:23
*** yamahata has quit IRC02:24
*** wojdev has quit IRC02:26
*** sigmavirus24_awa is now known as sigmavirus2402:27
*** baoli has joined #openstack-meeting-302:28
*** bpokorny has quit IRC02:30
*** absubram has quit IRC02:33
*** Poornima has joined #openstack-meeting-302:35
*** shwetaap has joined #openstack-meeting-302:37
*** beagles has quit IRC02:46
*** Guest87543 has joined #openstack-meeting-302:48
*** Yi has quit IRC02:52
*** mrmartin has joined #openstack-meeting-302:55
*** coolsvap|afk is now known as coolsvap03:04
*** stevemar has joined #openstack-meeting-303:08
*** mattgriffin has joined #openstack-meeting-303:11
*** absubram has joined #openstack-meeting-303:12
*** nati_ueno has quit IRC03:27
*** coolsvap is now known as coolsvap|afk03:32
*** Yi has joined #openstack-meeting-303:36
*** stanzgy_ has quit IRC03:37
*** stanzgy has quit IRC03:39
*** stanzgy has joined #openstack-meeting-303:39
*** coolsvap|afk is now known as coolsvap03:39
*** Daisy__ has quit IRC03:40
*** yamamoto has joined #openstack-meeting-303:40
*** Piet has quit IRC03:47
*** mrmartin has quit IRC03:47
*** stendulker has joined #openstack-meeting-303:49
*** VW_ has quit IRC03:49
*** sigmavirus24 is now known as sigmavirus24_awa03:57
*** jckasper has joined #openstack-meeting-303:57
*** sbalukoff has joined #openstack-meeting-304:03
*** Poornima has quit IRC04:08
*** jckasper has quit IRC04:09
*** Poornima has joined #openstack-meeting-304:09
*** baoli has quit IRC04:10
*** lazy_prince is now known as killer_prince04:15
*** Yi has quit IRC04:19
*** markvoelker has joined #openstack-meeting-304:19
*** markvoelker has quit IRC04:24
*** carl_baldwin has joined #openstack-meeting-304:26
*** Sukhdev has joined #openstack-meeting-304:31
*** Yi has joined #openstack-meeting-304:32
*** amotoki has joined #openstack-meeting-304:40
*** Yi has quit IRC04:53
*** Daisy_ has joined #openstack-meeting-305:03
*** yamamoto has quit IRC05:07
*** mattgriffin has quit IRC05:09
*** mattgriffin has joined #openstack-meeting-305:12
*** nati_ueno has joined #openstack-meeting-305:14
*** Daisy_ has quit IRC05:15
*** iymht has joined #openstack-meeting-305:16
*** markvoelker has joined #openstack-meeting-305:20
*** markvoelker has quit IRC05:25
*** armax has quit IRC05:27
*** yamamoto has joined #openstack-meeting-305:32
*** carl_baldwin has quit IRC05:39
*** eghobo has joined #openstack-meeting-305:40
*** coolsvap is now known as coolsvap|afk05:41
*** nati_ueno has quit IRC05:41
*** ChuckC has quit IRC05:45
*** MarkAtwood has joined #openstack-meeting-305:45
*** eghobo_ has joined #openstack-meeting-305:45
*** coolsvap|afk is now known as coolsvap05:48
*** eghobo has quit IRC05:48
*** MarkAtwood has quit IRC05:55
*** shwetaap has quit IRC05:56
*** megm has joined #openstack-meeting-305:57
*** megm_ has quit IRC05:58
*** stevemar has quit IRC06:00
*** Daisy_ has joined #openstack-meeting-306:03
*** sarob has quit IRC06:05
*** jschwarz has joined #openstack-meeting-306:06
*** eghobo_ has quit IRC06:11
*** eghobo has joined #openstack-meeting-306:13
*** killer_prince is now known as lazy_prince06:20
*** markvoelker has joined #openstack-meeting-306:21
*** markvoelker has quit IRC06:26
*** mattgriffin has quit IRC06:28
*** Sukhdev has quit IRC06:31
*** wojdev has joined #openstack-meeting-306:44
*** jcoufal has joined #openstack-meeting-306:53
*** jtomasek has joined #openstack-meeting-306:57
*** wojdev has quit IRC06:58
*** eghobo has quit IRC06:59
*** sarob has joined #openstack-meeting-307:05
*** sarob has quit IRC07:11
*** Yi has joined #openstack-meeting-307:12
*** Yi has quit IRC07:17
*** sergef has joined #openstack-meeting-307:21
*** markvoelker has joined #openstack-meeting-307:22
*** sreshetn1 has joined #openstack-meeting-307:24
*** markvoelker has quit IRC07:26
*** nkrinner has joined #openstack-meeting-307:27
*** sahid has joined #openstack-meeting-307:33
*** scheuran has joined #openstack-meeting-307:33
*** jtomasek has quit IRC07:36
*** Poornima is now known as Poornima_Lunch07:45
*** SumitNaiksatam has quit IRC07:51
*** belmoreira has joined #openstack-meeting-307:53
*** stendulker has quit IRC07:54
*** stendulker has joined #openstack-meeting-307:54
*** flaper87 has quit IRC07:56
*** flaper87 has joined #openstack-meeting-307:56
*** scheuran has quit IRC07:58
*** scheuran has joined #openstack-meeting-307:58
*** mrda is now known as mrda-away07:58
*** safchain has joined #openstack-meeting-308:00
*** zz_ttrifonov is now known as ttrifonov08:02
*** e0ne has joined #openstack-meeting-308:14
*** e0ne has quit IRC08:15
*** matrohon has joined #openstack-meeting-308:17
*** jtomasek has joined #openstack-meeting-308:33
*** pkarikh has quit IRC08:37
*** pkarikh has joined #openstack-meeting-308:39
*** iovadia has joined #openstack-meeting-308:40
*** iovadia has left #openstack-meeting-308:43
*** iymht has quit IRC08:49
*** Poornima has joined #openstack-meeting-308:53
*** marun has joined #openstack-meeting-308:53
*** marun has quit IRC08:58
*** iymht has joined #openstack-meeting-308:59
*** Yi has joined #openstack-meeting-309:01
*** Yi has quit IRC09:06
*** wojdev has joined #openstack-meeting-309:16
*** zz_johnthetubagu is now known as johnthetubaguy09:20
*** markvoelker has joined #openstack-meeting-309:23
*** Longgeek has quit IRC09:27
*** JeanBriceCombebi has joined #openstack-meeting-309:28
*** markvoelker has quit IRC09:28
*** Longgeek has joined #openstack-meeting-309:29
*** Guest87543 is now known as b3nt_pin09:29
*** wojdev has quit IRC09:30
*** Longgeek has quit IRC09:31
*** Longgeek has joined #openstack-meeting-309:37
*** Daisy_ has quit IRC09:40
*** eghobo has joined #openstack-meeting-309:43
*** watanabe_isao has quit IRC09:44
*** eghobo has quit IRC09:47
*** amotoki has quit IRC09:48
*** JeanBriceCombebi has quit IRC09:51
*** yamamoto has quit IRC09:54
*** JeanBriceCombebi has joined #openstack-meeting-309:56
*** megm_ has joined #openstack-meeting-309:59
*** megm has quit IRC10:00
*** absubram has quit IRC10:00
*** iymht has quit IRC10:11
*** Longgeek has quit IRC10:13
*** Longgeek has joined #openstack-meeting-310:13
*** lazy_prince has quit IRC10:17
*** yamamoto has joined #openstack-meeting-310:18
*** e0ne has joined #openstack-meeting-310:23
*** markvoelker has joined #openstack-meeting-310:24
*** killer_prince has joined #openstack-meeting-310:24
*** killer_prince has quit IRC10:24
*** wojdev has joined #openstack-meeting-310:24
*** lazy_prince has joined #openstack-meeting-310:24
*** markvoelker has quit IRC10:29
*** coolsvap is now known as coolsvap|afk10:41
*** stanzgy_ has joined #openstack-meeting-310:46
*** stanzgy has quit IRC10:48
*** Yi has joined #openstack-meeting-310:50
*** stanzgy_ has quit IRC10:51
*** wojdev has quit IRC10:54
*** Yi has quit IRC10:55
*** amotoki has joined #openstack-meeting-311:00
*** jschwarz has quit IRC11:01
*** jaypipes has joined #openstack-meeting-311:04
*** wojdev has joined #openstack-meeting-311:04
*** sergef has quit IRC11:05
*** sambetts has quit IRC11:09
*** stendulker has quit IRC11:09
*** sambetts has joined #openstack-meeting-311:11
*** mattfari_ has joined #openstack-meeting-311:11
*** mattfari_ has quit IRC11:12
*** wojdev has quit IRC11:19
*** mwagner_lap has quit IRC11:21
*** yamamoto has quit IRC11:25
*** markvoelker has joined #openstack-meeting-311:25
*** wojdev has joined #openstack-meeting-311:26
*** sergef has joined #openstack-meeting-311:29
*** markvoelker has quit IRC11:30
*** coolsvap|afk is now known as coolsvap11:36
*** wojdev has quit IRC11:37
*** e0ne is now known as e0ne_11:37
*** wojdev has joined #openstack-meeting-311:42
*** e0ne_ has quit IRC11:42
*** e0ne has joined #openstack-meeting-311:48
*** yamamoto has joined #openstack-meeting-311:50
*** Yi has joined #openstack-meeting-311:51
*** markvoelker has joined #openstack-meeting-311:54
*** sreshetn1 has quit IRC11:56
*** Yi has quit IRC11:56
*** JeanBriceCombebi has quit IRC11:58
*** wojdev has quit IRC12:03
*** mwagner_lap has joined #openstack-meeting-312:07
*** wojdev has joined #openstack-meeting-312:14
*** Longgeek has quit IRC12:20
*** Longgeek has joined #openstack-meeting-312:20
*** wojdev has quit IRC12:24
*** bknudson has quit IRC12:25
*** wojdev has joined #openstack-meeting-312:32
*** e0ne is now known as e0ne_12:33
*** Yi has joined #openstack-meeting-312:33
*** Longgeek_ has joined #openstack-meeting-312:37
*** Longgeek has quit IRC12:41
*** mrmartin has joined #openstack-meeting-312:41
*** wojdev has quit IRC12:42
*** e0ne_ has quit IRC12:43
*** bknudson has joined #openstack-meeting-312:45
*** wojdev has joined #openstack-meeting-312:49
*** lazy_prince has quit IRC12:55
*** killer_prince has joined #openstack-meeting-312:55
*** killer_prince is now known as lazy_prince12:56
*** xuhanp_ has joined #openstack-meeting-313:05
*** xuhanp has joined #openstack-meeting-313:05
*** Poornima has quit IRC13:05
*** Networkn3rd has quit IRC13:10
*** wojdev has quit IRC13:16
*** mrmartin has quit IRC13:17
*** Yi_ has joined #openstack-meeting-313:18
*** igordcard has joined #openstack-meeting-313:18
*** vgridnev_ has joined #openstack-meeting-313:21
*** Yi has quit IRC13:21
*** mrmartin has joined #openstack-meeting-313:21
*** ilyashakhat has quit IRC13:25
*** peristeri has joined #openstack-meeting-313:26
*** e0ne has joined #openstack-meeting-313:27
*** jckasper has joined #openstack-meeting-313:27
*** baoli has joined #openstack-meeting-313:32
*** Yi_ has quit IRC13:34
*** Longgeek_ has quit IRC13:35
*** JeanBriceCombebi has joined #openstack-meeting-313:38
*** nelsnelson has joined #openstack-meeting-313:42
*** sarob has joined #openstack-meeting-313:43
*** mrmartin has quit IRC13:44
*** eghobo has joined #openstack-meeting-313:44
*** Yi has joined #openstack-meeting-313:45
*** stendulker has joined #openstack-meeting-313:45
*** shwetaap has joined #openstack-meeting-313:46
*** sarob has quit IRC13:48
*** VW_ has joined #openstack-meeting-313:52
*** JeanBriceCombebi has quit IRC13:55
*** lblanchard has joined #openstack-meeting-313:57
*** wuhg has joined #openstack-meeting-313:59
*** pkoniszewski has joined #openstack-meeting-314:00
*** lblanchard has quit IRC14:01
*** sigmavirus24_awa is now known as sigmavirus2414:02
*** megm has joined #openstack-meeting-314:02
*** tosky2 has joined #openstack-meeting-314:02
*** megm_ has quit IRC14:02
*** lblanchard has joined #openstack-meeting-314:03
*** lblanchard has quit IRC14:03
*** tosky2 has quit IRC14:04
*** thomasem has joined #openstack-meeting-314:07
*** thomasem has quit IRC14:09
*** thomasem has joined #openstack-meeting-314:09
*** VW_ has quit IRC14:11
*** mattgriffin has joined #openstack-meeting-314:12
*** mattfarina has joined #openstack-meeting-314:12
*** eghobo_ has joined #openstack-meeting-314:13
*** etoews has joined #openstack-meeting-314:14
*** stevemar has joined #openstack-meeting-314:14
*** thangp has joined #openstack-meeting-314:15
*** VW_ has joined #openstack-meeting-314:15
*** eghobo has quit IRC14:16
*** dhellmann has quit IRC14:19
*** dhellmann has joined #openstack-meeting-314:19
*** e0ne is now known as e0ne_14:22
*** e0ne_ is now known as e0ne14:23
*** xuhanp_ has quit IRC14:23
*** xuhanp has quit IRC14:23
*** mrmartin has joined #openstack-meeting-314:25
*** yamamoto has quit IRC14:27
*** jcoufal_ has joined #openstack-meeting-314:29
*** eghobo_ has quit IRC14:29
*** iovadia has joined #openstack-meeting-314:31
*** VW_ has quit IRC14:31
*** jcoufal has quit IRC14:32
*** absubram has joined #openstack-meeting-314:32
*** yamamoto has joined #openstack-meeting-314:33
*** eghobo has joined #openstack-meeting-314:34
*** eghobo has quit IRC14:35
*** saggi1 has joined #openstack-meeting-314:39
*** wojdev has joined #openstack-meeting-314:40
*** baoli has quit IRC14:42
*** baoli has joined #openstack-meeting-314:43
*** sarob has joined #openstack-meeting-314:44
*** baoli has quit IRC14:45
*** VW_ has joined #openstack-meeting-314:45
*** baoli has joined #openstack-meeting-314:47
*** VW_ has quit IRC14:47
*** mrmartin has quit IRC14:48
*** tidwellr has joined #openstack-meeting-314:49
*** sarob has quit IRC14:49
*** timbyr_ has joined #openstack-meeting-314:49
*** timbyr_ has quit IRC14:49
*** MarkAtwood has joined #openstack-meeting-314:50
*** mrunge has quit IRC14:52
*** carl_baldwin has joined #openstack-meeting-314:54
*** lblanchard has joined #openstack-meeting-314:55
*** sarob has joined #openstack-meeting-314:56
*** VW_ has joined #openstack-meeting-314:59
*** mlavalle has joined #openstack-meeting-314:59
*** armax has joined #openstack-meeting-314:59
carl_baldwinhi15:00
mlavallehi15:00
tidwellrhi15:00
pavel_bondarhi15:00
*** pc_m has joined #openstack-meeting-315:00
pc_mhi15:00
haleybhi15:00
carl_baldwin#startmeeting neutron_l315:01
openstackMeeting started Thu Mar 19 15:01:02 2015 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:01
openstackThe meeting name has been set to 'neutron_l3'15:01
carl_baldwin#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:01
*** mrunge has joined #openstack-meeting-315:01
carl_baldwinKilo-3 is today.15:01
carl_baldwin#link https://launchpad.net/neutron/+milestone/kilo-315:02
carl_baldwinrc1 is already being planned.  I’m not sure when the date will be.15:02
carl_baldwin#link https://launchpad.net/neutron/+milestone/kilo-rc115:03
*** wojdev has quit IRC15:03
carl_baldwinIPAM stuff has been moved to rc1.15:03
*** amuller has joined #openstack-meeting-315:04
carl_baldwinAlso, IPv6 router support, report ha router master, and multiple ipv6 prefixes.15:04
carl_baldwinLooks like release candidates begin on April 9th.  That is only 3 weeks away.15:04
carl_baldwin#link https://wiki.openstack.org/wiki/Kilo_Release_Schedule15:05
carl_baldwinAny other announcements?15:05
carl_baldwin#topic neutron-ipam15:06
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:06
*** Networkn3rd has joined #openstack-meeting-315:06
*** mrunge has quit IRC15:06
carl_baldwinpavel_bondar: salv-orlando: tidwellr: ping15:06
tidwellrpong15:06
pavel_bondarpong15:06
pavel_bondarLooks like I hit serious issue with transactions during integration testing15:06
pavel_bondarit may require changing interface15:07
salv-orlandohere15:07
salv-orlandoI spoke about this with pavel_bondar already. He has all the details for making the ipam driver work.15:07
carl_baldwinpavel_bondar: Can you catch the rest of us up?15:08
pavel_bondarok15:08
pavel_bondarIPAM Driver was expected to run in separate db transaction, so it fetch new session and create new db transaction.15:08
pavel_bondarand it works fine in most cases15:08
pavel_bondarbut when some plugin wraps up for example create_port() with transaction, things are breaking15:09
pavel_bondarso ipam driver code is executed inside of existing transaction and create new transaction.15:10
*** qwebirc56132 has joined #openstack-meeting-315:11
*** evgenyf has joined #openstack-meeting-315:11
pavel_bondarI have seen 1k test failures, most of them happened only when create_port is wrapped by transaction on higher level15:11
pavel_bondarafter I made small patch to pass context to ipam driver, test failures count decreased  to ~100 falures15:11
pavel_bondar10x decreasing15:12
salv-orlandobasically the issue is not with the double transaction itself, but with the wrapping mandated by the plugin!15:12
salv-orlandopavel_bondar: that was the bit which was unclear to me15:12
carl_baldwinpavel_bondar: Is that the proposed action to fix the problem?  Pass the context to IPAM and run it in the same transaction?15:13
salv-orlandoso the problem is inheritance15:13
salv-orlandocarl_baldwin: that's the only viable solution if we want to give pluggable ipam to all plugins... however15:13
pavel_bondarcarl_baldwin: yes, for now I see only this solution15:13
*** qwebirc56132 has quit IRC15:13
salv-orlandoit defies a bit the very reason for which we introduced the interface15:13
pavel_bondarcarl_baldwin: because each plugin and a lot of other stuff like floating ip creation wraps db_base method with higher level transaction15:14
salv-orlandopavel_bondar, carl_baldwin: what if we say that plugin that wrap super() calls in a transaction are not compatible with pluggable ipam?15:14
pavel_bondarcarl_baldwin: so we already run inside of another transaction in most cases15:14
carl_baldwinsalv-orlando: “it defies a bit the very reason…”  That is what I was thinking.15:15
carl_baldwinsalv-orlando: What plugins are we talking about that do this wrapping?15:16
*** pkarikh has quit IRC15:16
salv-orlandocarl_baldwin: I think in a way or another several... probably pavel_bondar has the whole list15:16
*** pkarikh has joined #openstack-meeting-315:17
salv-orlandobut from my perspective we might be happy if it works for ml215:17
salv-orlandoand I'm pretty sure ml2 is one of them15:17
salv-orlandoml2 is even worse because it overrides some of the methods we've refactored15:17
salv-orlandoanyway, the conclusion between me and pavel_bondar was that I'd look at this too and seek if we have any viable alternative, like stating that ipam pluggable might be enabled only for some plugin which met certain conditions15:18
carl_baldwinsalv-orlando: I don’t think we can not be compatible with ML2.15:18
salv-orlandoand if you tried to enable it on a plugin which does not met these conditions things are likely to break15:18
salv-orlandoso I was going to try tonight to make at least ML2 compatible with pluggable IPAM and separate transactions15:19
salv-orlandoand then report on the mailing list15:19
pavel_bondaryeah, ml2 indefinitely wraps create_ipam() code in higher-level transaction, and other 3 plugins I have checked do the same.15:19
salv-orlandoIf I fail we'd have to consider doing as pavel_bondar suggests15:19
carl_baldwinsalv-orlando: that sounds like the right thing to do next.  I’d like to jump in and help out if I can but I don’t want to slow you down.15:19
carl_baldwinsalv-orlando: we’ll watch for your report.15:21
salv-orlandocarl_baldwin: I'm very good at slowing down by myself ;)15:22
carl_baldwinsalv-orlando: Another reason for me not to slow you down any more.  ;)15:24
*** ChuckC has joined #openstack-meeting-315:24
carl_baldwinpavel_bondar: What about the other 100 test failures.  Have you started to look in to those?15:24
pavel_bondarcarl_baldwin: part of them comes from floating_ip stuff, but I am just started with them for now, will continue investigation on them15:25
carl_baldwinpavel_bondar: Good.  Keep us posted on your progress.  Is there anything I can help with?15:26
pavel_bondarcarl_baldwin: Sure will keep you posted about the progress. And that is it for me for now, so will continue digging with other tests15:28
carl_baldwinpavel_bondar and salv-orlando:  Thank you.15:28
carl_baldwintidwellr: ping15:28
tidwellrhere15:28
carl_baldwintidwellr: Let me have one more look through https://review.openstack.org/#/c/148698/ .  Hopefully, we can kick it in today.15:29
carl_baldwintidwellr: I might need to get another devstack running and try it out with the client modificatinos.15:29
carl_baldwin*modifications15:29
carl_baldwintidwellr: Has this one run through the new tempest tests?15:30
tidwellrcarl_baldwin: no, and it needs to15:30
*** VW_ has quit IRC15:30
tidwellrthat's my task for the day15:31
tidwellrcarl_baldwin: I've also done some iterations on https://review.openstack.org/#/c/157597, I don't see a corresponding client patch though15:32
tidwellrmay need to get that started15:32
tidwellrand then https://review.openstack.org/#/c/165264 should be put through the meat grinder15:33
carl_baldwintidwellr: I’ll see if Zengfa has some time to work on the client.15:33
*** bpokorny has joined #openstack-meeting-315:33
tidwellrat this point I'm just turning patch sets in response to reviews, I've got some bandwidth15:34
carl_baldwintidwellr: Thanks for the reminder about the quota patch.  I haven’t looked at it yet and it looks like I’m not alone in that.  :(15:34
tidwellrI feel like subnet allocation is close, but the reviews haven't really come in on quotas and allocation yet :)15:36
carl_baldwintidwellr: Will review today and encourage others to do the same.15:37
*** reed has joined #openstack-meeting-315:37
*** lazy_prince is now known as killer_prince15:37
carl_baldwinAnything else on IPAM?15:38
*** nkrinner has quit IRC15:39
salv-orlandonot from me15:39
carl_baldwintidwellr: Zengfa tells me that subnet allocation is tested and added to the client as part of the existing patches.  We should confirm.15:39
tidwellrok, I'll check it out15:39
carl_baldwin#topic Open Discussion15:41
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:41
amullerhttps://review.openstack.org/#/q/status:open+branch:master+topic:bp/report-ha-router-master,n,z15:41
carl_baldwin#action carl_baldwin needs to work on the agenda page.  It has gotten stale.15:41
amullerreport-ha-router-master had its heavy patches merged the last couple of days15:41
*** stendulker_ has joined #openstack-meeting-315:41
amullerthe rest of the patches are ready to be merged on my end15:42
carl_baldwinamuller: I noticed that one on the rc1 page.  Let’s have a look at the remaining ones.  Thanks.15:42
amulleryeah, kind of a shame, even if all of the patches get approved today, mestery cut K3 already15:43
amullerso d/s QE won't get to test the feature off a K3 build15:43
mesteryamuller: Not cut yet, but cutting soon once ttx gets back15:43
amullerQA*15:43
mesteryamuller: But I believe I moved it to RC115:43
amullermestery: ack15:43
mesteryamuller: cool15:43
mesteryamulleri: Time just ran out on us15:43
mesteryfor kilo-3 at least15:43
amullerUnderstood15:44
*** stendulker has quit IRC15:44
*** cbader has joined #openstack-meeting-315:47
carl_baldwinAnyone giving thought to Liberty and beyond?  (Besides IPAM which we know has some work left to do)15:47
amullerDVR + L3 HA integration pops to mind, but I am biased :)15:48
*** marun has joined #openstack-meeting-315:49
*** eghobo has joined #openstack-meeting-315:49
saggi1carl_baldwin: Us at dragonflow hope to get something ready for liberty15:50
carl_baldwinamuller: ack and I agree15:50
amullercarl_baldwin: Have you heard from Jaume about BGP lately?15:51
carl_baldwinamuller: I haven’t.  It is something I’d like to revive for Liberty.  I think there was a fair amount of work done on it.15:52
carl_baldwinsaggi1: Any more specifics?15:52
saggi1https://launchpad.net/dragonflow15:53
saggi1kind of competing with dvr15:53
saggi1different approach. Using ovs rules instead of namespaces.15:53
carl_baldwinI think I’d like to revise and trim down my blueprint on backing networks and combine that with BGP.15:54
saggi1We don't have too much working. But the work on factoring out dvr is helping us integrate.15:55
*** kozhukalov has joined #openstack-meeting-315:55
carl_baldwinsaggi1: thanks for the link.15:55
*** cbader has quit IRC15:59
carl_baldwinI guess we’re out of time.  Thanks, all.16:00
*** cbader has joined #openstack-meeting-316:00
*** cbader has quit IRC16:00
carl_baldwin#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings"16:00
openstackMeeting ended Thu Mar 19 16:00:14 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-03-19-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-03-19-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-03-19-15.01.log.html16:00
yamamotobye16:00
*** pc_m has left #openstack-meeting-316:00
*** gsagie has joined #openstack-meeting-316:00
*** tidwellr has left #openstack-meeting-316:01
*** gsagie has left #openstack-meeting-316:01
*** saggi1 has quit IRC16:02
*** baoli has quit IRC16:02
*** baoli has joined #openstack-meeting-316:03
*** elmiko has joined #openstack-meeting-316:03
*** jcoufal_ has quit IRC16:08
*** elmiko has left #openstack-meeting-316:09
*** belmoreira has quit IRC16:12
*** eghobo has quit IRC16:14
*** scheuran has quit IRC16:15
mlavalle/close16:16
*** mlavalle has left #openstack-meeting-316:16
*** pkarikh has quit IRC16:22
*** amotoki has quit IRC16:22
*** emagana has joined #openstack-meeting-316:26
*** eghobo has joined #openstack-meeting-316:30
*** sarob has quit IRC16:34
*** JeanBriceCombebi has joined #openstack-meeting-316:34
*** thomasem has quit IRC16:41
*** egallen has joined #openstack-meeting-316:46
*** amuller has left #openstack-meeting-316:46
*** pkoniszewski has quit IRC16:46
*** JeanBriceCombebi has quit IRC16:51
*** JeanBriceCombebi has joined #openstack-meeting-316:51
*** yamahata has joined #openstack-meeting-316:52
*** evgenyf has quit IRC16:53
*** baoli has quit IRC16:54
*** hemanthravi has joined #openstack-meeting-316:55
*** baoli has joined #openstack-meeting-316:55
*** hemanthravi has left #openstack-meeting-316:55
*** banix has joined #openstack-meeting-316:59
*** bpokorny_ has joined #openstack-meeting-317:00
*** Swami has joined #openstack-meeting-317:01
*** bpokorny has quit IRC17:03
*** yapeng has joined #openstack-meeting-317:05
*** Networkn3rd has quit IRC17:05
*** Poornima has joined #openstack-meeting-317:09
*** Networkn3rd has joined #openstack-meeting-317:15
*** JeanBriceCombebi has quit IRC17:16
*** iovadia has quit IRC17:20
*** shwetaap has quit IRC17:20
*** mattgriffin has quit IRC17:25
*** mwagner_lap has quit IRC17:27
*** wuhg has quit IRC17:29
*** s3wong has joined #openstack-meeting-317:29
*** e0ne has quit IRC17:30
*** shwetaap has joined #openstack-meeting-317:30
*** mestery_ has joined #openstack-meeting-317:31
*** mestery has quit IRC17:33
*** coolsvap is now known as coolsvap|afk17:33
*** egallen has quit IRC17:33
*** eghobo has quit IRC17:33
*** clu_ has joined #openstack-meeting-317:34
*** thomasem has joined #openstack-meeting-317:37
*** mestery_ is now known as mestery17:39
*** ivar-lazzaro has joined #openstack-meeting-317:43
*** yamamoto has quit IRC17:44
*** ivar-lazzaro has quit IRC17:45
*** ivar-lazzaro has joined #openstack-meeting-317:47
*** mageshgv has joined #openstack-meeting-317:49
*** susaant has joined #openstack-meeting-317:50
*** matrohon has quit IRC17:51
*** rkukura has joined #openstack-meeting-317:55
*** SumitNaiksatam has joined #openstack-meeting-317:55
*** sreshetn1 has joined #openstack-meeting-317:58
*** mattgriffin has joined #openstack-meeting-317:59
*** reed has quit IRC17:59
SumitNaiksatambanix: ivar-lazzaro rkukura mageshgv Yi yapeng yamahata: hi18:00
rkukurahi18:00
mageshgvhi18:00
banixhi18:00
SumitNaiksatam#startmeeting networking_policy18:01
openstackMeeting started Thu Mar 19 18:01:24 2015 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: networking_policy)"18:01
openstackThe meeting name has been set to 'networking_policy'18:01
Yihi18:01
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#March_19th.2C_12th_201518:01
SumitNaiksatam#info kilo-2 was released as planned: #link http://lists.openstack.org/pipermail/openstack-dev/2015-March/059236.html18:02
SumitNaiksatamthings which did not make it into kilo-2 now moved to kilo-318:02
SumitNaiksatam#info kilo-3 deadline is April 15th18:02
*** bpokorny has joined #openstack-meeting-318:02
SumitNaiksatamso we are the real business end of the release now! ;-)18:03
*** enikanorov has joined #openstack-meeting-318:03
*** megm_ has joined #openstack-meeting-318:03
SumitNaiksatamwe also had the PTL elections (per project requirements), and the results were declarded: #link http://lists.openstack.org/pipermail/openstack-dev/2015-March/059317.html18:04
SumitNaiksatamthanks to malini for shepherding the elections18:04
rkukuracongrats SumitNaiksatam!18:04
Yicongrats!18:04
*** megm has quit IRC18:04
SumitNaiksatamrkukura: yi: thanks ;-)18:04
mageshgvCongrats SumitNaiksatam!!18:04
SumitNaiksatammageshgv: thanks18:04
SumitNaiksatamso lets start with the standing agenda items18:04
SumitNaiksatam#topic Bugs18:04
*** openstack changes topic to "Bugs (Meeting topic: networking_policy)"18:04
SumitNaiksatamat least one critical bug this time:18:05
*** bpokorn__ has joined #openstack-meeting-318:05
SumitNaiksatam#link https://bugs.launchpad.net/group-based-policy/+bug/143353018:05
openstackLaunchpad bug 1433530 in Group Based Policy "GBP Kilo release should be in sync with Neutron Kilo" [Critical,New] - Assigned to Magesh GV (magesh-gv)18:05
ivar-lazzarohi18:05
SumitNaiksatamwe have known this for a while, so mageshgv thanks for jumping on this18:05
*** bpokorny_ has quit IRC18:05
SumitNaiksatam#link https://review.openstack.org/16537718:06
*** enikanorov__ has quit IRC18:06
SumitNaiksatami agree with ivar-lazzaro’s comment there, that should be added right away so that we can catch all other issues with the neutron integration at least at the UT level18:07
SumitNaiksatammageshgv: are you comfortable with this or is it blowing up into too many changes?18:07
*** bpokorny has quit IRC18:08
mageshgvSumitNaiksatam: It looks pretty straight forward for the server18:08
SumitNaiksatammageshgv: okay18:08
*** eghobo has joined #openstack-meeting-318:09
SumitNaiksatamon the client side also, there are similar oslo changes, and we should do that in parallel to bump up the neutron client dependency to 2.3.1018:09
mageshgv#link https://review.openstack.org/#/c/165378/18:09
SumitNaiksatammageshgv: i believe you need this for your floating IP support impl as well?18:09
SumitNaiksatammageshgv: oh nice, sorry i did not catch that18:09
mageshgvThe client has some tricky changes though18:09
SumitNaiksatammageshgv: hmmm, ok18:10
mageshgvAs for floating IP, I can post a WIP patch may be tomorrow18:10
SumitNaiksatammageshgv: sweet, lets get to that in the specs discussion18:10
SumitNaiksatamivar-lazzaro: you wanted to discuss: #link https://bugs.launchpad.net/group-based-policy/+bug/1432816 ?18:11
openstackLaunchpad bug 1432816 in Group Based Policy "inconsistent template ownership during chain creation" [Undecided,New] - Assigned to Ivar Lazzaro (mmaleckk)18:11
*** coolsvap|afk has quit IRC18:11
ivar-lazzaroSumitNaiksatam: yep18:11
ivar-lazzaroTo give a quick summary, the problem in on SC instance ownership18:12
ivar-lazzaroa chain can be triggered in many different ways... By someone providing a PRS, or consuming it18:13
ivar-lazzaroor even by an admin changing the PRS rules18:13
*** hemanthravi has joined #openstack-meeting-318:13
SumitNaiksatamivar-lazzaro: true18:13
ivar-lazzaroEven though the intent is the same, the final state diverges depending on the user that triggers the chain18:13
ivar-lazzarofor example, suppose you have a shared PRS, and TenantA provides it18:14
ivar-lazzaroTenantB consuming it will trigger the chain, and TenantB will be the owner of the SC instance18:14
ivar-lazzaroHowever, if TenantB was previously consuming the chain, and then TenantA triggered the instance by providing the same PRS18:15
SumitNaiksatamivar-lazzaro: mageshgv: shouldn’t the SC intance be always owned by admin (since its an internal artifact)? or does that cause issues with sharing due to associations with other resources?18:15
ivar-lazzaroIn this case the SC instance (and the HEAT stacks) will be owned by tenantA18:15
ivar-lazzaroThis becomes a problem when a given tenant starts the action, and another one do the opposite (eg. destroy the chain)18:16
ivar-lazzarothis would fail because the tenant triggering the destruction is not owning the chain18:16
ivar-lazzaroSumitNaiksatam: that's the question I want to bring up... who has to own the chain?18:17
ivar-lazzaroSumitNaiksatam: the admin? The provider? The consumer?18:17
Yiivar-lazzaro: what's the difference between SFC case and other cases?18:17
mageshgvSumitNaiksatam: admin owning the SC instance does solve this issue.18:17
hemanthraviin case of admin that would be a parent PRS with the SC, is that right?18:17
SumitNaiksatamhemanthravi: there is no PRS hierarchy issue here18:18
ivar-lazzaroYi: that with SFC some heat stacks are created, and owned by a given tenant18:18
mageshgvivar-lazzaro: the owner should not be the consumer IMO. It can be either the admin or the provider18:18
ivar-lazzaroYi: and they cannot be destroyed unless the very same tenant triggers the disruption18:18
ivar-lazzaromageshgv: I agree18:18
hemanthravimageshv: agree18:19
SumitNaiksatamhemanthravi: the issue is that we create service chain instances internally (triggered by some other user actions), and currently we dont consistently use the same tenant to create/modify the SC instance18:19
ivar-lazzaroThe advantage of having the provider owning it is that he can go and modify manually the instances if available18:19
SumitNaiksatamivar-lazzaro: true but that would be concern too, no?18:19
*** johnthetubaguy is now known as zz_johnthetubagu18:19
ivar-lazzaroBut it will hit his/her quota (in the VM case for example)18:20
ivar-lazzaroThe advantage of having the admin as the owner is that all the chains belong to the same place, but they won't be visible by the tenants18:20
*** sergef has quit IRC18:21
SumitNaiksatamivar-lazzaro: they can always be visible, right?18:21
mageshgvivar-lazzaro, SumitNaiksatam: may be we can even consider something similar to this #link https://review.openstack.org/#/c/101281/18:21
ivar-lazzaroSumitNaiksatam: no unless you share them18:21
SumitNaiksatamivar-lazzaro: its just that the non-admin user wont be able to modify18:21
SumitNaiksatamivar-lazzaro: true, or we could add another user18:21
yapengivar-lazzaro: but we can't assume that admin always as owner of chain, right?18:22
SumitNaiksatamuser -> role, i was going to mention that earlier18:22
ivar-lazzaroSumitNaiksatam: even in that case, providers and consumers won't be able to see the instances18:22
igordcardivar-lazzaro: but then the admin would need to pre-create all possible chains, right?18:22
ivar-lazzaroyapeng: it could be a configurable user18:22
SumitNaiksatamyapeng: this is chain instance that is internally created18:22
ivar-lazzaroyapeng: which is an Admin and which can create Heat templates18:22
SumitNaiksatamigordcard: hi, good to see you join the meeting - to your question, no, not required to pre-create18:23
ivar-lazzaroBut there are other issues to consider, like how a VM (NFV) could be attached to one or more networks belonging to different tenant18:23
SumitNaiksatamivar-lazzaro: here is my suggestion (dont mean to prolong the discussion) -18:23
SumitNaiksatamivar-lazzaro: i think people need a little more time to think about this, so i believe this is an excellent topic to bring up on the -dev ML18:24
ivar-lazzaroSumitNaiksatam: +118:24
SumitNaiksatamand we can have the discussion there and try to wrap this up in a couple of days, sound okay?18:24
mageshgv+118:24
igordcardSumitNaiksatam: +118:24
SumitNaiksatamokay good, i believe ivar-lazzaro has given it the most thought, so i more inclined to go with his approach, but there are other groups working on similar problem, so lets see if we hear from them18:25
SumitNaiksatamivar-lazzaro: mageshgv: igordcard yapeng Yi hemanthravi: thanks for your input on this18:25
*** bpokorny has joined #openstack-meeting-318:26
SumitNaiksatamivar-lazzaro: i bumped the other bug assigned to you to Critical (support for redirect in external policy)18:26
SumitNaiksatamivar-lazzaro: but i believe you have that covered18:26
ivar-lazzaroSumitNaiksatam: thanks, there's already a patch there18:26
ivar-lazzarowhich brings up another question actually18:27
SumitNaiksatamivar-lazzaro: ah okay, #link https://review.openstack.org/16492018:27
ivar-lazzarodo we have time to discuss this?18:27
SumitNaiksatamas matter of sanity, we will discuss every critical bug in this meeting18:27
SumitNaiksatamivar-lazzaro: yes18:27
SumitNaiksatamcritical bug is show-stopper18:27
ivar-lazzarook18:27
ivar-lazzaro#link https://bugs.launchpad.net/group-based-policy/+bug/143277918:27
openstackLaunchpad bug 1432779 in Group Based Policy "redirect actions don't work with external policies" [Critical,Confirmed] - Assigned to Ivar Lazzaro (mmaleckk)18:27
*** safchain has quit IRC18:28
ivar-lazzaroThe quick summary is that chains are not triggered when one of the actors is an External Policy18:28
*** banix has quit IRC18:28
ivar-lazzarowhich is obviously needed (ie. LB in front of Web access)18:28
SumitNaiksatamivar-lazzaro: okay, i believe this was an oversight in the earlier integration between the external connectivity and service chaining?18:28
ivar-lazzaroSumitNaiksatam: yes18:29
*** reed has joined #openstack-meeting-318:29
SumitNaiksatamand it was discovered during recent integration testing18:29
*** bpokorn__ has quit IRC18:29
ivar-lazzaroIn my current implementation, a chain can only be consumed by an External Policy18:29
SumitNaiksatamivar-lazzaro: thanks for catching that and jumping on it18:29
ivar-lazzarowhen an external policy provides a chain, it's managed like a normal ALLOW action18:30
SumitNaiksatamjust a friendly suggestion to everyone, please add “group-based-policy-core” to the reviewer’s list when you submit a patch18:30
ivar-lazzaroSumitNaiksatam: woops18:30
SumitNaiksatamivar-lazzaro: right18:30
SumitNaiksatamonce you add that alias, all cores will get automatically added and it will show on the review dashboards18:30
igordcardSumitNaiksatam: ahh, thanks18:31
*** emagana has quit IRC18:31
SumitNaiksatamivar-lazzaro: sorry did not mean to interrupt18:31
ivar-lazzaroI was wondering if there are any use cases for which we want to enable chaining also on a EP *providing* a PRS18:31
ivar-lazzaroSumitNaiksatam: np, that was a good observation18:31
*** emagana has joined #openstack-meeting-318:32
SumitNaiksatamivar-lazzaro: but seems like you have this covered18:32
ivar-lazzaroI don't see an EP providing a Load Balancer for instance... But I can see it providing an IDS18:33
SumitNaiksatamivar-lazzaro: good question, i have not thought through that18:33
SumitNaiksatamivar-lazzaro: not sure about IDS, i think hemanthravi might have more insight here18:33
SumitNaiksatamivar-lazzaro: but i would suggest that this is also a great question for the -dev ML18:33
Yiivar-lazzaro: why no LB?18:34
ivar-lazzaroYi: well, the external policy is the rest of the world, Who are the members of the load balancer in that case?18:34
ivar-lazzaroYi: in the RMD case, the porta on the External Network are usually router interfaces18:35
hemanthraviivar: In case the EP is for provider resources such as a logging service, etc the IDS might not be required18:35
igordcardif service chaining evolves to support other kinds of services, even provided by VMs, it may make sense for future use cases to have chaining on provider EPs..18:35
SumitNaiksatamhemanthravi: good point, “logging service” seems like a good example18:35
SumitNaiksatamigordcard: +118:36
ivar-lazzarohemanthravi: logging seems a good case18:36
SumitNaiksatamivar-lazzaro: lets take this to the ML as well ;-)18:36
*** banix has joined #openstack-meeting-318:36
SumitNaiksatamivar-lazzaro: sorry, dont mean to delay things18:36
ivar-lazzaroroger that18:36
SumitNaiksatamivar-lazzaro: but good to have broader discussion18:36
hemanthravidon't think we need to support SC for EP provider at this time18:37
ivar-lazzaroSumitNaiksatam: it makes sense to me, it's a great help for making decisions18:37
SumitNaiksatamivar-lazzaro: okay18:37
ivar-lazzaroSumitNaiksatam: the more use cases people have in mind, the better18:37
SumitNaiksatamhemanthravi: okay, lets chime in on the ML (ivar-lazzaro will send email and start the discussion)18:37
SumitNaiksatamany other bugs anyone wants to discuss?18:37
SumitNaiksatam#topic Functional/Integration Tests18:38
*** openstack changes topic to "Functional/Integration Tests (Meeting topic: networking_policy)"18:38
SumitNaiksatam#link https://review.openstack.org/#/c/161511 was approved18:38
SumitNaiksatamand then there was a follow up patch as well18:38
SumitNaiksatamanyway, summary is that we if you do a “check experimental” it will trigger a job from the openstack infra18:39
SumitNaiksatamthe actual job that needs to be run is being configured in gate-hook that resides on teh GBP side:18:39
SumitNaiksatam#link https://review.openstack.org/#/c/16153218:40
SumitNaiksatami am working on this part18:40
SumitNaiksatamapologies on the slower progress on this, i am learning by trial and error18:40
*** bpokorny_ has joined #openstack-meeting-318:40
SumitNaiksatamis jishnu here?18:40
SumitNaiksatamhe is working on adapting his test suite to be triggered from this gate job, would have been good to have his update18:41
SumitNaiksatamany questions on this?18:41
SumitNaiksatamwe wil soon get to a point where we will require submitting some functional/integration tests with every new feature18:42
SumitNaiksatamand that is a good thing ;-)18:42
*** stendulker_ has quit IRC18:42
SumitNaiksatamif you have spare cycles please feel free to jump in on this activity (ping me offline)18:42
SumitNaiksatam#topic Packaging update18:43
*** openstack changes topic to "Packaging update (Meeting topic: networking_policy)"18:43
SumitNaiksatamrkukura: over to you18:43
*** songole has joined #openstack-meeting-318:43
*** bpokorny has quit IRC18:43
SumitNaiksatamsorry, i dont have the new release of the stable/juno yet18:43
rkukuraNow that we have a stable/juno update, I need to update the Fedora and RDO packaging. Should get to that over the next week or so.18:43
rkukuraSumitNaiksatam: I thought you did - sorry18:44
rkukuraforgot we were still trying to get the policy.json fix in18:44
*** yamamoto has joined #openstack-meeting-318:44
SumitNaiksatamrkukura: yeah, i was exploring mageshgv’s comment18:44
SumitNaiksatamexploring -> investigating18:45
SumitNaiksatammageshgv: i will catch up with you offline18:45
SumitNaiksatam#link https://review.openstack.org/#/c/165294/1/setup.cfg18:45
mageshgvSumitNaiksatam: okay, we can discuss on this offline18:45
rkukuraIt would be great if we could use the policy_dirs approach rather than requiring manual merging of the files.18:45
SumitNaiksatamrkukura: that is not clear to me, but may be i am missing something18:46
SumitNaiksatammageshgv: thanks for the suggestion though, since i was not even aware of this possibility18:46
SumitNaiksatamrkukura: thanks for the update18:46
rkukuramageshgv: you said “this will cause issues” so I’m not assuming it possible - just that it would be nice18:46
SumitNaiksatam#topic GBP Project Proposal18:47
*** openstack changes topic to "GBP Project Proposal (Meeting topic: networking_policy)"18:47
SumitNaiksatam#undo18:47
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x8e5f350>18:47
*** mattgriffin has quit IRC18:48
rkukuraLets followup on the gerrit review18:48
SumitNaiksatamrkukura: okay18:48
SumitNaiksatam#topic GBP Project Proposal18:48
*** openstack changes topic to "GBP Project Proposal (Meeting topic: networking_policy)"18:48
SumitNaiksatamwe put the proposal in WIP18:48
SumitNaiksatamsince we wanted to address the comments made - (1) PTL election, (2) gate that has more than just UTs18:49
*** yamamoto has quit IRC18:49
SumitNaiksatami believe we are past (1) now18:49
SumitNaiksatamonce we sort out (2) (and we are getting closer on that), we will remove the WIP18:49
SumitNaiksatamjust FYI - the TC meets every tuesday to discuss these type of things18:50
*** SotK has quit IRC18:50
SumitNaiksatamand we need to request being on their agenda 4 business days prior to the meeting18:50
SumitNaiksatamso anyone has any thoughts/suggestions/comments on this please let me know18:50
SumitNaiksatami am rushing here a little but since we have only 10 mins left18:50
SumitNaiksatamour favorite topic -18:51
SumitNaiksatam#topic Re-factor Group Based Policy with Neutron RESTful APIs18:51
*** openstack changes topic to "Re-factor Group Based Policy with Neutron RESTful APIs (Meeting topic: networking_policy)"18:51
SumitNaiksatamYi: yapeng: over to you18:51
*** sreshetn1 has quit IRC18:51
SumitNaiksatamsorry i havent reviewed the latest changes18:51
SumitNaiksatamhow close are we to addressing the last round of review suggestions by ivar-lazzaro and rkukura?18:52
*** safchain has joined #openstack-meeting-318:52
yapengwe are wrapping up the UTs. I updated one patch and ready for review.18:52
SumitNaiksatamyapeng: #link https://review.openstack.org/159725 right?18:53
yapengYes18:53
SumitNaiksatamokay18:53
SumitNaiksatamyapeng: Yi: any blockers?18:53
YiSumitNaiksatam: on my side, I finished the mixin that Ivar suggested18:53
SumitNaiksatamYi: sweet!!18:53
Yibut on patching the UT, I have some issues18:54
ivar-lazzaronice18:54
YiI have create_resource/update_resource/delete_resource patched18:54
Yibut got issue with get_resource and get_resources18:54
Yi1. for get_resource, or show_resource18:55
Yiit somehow cannot get along with the gbp plugin operations18:55
SumitNaiksatamivar-lazzaro: can i request you to spare a few minutes to help  Yi  with this in #openstack-gbp after this meeting?18:56
ivar-lazzaroSumitNaiksatam: sure18:56
Yifor example, getting policy target would be fine if I patch the get_port through plugin call18:56
SumitNaiksatamivar-lazzaro: thanks18:56
Yibut if I patch the get_port with WSGI, get_policy_target will fail18:56
SumitNaiksatamYi: okay18:56
SumitNaiksatamYi: seems like a slightly longer discussion, if you dont mind lets pick it up in #openstack-gbp immediately after this18:57
YiSumitNaiksatam, ivar-lazzaro: that would be great. thanks!18:57
SumitNaiksatamYi: nice, thanks for persistence on this!18:57
SumitNaiksatam#topic Floating IP support18:57
*** openstack changes topic to "Floating IP support (Meeting topic: networking_policy)"18:57
SumitNaiksatam#link https://review.openstack.org/15729818:58
*** SotK has joined #openstack-meeting-318:58
SumitNaiksatammageshgv: i believe you mentioned you will be posting a WIP tomorrow?18:58
SumitNaiksatammageshgv: will you be updating the spec accordingly?18:58
mageshgvSumitNaiksatam: yes, I will post the patch tomorrow18:58
*** ttrifonov is now known as zz_ttrifonov18:59
mageshgvonce we go over the patch and see that the current approach makes sense at a high level, I can update the bp18:59
*** sreshetn1 has joined #openstack-meeting-318:59
SumitNaiksatammageshgv: okay, but we need to iterate quickly on this19:00
*** thangp has quit IRC19:00
SumitNaiksatammageshgv: lets identify a couple of point people (in terms of reviewers) that will work with you closely on this to move this forward19:00
*** mattgriffin has joined #openstack-meeting-319:00
SumitNaiksatammageshgv: thanks for the update19:00
mageshgvSumitNaiksatam: yes, it should be faster to iterate now that we have a rough implementation19:01
SumitNaiksatam#topic Cross Project Liaisons19:01
*** openstack changes topic to "Cross Project Liaisons (Meeting topic: networking_policy)"19:01
*** mattgriffin has quit IRC19:01
SumitNaiksatamrkukura: stepped up for being a liaison for Oslo and Nova19:01
SumitNaiksatamwe are still looking for liaisons for other projects, with Keystone and Neutron being a priority19:01
rkukuranothing to report yet though19:01
SumitNaiksatamplease ping me if you would like to19:01
SumitNaiksatamrkukura: thanks!19:02
*** mattgriffin has joined #openstack-meeting-319:02
SumitNaiksatam#topic Open Discussion19:02
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"19:02
SumitNaiksatamwe are two minutes over19:02
SumitNaiksatamanything we missed that you want to bring up?19:02
SumitNaiksatamkilo-3 is crunch time, so lets lock in our focus! ;-)19:03
SumitNaiksatamokay thanks everyone for attending today19:03
SumitNaiksatambye19:03
rkukurathanks SumitNaiksatam!19:03
mageshgvnye19:03
igordcardbye19:03
rkukurabye19:03
mageshgvbye19:03
hemanthravibye19:03
SumitNaiksatam#endmeeting19:03
*** openstack changes topic to "OpenStack Meetings"19:03
openstackMeeting ended Thu Mar 19 19:03:52 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:03
songolebye19:03
yapengbye19:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-03-19-18.01.html19:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-03-19-18.01.txt19:03
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-03-19-18.01.log.html19:03
*** mageshgv has quit IRC19:04
*** hemanthravi has left #openstack-meeting-319:04
*** songole has left #openstack-meeting-319:04
Yibye19:04
*** susaant has quit IRC19:04
*** rkukura has left #openstack-meeting-319:06
*** marun has quit IRC19:09
*** evgenyf has joined #openstack-meeting-319:16
*** marun has joined #openstack-meeting-319:19
*** banix has quit IRC19:22
*** Poornima has quit IRC19:29
*** banix has joined #openstack-meeting-319:36
*** SumitNaiksatam has quit IRC19:39
*** Poornima has joined #openstack-meeting-319:44
*** evgenyf has quit IRC19:49
*** shwetaap has quit IRC19:56
*** Poornima has quit IRC20:01
*** Shamail has joined #openstack-meeting-320:02
*** mattgrif_ has joined #openstack-meeting-320:03
*** mattgriffin has quit IRC20:04
*** mattgrif_ is now known as mattgriffin20:04
*** sreshetn1 has quit IRC20:05
*** sambetts has quit IRC20:06
*** sambetts has joined #openstack-meeting-320:06
*** Yi has quit IRC20:07
*** Shamail has quit IRC20:07
*** e0ne has joined #openstack-meeting-320:09
*** shwetaap has joined #openstack-meeting-320:11
*** eghobo has quit IRC20:11
*** e0ne has quit IRC20:14
*** Shamail has joined #openstack-meeting-320:15
*** sreshetn1 has joined #openstack-meeting-320:16
*** mrda-away is now known as mrda20:17
*** Shamail has quit IRC20:18
*** thomasem has quit IRC20:20
*** emagana has quit IRC20:20
*** megm_ has quit IRC20:24
*** banix has quit IRC20:25
*** megm has joined #openstack-meeting-320:25
*** emagana has joined #openstack-meeting-320:25
*** Shamail has joined #openstack-meeting-320:25
*** Swami has quit IRC20:26
*** Yi has joined #openstack-meeting-320:26
*** salv-orlando has quit IRC20:27
*** sreshetn1 has quit IRC20:27
*** Shamail has quit IRC20:28
*** mattgriffin has quit IRC20:35
*** claired has joined #openstack-meeting-320:48
*** mattgriffin has joined #openstack-meeting-320:48
*** jaypipes has quit IRC20:50
*** nickchase has joined #openstack-meeting-320:51
*** safchain has quit IRC20:51
*** emagana has quit IRC20:53
*** VW_ has joined #openstack-meeting-320:54
*** sreshetn1 has joined #openstack-meeting-320:54
*** emagana has joined #openstack-meeting-320:54
mattgriffinHA Guide Team: 5 minute warning20:55
*** Sukhdev has joined #openstack-meeting-320:57
*** matrohon has joined #openstack-meeting-320:58
*** Shamail has joined #openstack-meeting-320:59
*** absubram has quit IRC20:59
mattgriffino/ HA Guide Team21:00
*** kozhukalov has quit IRC21:00
mattgriffin#startmeeting HA-Guide-Update21:01
openstackMeeting started Thu Mar 19 21:01:23 2015 UTC and is due to finish in 60 minutes.  The chair is mattgriffin. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: HA-Guide-Update)"21:01
openstackThe meeting name has been set to 'ha_guide_update'21:01
ShamailHi mattgriffin!21:01
nickchaseHey all.21:01
mattgriffinhi Shamail nickchase21:01
*** jckasper has quit IRC21:01
megmHi all21:02
Shamail(I might have a little lag; on mobile)21:02
mattgriffinhi megm21:02
mattgriffinShamail, np21:02
mattgriffinlooks like sam-i-am isn't around21:02
megmShamail, I partially updated https://wiki.openstack.org/wiki/HAGuideImprovements/TOC with the Storage Backend piece we discussed21:02
*** clouddon has joined #openstack-meeting-321:02
megmI'll finish it after our meeting21:02
mattgriffinmegm, cool. let's get started on the agenda then21:03
mattgriffin#topic Review action items from last meeting21:03
*** openstack changes topic to "Review action items from last meeting (Meeting topic: HA-Guide-Update)"21:03
Shamailmegm: looks great21:03
mattgriffinmost of you reviewed and edited the email to the Docs team and megm's big edits. thank you!21:03
nickchasesam-i-am has been occupied with the ops meetup21:04
nickchaseand he apologizes but he's overbooked right now.21:04
mattgriffinnickchase, ack21:04
megmAndreas seems pleased -- that seems like a good thing21:04
clouddonim here sneaking21:04
*** ivar-laz_ has joined #openstack-meeting-321:04
ShamailHi clouddon21:04
nickchasethe email is a good philosophy but we do need a more detailed TOC.21:05
mattgriffinmegm, yeah. great overview getting everyone else up to speed21:05
mattgriffinhi clouddon21:05
*** VW_ has quit IRC21:05
clouddonhi all!21:05
*** ivar-laz_ has quit IRC21:05
mattgriffinone action item that we had from last week (again, sorry for holding the meeting early) was "check with sam-i-am and nickchase on starting a "new" doc structure"21:05
megmI thought the detailed outline was in the https://wiki.openstack.org/wiki/HAGuideImprovements/TOC file21:05
mattgriffinheh... i can't remember what that was about21:06
*** ivar-laz_ has joined #openstack-meeting-321:06
megmI remember21:06
mattgriffinplease share :)21:06
nickchaseSam-I-Am and I were discussing...21:06
megmThe question is whether we try to modify within the current file structure in the repo or start a new doc for development21:06
*** ivar-laz_ has quit IRC21:07
megmPerhaps eventually move the new doc back to the old title21:07
nickchase(I'll wait.)21:07
mattgriffinmegm, ack21:07
clouddonisnt the new structure for this?21:07
megmso what did sam-i-am and nick conclude?21:07
nickchaseI think it depends on how close the new structure is to the old one.21:07
nickchasewe were discussing where/if we were going to talk about pacemaker.21:07
*** ivar-laz_ has joined #openstack-meeting-321:07
ShamailThe TOC is the new structure right?21:07
nickchaseWe finally settled on...21:08
nickchasethe idea that there are basically 3 levels of HA in OpenStack:21:08
nickchase0)  None; you just install everything and hope for the best.21:08
*** ivar-lazzaro has quit IRC21:08
nickchase1)  Basic HA:  you use the "traditional" means of HA, such as Galera for MySQL, redundant RabbitMQ clusters, etc.  If something breaks, it stays up -- unless it breaks again.21:09
nickchase3)  Nothing is going to take this sucker down:  you use more stringent HA such as Pacemaker, which proactively makes sure that everything stays up, and if it goes down, then it gets brought back up (if possible)21:09
nickchase(sorry, that's 2)21:10
nickchaseSo those are the 3 levels, and ...21:10
nickchasewe thought that one way to cover it would be...21:10
nickchaseto start with the "traditional" means, then talk about what you should do if you want level 2 (Nothing will take this down).21:10
nickchaseWhat do you guys think?21:11
mattgriffinnickchase, +121:11
Shamailnickchase: +121:11
megm                                              -1                                                                                                                                                                                                               nic21:11
clouddonmy only point with this sturcture would be the disticntion btweeen aactive/ active vs active/ apsssive21:12
ShamailThis is the control plane aspect though.  The data plane equivalent of this is out of scope, right?21:12
megmI think this is a good structure for the introductory material, which really does need to be expanded significantly.21:12
megmBut I thought we had agreed that the bulk of the guide would be structured to parallel the Install Guide.21:12
nickchaseI confess that I can't answer either clouddon or shamail on this; both statements are beyond my knowledge and I lean on SMEs. :)21:12
nickchaseWe can be parallel to the install guid321:13
clouddonHow about this?21:13
nickchaseand still follow this21:13
clouddonwhoever has points comment on wiki21:13
nickchaseby basically doing what I've described as "level 1" here based on the install guide.21:13
*** Networkn3rd has quit IRC21:13
Shamailnickchase: on my question, I would say let's keep this to control plane HA for now to stay out of political stuff/stifling topics.  clouddon: good suggestion +121:14
nickchaseclouddon +121:14
clouddongr8. thanks21:15
nickchaseShamail: I'm all for staying out of poltics; not sure what you mean by "stifling topics".21:15
mattgriffinShamail, i think +1 on control plane. likely more materials available elsewhere on data plane HA21:15
megmYes, Cloudon and everyone, muck with and comment on the outline21:15
*** ivar-laz_ has quit IRC21:15
Shamailnickchase: by stifiling topics I meant trying to speak for third parties without their participation.21:15
mattgriffin+1 for muck21:16
*** yamamoto has joined #openstack-meeting-321:16
ShamailOverall, the levels look great Nick.21:16
nickchaseShamail:  I agree, but just so I understand, who are the third parties?  You mean the SMEs?21:16
nickchaseShamail: great.21:16
mattgriffinthe other part of the "doc structure" issue is less about the TOC and more about how do we implement the large scale changes given the existing HA Guide, right?21:17
ShamailData plane would come down to how compute, network, storage vendors advise HA configuration/considerations for infrastructure resiliency21:17
megmI think it's important that we address the data plane issues, at least conceptually.  Details are elsewhere but I don't know of anything that puts it all together21:17
mattgriffinmegm, ^21:17
nickchasemegm: +121:18
Shamailmegm: I agree, we should address it at a high-level and say it's not our scope and to talk to your providers21:18
mattgriffinmegm, +121:18
megmkeywords:  DON'T LOSE MY DATA!!!  ;-)21:18
nickchase:)21:18
ShamailHaha21:18
*** sreshetn1 has quit IRC21:19
*** claired has quit IRC21:19
nickchaseAnd that, I assume, Shamail, is what you mean by "third parties".21:19
ShamailIf we can even add a summary of data plane resiliency technologies, etc. for each infrastructure layer.  Please look at the high-level summary I gave to Meg for "storage back ends" and poke at it. :)21:20
Shamailnickchase: yep!21:20
*** Piet has joined #openstack-meeting-321:20
ShamailWe could add one for network and compute as well21:20
megmCeph is a big player here, too -- not exactly what I would call a third-party but the concept is the same21:20
ShamailYep!21:20
*** yamamoto has quit IRC21:21
nickchaseOK, I agree in principle.  But at some point we're going to have to take a stand and be specific, in order to be truly useful.21:21
mattgriffinShamail, i think we have a good plan here already. anything you'd alter? https://wiki.openstack.org/wiki/HAGuideImprovements/TOC#Storage_Backend21:21
mattgriffinwell maybe just comment in the wiki like clouddon suggested21:21
ShamailIm going to modify it slightly mattgriffin, this was the result of a brief chat between Meg and I.21:22
mattgriffinexcellent21:22
megmSpecific about the concepts, not the procedures.  We point to the individual technologies for procedures but we need to explain what RAID does and does not do, etc21:22
ShamailWe should do something for network and compute.21:22
ShamailBut they also follow standard means of protection.  The point we should make is to consider protection at the infrastructure layer and give some standards that are used.  Leave the actual choice of protection to the user.21:23
ShamailI'll comment on wiki.  Just wanted to raise the infrastructure question.  I think we all agree on how deep we should go.21:23
mattgriffinack21:23
megmWe also discussed that we would cover HAProxy but make a mention of Level 2 switches for load-balancing...21:23
nickchaseI'm nto sure I agree; I'll know it when I see it. :)21:23
ShamailFair enough. :)21:24
ShamailWhat's up Mattgriffin?21:24
*** ivar-lazzaro has joined #openstack-meeting-321:24
megmIt boils down to needing more conceptual material.  The current guide has a lot of sections that are nothing more than a sample config file and instructions to copy it.21:25
Shamailmegm: +1121:25
ShamailOr +121:25
mattgriffinheh21:25
ShamailWhat's an extra 1 or 0?21:25
mattgriffinmove on to next action item from last week?21:25
*** lblanchard has quit IRC21:26
mattgriffinbtw... i'm using https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update#Next_Meeting21:26
mattgriffin#link https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update#Next_Meeting21:26
mattgriffinAre we ready to start assigning content or want to wait another week to leave comments on the wiki for any other potential changes?21:27
*** salv-orlando has joined #openstack-meeting-321:27
mattgriffinsounds like we should give it another week. agree?21:27
nickchaseDoes the current TOC track the install guide?21:27
nickchase+121:28
mattgriffinnickchase, if we swap our project names with what they do, yes21:28
megmI think pretty much21:28
nickchasewell, then I'd go either way; even if we add level 2, we'll likely keep what's here now.21:29
Shamailmattgriffin: +121:29
clouddonIf we are taking too long to confer, how about we put a date?21:30
megmThe old guide is arranged for active/active and active/passive.  The current TOC breaks that model.21:30
nickchaseWhy don't we assign some topics we KNOW are going to get written?21:30
megmI thought we had agreement but do we?21:30
nickchaseWe agree we're going to break that model, I believe.21:31
mattgriffinmegm, nickchase yes21:31
megmWhere are the existing source files?  I don't seem to have them in the openstack-manual repo I downloaded21:31
ShamailI like the new flow (vs. building the entire structure around A/A and A/P), however I think we still have to address A/A and A/P in each section.21:32
megmShamail +121:32
nickchaseare they not in openstack-manualsdoc/ha-guide?21:32
megmI didn't get that subdirectory21:33
megmAlso, when/how are we going to convert the existing docbook source to RST?21:34
nickchaseI'm not seeing it either.21:34
nickchaseOK, i give up, where is it?21:34
*** vgridnev_ has quit IRC21:34
Shamailhttps://github.com/openstack/ha-guide21:34
ShamailThis it?21:35
nickchaseso it as its own rep?21:35
nickchaserepo*21:35
ShamailApparently21:35
*** carl_baldwin has quit IRC21:35
ShamailSurprised.21:35
nickchaseI am too.21:35
*** mattfarina has quit IRC21:35
megmInteresting...21:36
nickchaseok, well, if it does, it does.21:36
nickchasewe just needed to know where to find it.21:36
*** ChuckC has quit IRC21:36
ShamailWho has core here?21:36
nickchaseno idea.21:37
mattgriffinmegm, is this enough to understand a process for converting?21:37
megmWe should add this info to the wiki21:37
nickchaseI think the first question is "why does it have its own repo?"21:37
nickchaseI know how to create a new RST book in openstack-manuals but not in openstack.21:37
megmMaybe this is a golden opportunity?  Leave the old guide where it is and create a new ha-guide in openstack-manuals?21:38
nickchaseWe can certainly do that.21:38
megmmattgriffin, I don't see info for converting that you reference.21:38
nickchaseI don't think info on converting is documented.21:39
nickchaseI only know because I did the network guide.21:39
nickchaseI take it back21:39
*** alexpilotti has joined #openstack-meeting-321:39
nickchaseinfo on converting specific files is documented21:39
nickchaseI'll find it in a moment21:39
megmNick, if you'll help me get started, I could convert and set up new files21:39
nickchasejust not creating a book.21:39
nickchaseTell you what: I'll create a book and help you get started converting the existing files to drop into it.  OK?21:40
nickchase(Just that it'll take longer to explain it than do it. :))21:40
nickchaseI'll have to do it to document it (which I will).21:40
*** salv-orlando has quit IRC21:40
*** safchain has joined #openstack-meeting-321:41
megmSounds good -- you do what is easier for you to do, then hand off to me?21:41
clouddoni need to sign off. thanks all21:41
ShamailSame here21:41
mattgriffinclouddon, Shamail later21:41
ShamailI'll catch up on the meeting log, cya all21:41
mattgriffincool21:42
*** safchain has quit IRC21:42
megmThanks!21:42
*** Shamail has quit IRC21:42
mattgriffinwill be posted to the wiki21:42
*** salv-orlando has joined #openstack-meeting-321:42
mattgriffinmegm, nickchase i think we need to wrap up21:42
nickchaseall sounds good21:43
nickchasethanks21:43
mattgriffinnickchase, you're going to do some documentation on converting, yes?21:43
nickchaseyes21:43
megmNick, do you know what we need to do?21:43
nickchaseyes.21:43
megmAnd we're ready to start setting up ha-guide files in openstack-manuals and leave the old repo intact?21:43
nickchase+121:43
nickchasethat's the plan, right?21:43
megmNick, let me know when you need me...21:44
nickchasewill do21:44
nickchasewill do, Meg21:44
mattgriffinmegm, nickchase like here? https://github.com/openstack/openstack-manuals/tree/master/doc21:44
nickchaseyes, there.21:45
mattgriffincool21:45
megm+121:45
mattgriffinquick documentation for action items...21:45
megmI will update https://etherpad.openstack.org/p/ha-guide-march-2015-update about the repos21:45
mattgriffin#action nickchase document how to convert21:45
*** clouddon has quit IRC21:45
mattgriffinmegm, cool21:46
mattgriffin#action all: review TOC and comment21:46
*** peristeri has quit IRC21:46
mattgriffinmegm, i think that (repos info) would be better on the HA Guide wiki21:46
mattgriffinye?21:46
mattgriffinyes?21:46
megm+121:47
mattgriffinhere: https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update21:47
nickchaseyes, definitely21:47
nickchasewe should also let the mailing list know21:47
mattgriffin#action megm update the HA Guide wiki with the right repos info21:47
nickchasein case there was some reason that it was moved.21:48
mattgriffin+121:48
megmWill do21:48
mattgriffinok. i think we're good until next week. anything else?21:48
megmI'm good21:48
mattgriffini think we should still be thinking about who we might want to pull into this effort (at our company or another group) to write some of the content.. but that's an ongoing action item until we start assigning sections.21:49
nickchaseI have a list of people and topics21:50
mattgriffinnickchase, great!21:50
nickchasethey're ready to tart21:50
nickchasestart*21:50
mattgriffinif there's nothing else, i'm going to end21:50
mattgriffinthanks megm & nickchase21:50
nickchaselater21:50
megmHave a great week!21:50
mattgriffinyou too!21:50
mattgriffin#endmeeting21:51
nickchaseyou too21:51
*** openstack changes topic to "OpenStack Meetings"21:51
openstackMeeting ended Thu Mar 19 21:51:01 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ha_guide_update/2015/ha_guide_update.2015-03-19-21.01.html21:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ha_guide_update/2015/ha_guide_update.2015-03-19-21.01.txt21:51
openstackLog:            http://eavesdrop.openstack.org/meetings/ha_guide_update/2015/ha_guide_update.2015-03-19-21.01.log.html21:51
*** absubram has joined #openstack-meeting-321:57
*** megm_ has joined #openstack-meeting-322:06
*** megm has quit IRC22:06
*** nati_ueno has joined #openstack-meeting-322:11
*** e0ne has joined #openstack-meeting-322:11
*** sreshetn1 has joined #openstack-meeting-322:15
*** yamamoto has joined #openstack-meeting-322:17
*** e0ne has quit IRC22:18
*** sahid has quit IRC22:19
*** sreshetn1 has quit IRC22:19
*** yamamoto has quit IRC22:21
*** ChuckC has joined #openstack-meeting-322:24
*** bknudson has quit IRC22:27
*** shwetaap has quit IRC22:31
*** nickchase has quit IRC22:34
*** matrohon has quit IRC22:52
*** Sukhdev has quit IRC22:57
*** mattgriffin has quit IRC22:59
*** marios has quit IRC23:01
*** s3wong has quit IRC23:14
*** Yi has quit IRC23:15
*** sreshetn1 has joined #openstack-meeting-323:16
*** s3wong has joined #openstack-meeting-323:16
*** banix has joined #openstack-meeting-323:16
*** sreshetn1 has quit IRC23:20
*** stevemar has quit IRC23:23
*** stevemar has joined #openstack-meeting-323:33
*** MarkAtwood has quit IRC23:34
*** stevemar has quit IRC23:40
*** stendulker has joined #openstack-meeting-323:44
*** stendulker has quit IRC23:52
*** watanabe_isao has joined #openstack-meeting-323:54
*** jckasper has joined #openstack-meeting-323:55
*** Yi has joined #openstack-meeting-323:55
*** gugl has joined #openstack-meeting-323:55

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