Tuesday, 2013-10-22

*** vipul-away is now known as vipul00:10
*** SergeyLukjanov is now known as _SergeyLukjanov00:10
*** _SergeyLukjanov has quit IRC00:11
*** SergeyLukjanov has joined #openstack-meeting-alt00:15
*** SergeyLukjanov is now known as _SergeyLukjanov00:16
*** IlyaE has quit IRC00:19
*** markmcclain has joined #openstack-meeting-alt00:19
*** SergeyLukjanov has joined #openstack-meeting-alt00:22
*** amitgandhi has joined #openstack-meeting-alt00:25
*** rakhmerov has joined #openstack-meeting-alt00:25
*** sarob has joined #openstack-meeting-alt00:26
*** gokrokve has quit IRC00:28
*** HenryG_ has joined #openstack-meeting-alt00:29
*** gokrokve has joined #openstack-meeting-alt00:29
*** rakhmerov has quit IRC00:30
*** sarob has quit IRC00:31
*** HenryG has quit IRC00:31
*** gokrokve has quit IRC00:34
*** markmcclain has quit IRC00:39
*** jrodom has quit IRC00:41
*** tanisdl has quit IRC00:46
*** sacharya has quit IRC00:48
*** sacharya has joined #openstack-meeting-alt00:48
*** bill_az_ has quit IRC00:49
*** nosnos has joined #openstack-meeting-alt00:52
*** sarob has joined #openstack-meeting-alt00:53
*** jrodom has joined #openstack-meeting-alt00:53
*** zehicle has joined #openstack-meeting-alt00:56
*** sarob has quit IRC00:57
zehicleThe OpenStack Core meetup will use IRC openstack-meeting01:00
*** markwash has quit IRC01:23
*** SergeyLukjanov is now known as _SergeyLukjanov01:26
*** rakhmerov has joined #openstack-meeting-alt01:26
*** HenryG_ has quit IRC01:26
*** _SergeyLukjanov has quit IRC01:27
*** rakhmerov has quit IRC01:30
*** amitgandhi has quit IRC01:36
*** IlyaE has joined #openstack-meeting-alt01:37
*** jrodom has quit IRC01:38
*** esker has joined #openstack-meeting-alt01:38
*** SergeyLukjanov has joined #openstack-meeting-alt01:38
*** SergeyLukjanov has quit IRC01:39
*** gokrokve has joined #openstack-meeting-alt01:39
*** gokrokve has quit IRC01:44
*** sacharya has quit IRC01:58
*** rakhmerov has joined #openstack-meeting-alt02:26
*** gokrokve has joined #openstack-meeting-alt02:28
*** sacharya has joined #openstack-meeting-alt02:30
*** rakhmerov has quit IRC02:31
*** gokrokve has quit IRC02:42
*** gokrokve has joined #openstack-meeting-alt02:43
*** gokrokve has quit IRC02:47
*** colinmcnamara has joined #openstack-meeting-alt03:02
*** markwash has joined #openstack-meeting-alt03:07
*** colinmcnamara has quit IRC03:08
*** colinmcnamara has joined #openstack-meeting-alt03:09
*** colinmcnamara has quit IRC03:13
*** rakhmerov has joined #openstack-meeting-alt03:27
*** rakhmerov has quit IRC03:32
*** esker has quit IRC03:45
*** amytron has joined #openstack-meeting-alt03:49
*** rakhmerov has joined #openstack-meeting-alt03:50
*** IlyaE has quit IRC03:50
*** eankutse has joined #openstack-meeting-alt03:51
*** gokrokve has joined #openstack-meeting-alt03:59
*** gokrokve has quit IRC04:03
*** IlyaE has joined #openstack-meeting-alt04:14
*** sacharya has quit IRC04:16
*** amytron has quit IRC04:16
*** sarob has joined #openstack-meeting-alt04:22
*** akuznetsov has joined #openstack-meeting-alt04:25
*** gokrokve has joined #openstack-meeting-alt04:29
*** gokrokve has quit IRC04:34
*** sarob has quit IRC04:45
*** sarob has joined #openstack-meeting-alt04:45
*** sarob_ has joined #openstack-meeting-alt04:50
*** sarob has quit IRC04:50
*** sarob_ has quit IRC04:51
*** sarob has joined #openstack-meeting-alt04:51
*** sarob has quit IRC04:56
*** gokrokve has joined #openstack-meeting-alt05:00
*** amytron has joined #openstack-meeting-alt05:00
*** gokrokve has quit IRC05:04
*** boris-42 has joined #openstack-meeting-alt05:04
*** eankutse has quit IRC05:17
*** dmakogon has joined #openstack-meeting-alt05:21
*** vipul has quit IRC05:25
*** vipul has joined #openstack-meeting-alt05:26
*** nadya has joined #openstack-meeting-alt05:26
*** gokrokve has joined #openstack-meeting-alt05:31
*** amytron has quit IRC05:31
*** akuznetsov has quit IRC05:31
*** akuznetsov has joined #openstack-meeting-alt05:35
*** gokrokve has quit IRC05:35
*** jtomasek has joined #openstack-meeting-alt05:41
*** nadya has quit IRC05:50
*** akuznetsov has quit IRC05:52
*** jtomasek has quit IRC05:56
*** vipul is now known as vipul-away06:00
*** gokrokve has joined #openstack-meeting-alt06:02
*** sarob has joined #openstack-meeting-alt06:02
*** vipul-away is now known as vipul06:05
*** gokrokve has quit IRC06:06
*** sarob has quit IRC06:07
*** markwash has quit IRC06:12
*** akuznetsov has joined #openstack-meeting-alt06:14
*** yamahata has quit IRC06:15
*** markwash has joined #openstack-meeting-alt06:18
*** SergeyLukjanov has joined #openstack-meeting-alt06:21
*** yamahata has joined #openstack-meeting-alt06:22
*** jcoufal has joined #openstack-meeting-alt06:25
*** gokrokve has joined #openstack-meeting-alt06:32
*** gokrokve has quit IRC06:37
*** boris-42 has quit IRC06:38
*** markwash has quit IRC06:40
*** akuznetsov has quit IRC06:48
*** yamahata has quit IRC06:53
*** IlyaE has quit IRC06:58
*** ilyashakhat has joined #openstack-meeting-alt07:23
*** jtomasek has joined #openstack-meeting-alt07:30
*** gokrokve has joined #openstack-meeting-alt07:34
*** SergeyLukjanov is now known as _SergeyLukjanov07:37
*** _SergeyLukjanov has quit IRC07:37
*** gokrokve has quit IRC07:39
*** SergeyLukjanov has joined #openstack-meeting-alt07:46
*** katyafervent has quit IRC07:46
*** SergeyLukjanov is now known as _SergeyLukjanov07:55
*** boris-42 has joined #openstack-meeting-alt08:01
*** SergeyLukjanov has joined #openstack-meeting-alt08:03
*** gokrokve has joined #openstack-meeting-alt08:05
*** gokrokve has quit IRC08:10
*** SergeyLukjanov has quit IRC08:10
*** SergeyLukjanov_ has joined #openstack-meeting-alt08:10
*** jmaron has quit IRC08:10
*** yamahata has joined #openstack-meeting-alt08:22
*** derekh has joined #openstack-meeting-alt08:26
*** SergeyLukjanov_ has quit IRC08:28
*** SergeyLukjanov has joined #openstack-meeting-alt08:33
*** SergeyLukjanov has quit IRC08:35
*** gokrokve has joined #openstack-meeting-alt08:36
*** sergmelikyan has quit IRC08:37
*** gokrokve has quit IRC08:40
*** IgorYozhikov has quit IRC08:54
*** gokrokve has joined #openstack-meeting-alt09:06
*** yamahata has quit IRC09:08
*** gokrokve has quit IRC09:10
*** jmaron has joined #openstack-meeting-alt09:11
*** jmaron has quit IRC09:16
*** sergmelikyan has joined #openstack-meeting-alt09:27
*** akuznetsov has joined #openstack-meeting-alt09:33
*** gokrokve has joined #openstack-meeting-alt09:37
*** gokrokve has quit IRC09:41
*** gokrokve has joined #openstack-meeting-alt10:08
*** gokrokve has quit IRC10:12
*** aostapenko has quit IRC10:16
*** yamahata has joined #openstack-meeting-alt10:19
*** dukhlov has joined #openstack-meeting-alt10:38
*** yamahata has quit IRC10:39
*** gokrokve has joined #openstack-meeting-alt10:39
*** gokrokve has quit IRC10:43
*** yamahata has joined #openstack-meeting-alt10:51
*** yamahata has quit IRC10:58
*** jcoufal has quit IRC11:04
*** gokrokve has joined #openstack-meeting-alt11:10
*** jmaron has joined #openstack-meeting-alt11:12
*** gokrokve has quit IRC11:14
*** jmaron has quit IRC11:17
*** malini_afk is now known as malini11:40
*** gokrokve has joined #openstack-meeting-alt11:40
*** katyafervent has joined #openstack-meeting-alt11:41
*** rakhmerov has quit IRC11:44
*** gokrokve has quit IRC11:45
*** yamahata has joined #openstack-meeting-alt11:51
*** pcm_ has joined #openstack-meeting-alt11:51
*** HenryG has joined #openstack-meeting-alt11:52
*** jcoufal has joined #openstack-meeting-alt12:00
*** pdmars has joined #openstack-meeting-alt12:03
*** gokrokve has joined #openstack-meeting-alt12:11
*** yamahata has quit IRC12:13
*** jmaron has joined #openstack-meeting-alt12:13
*** malini is now known as malini_afk12:13
*** gokrokve has quit IRC12:15
*** malini_afk is now known as malini12:15
*** demorris has joined #openstack-meeting-alt12:17
*** sarob has joined #openstack-meeting-alt12:18
*** sarob has quit IRC12:25
*** sarob has joined #openstack-meeting-alt12:26
*** nosnos has quit IRC12:27
*** nosnos has joined #openstack-meeting-alt12:28
*** demorris has quit IRC12:30
*** sarob has quit IRC12:30
*** rakhmerov has joined #openstack-meeting-alt12:31
*** nosnos has quit IRC12:32
*** colinmcnamara has joined #openstack-meeting-alt12:33
*** betsy has joined #openstack-meeting-alt12:35
*** colinmcnamara has quit IRC12:35
*** colinmcnamara has joined #openstack-meeting-alt12:36
*** colinmcnamara has quit IRC12:40
*** anteaya has joined #openstack-meeting-alt12:41
*** gokrokve has joined #openstack-meeting-alt12:42
*** gokrokve has quit IRC12:46
*** lblanchard has joined #openstack-meeting-alt12:53
*** amytron has joined #openstack-meeting-alt12:56
*** kevinconway has quit IRC12:56
*** dguitarbite has joined #openstack-meeting-alt12:59
*** dprince has joined #openstack-meeting-alt13:04
*** kevinconway has joined #openstack-meeting-alt13:05
*** obondarev has joined #openstack-meeting-alt13:06
*** dguitarbite has quit IRC13:12
*** dguitarbite has joined #openstack-meeting-alt13:13
*** gokrokve has joined #openstack-meeting-alt13:13
*** eankutse has joined #openstack-meeting-alt13:13
*** eankutse has quit IRC13:13
*** eankutse has joined #openstack-meeting-alt13:13
*** esker has joined #openstack-meeting-alt13:17
*** gokrokve has quit IRC13:17
*** ozstacker has quit IRC13:22
*** julim has joined #openstack-meeting-alt13:23
*** malini is now known as malini_afk13:31
*** yamahata has joined #openstack-meeting-alt13:32
*** Barker has joined #openstack-meeting-alt13:36
*** enikanorov has joined #openstack-meeting-alt13:37
*** yamahata has quit IRC13:40
*** yamahata has joined #openstack-meeting-alt13:41
*** amitgandhi has joined #openstack-meeting-alt13:42
*** gokrokve has joined #openstack-meeting-alt13:43
*** sacharya has joined #openstack-meeting-alt13:47
*** gokrokve has quit IRC13:48
*** eankutse1 has joined #openstack-meeting-alt13:50
*** eankutse has quit IRC13:51
*** zehicle has quit IRC13:51
*** sarob has joined #openstack-meeting-alt13:53
*** dguitarbite has quit IRC13:55
*** dguitarbite has joined #openstack-meeting-alt13:56
*** enikanorov has quit IRC13:56
*** enikanorov has joined #openstack-meeting-alt13:56
*** IlyaE has joined #openstack-meeting-alt13:56
*** sacharya has quit IRC13:57
*** noslzzp has joined #openstack-meeting-alt14:01
*** HenryG has quit IRC14:04
*** demorris has joined #openstack-meeting-alt14:04
*** yamahata has quit IRC14:04
dguitarbitesarob: hi, wheres Colin? didn see him for some time14:04
*** colinmcnamara has joined #openstack-meeting-alt14:06
*** colinmcnamara has quit IRC14:06
*** colinmcnamara has joined #openstack-meeting-alt14:06
colinmcnamaraSorry I'm late14:06
dguitarbitehi colinmcnamara14:06
dguitarbitemeetings not yet started14:07
colinmcnamaraOk, is Sean on ?14:07
dguitarbitecolinmcnamara: ping14:07
*** zehicle_at_dell has joined #openstack-meeting-alt14:07
dguitarbiteyea14:07
dguitarbitehe is online14:07
dguitarbitehe is talking to anne gentle as of now14:07
*** sarob has quit IRC14:07
colinmcnamaraK14:07
*** amitgandhi has left #openstack-meeting-alt14:08
colinmcnamaraK, then we will wait for Sean14:08
*** joel_c has quit IRC14:09
*** yamahata has joined #openstack-meeting-alt14:10
dguitarbitejust ping him once14:10
colinmcnamaraI'm checking. I think he might be getting up to 10,000 feet. Before he can log on14:11
colinmcnamaraNope, his flight is at 8:3014:12
colinmcnamaraMine is in 30 min14:12
colinmcnamaraCalling him now14:12
*** dguitarbite has quit IRC14:13
*** HenryG has joined #openstack-meeting-alt14:13
*** dguitarbite has joined #openstack-meeting-alt14:13
colinmcnamaraSean will be on in 5 min or so, he is getting through the airport14:13
*** dguitarbite has quit IRC14:14
*** gokrokve has joined #openstack-meeting-alt14:14
colinmcnamaraDifferent airport than me btw14:14
*** dguitarbite has joined #openstack-meeting-alt14:15
*** yamahata has quit IRC14:15
dguitarbitealrite14:16
*** dguitarbite has quit IRC14:16
*** dguitarbite has joined #openstack-meeting-alt14:16
*** sarob has joined #openstack-meeting-alt14:16
sarobI'm back14:16
*** yamahata has joined #openstack-meeting-alt14:17
sarobSecurity line took longer than expected14:17
*** dkehn has quit IRC14:17
dguitarbitehi14:17
sarobMeeting start?14:18
*** gokrokve has quit IRC14:18
sarobWho's here?14:18
dguitarbitego14:18
dguitarbiteim here14:18
*** colinmcnamara has quit IRC14:19
sarob#startmeeting training-manuals14:19
openstackMeeting started Tue Oct 22 14:19:38 2013 UTC and is due to finish in 60 minutes.  The chair is sarob. Information about MeetBot at http://wiki.debian.org/MeetBot.14:19
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:19
*** openstack changes topic to " (Meeting topic: training-manuals)"14:19
openstackThe meeting name has been set to 'training_manuals'14:19
sarob#topic rst xml devref conversion14:20
*** openstack changes topic to "rst xml devref conversion (Meeting topic: training-manuals)"14:20
dguitarbitetopic? rst to xml?14:20
dguitarbite:D14:20
sarobSo I missed most of the docs meet discussion14:21
sarobI'm confused why they want to go slow14:21
dguitarbitealrite, i guess ill give you the summary on training stuff14:21
sarobHelp me understand14:21
dguitarbitetill colin comes in14:21
dguitarbitealrite, so they wanteed to know whats unique with training manuals14:21
sarobUnique?14:22
*** gokrokve has joined #openstack-meeting-alt14:22
dguitarbite1. They think that this is closer to user groups, they clearly have not understood hackathon's purpose14:22
dguitarbiteunique in d sense14:22
dguitarbitewhats is different from manuals14:22
dguitarbitetheres a bit of confusion there14:23
dguitarbite2. Anne has a point, she will hesitate to touch Havanna branch as she has to keep it stable ...14:23
sarobSo I want to get all the devref rst available in xml so we can work14:23
sarobWhere's the confusion?14:24
dguitarbiteyes so that goes in Icehouse14:24
sarobIt goes online14:24
dguitarbitethe point put up by them is that, the tools for openstack docs nearly stable and so the the content14:24
sarobRst devref goes into Havana14:24
sarobTools?14:25
dguitarbitein the sense the Rst devref will convert14:25
dguitarbiteloads of content14:25
sarobNow I'm really confused14:25
*** SergeyLukjanov has joined #openstack-meeting-alt14:26
sarobWell yeah there's lots of project rst14:26
dguitarbitealrite Rst Devref automates certain things, they dont want to get it in14:26
dguitarbitethe branch which is about to be stable14:26
sarobWe want to use it rather than it molding14:26
*** ozstacker has joined #openstack-meeting-alt14:26
sarobGreat so we get to wait until when14:27
sarobDid anyone say?14:27
dguitarbitetill the end of this week14:28
sarobAnd then the patch with the conversion14:28
sarobCan come in?14:28
sarobOr something else14:28
dguitarbiteone second14:28
sarobOkay14:29
dguitarbitesome guy is going to work on this for a week14:29
dguitarbiteand then they will decide about it14:29
dguitarbitebut I am not sure if we can rely on that !14:29
dguitarbiteyeah we can patch this convo14:29
sarobHold on a sec14:31
dguitarbitesure14:31
*** SumitNaiksatam has joined #openstack-meeting-alt14:32
*** ozstacker has quit IRC14:33
sarobBack14:33
sarobNermina has offered to help14:33
sarobIt sounds like they want to copy some of the devref rst14:34
sarobWhich would cause major stale content14:34
sarobIf the devref materials are stale then we either update them or move14:35
sarobMove will take time14:35
sarobSo we update first14:35
sarobThen work with projects on the move14:35
*** colinmcnamara has joined #openstack-meeting-alt14:36
sarobCopy is a no go14:36
*** ymht has joined #openstack-meeting-alt14:36
*** ymht has left #openstack-meeting-alt14:37
*** colinmcnamara has quit IRC14:38
*** dguitarbite has quit IRC14:39
*** sacharya has joined #openstack-meeting-alt14:40
*** dguitarbite has joined #openstack-meeting-alt14:42
*** bmelande has joined #openstack-meeting-alt14:42
dguitarbitesorry for that internet issue14:43
sarobBack14:43
sarobNermina discussion14:45
dguitarbitesounds good14:45
sarobColin or Pranav can you finish meet14:45
dguitarbiteis colin on14:45
dguitarbite?14:45
*** tsufiev has quit IRC14:49
*** mestery has quit IRC14:49
*** dguitarbite has quit IRC14:54
*** bmelande has quit IRC14:54
*** bmelande has joined #openstack-meeting-alt14:55
sarobSorry I have to go14:55
sarobClose meet for now?14:56
sarobCatch up later?14:56
sarobI'm too worked up to talk right now anyway14:56
sarob#endmeeting14:57
*** openstack changes topic to "OpenStack meetings (alternate)"14:57
openstackMeeting ended Tue Oct 22 14:57:07 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/training_manuals/2013/training_manuals.2013-10-22-14.19.html14:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/training_manuals/2013/training_manuals.2013-10-22-14.19.txt14:57
openstackLog:            http://eavesdrop.openstack.org/meetings/training_manuals/2013/training_manuals.2013-10-22-14.19.log.html14:57
sarobCrappy meeting14:57
sarobSorry14:57
*** sarob has quit IRC15:02
*** jmontemayor has joined #openstack-meeting-alt15:04
*** SergeyLukjanov is now known as _SergeyLukjanov15:05
*** _SergeyLukjanov has quit IRC15:05
*** amotoki has joined #openstack-meeting-alt15:07
*** malini_afk is now known as malini15:08
*** tanisdl has joined #openstack-meeting-alt15:09
*** geoffarnold has joined #openstack-meeting-alt15:11
*** devios_Lang has joined #openstack-meeting-alt15:12
*** boris-42 has quit IRC15:12
*** vkmc has joined #openstack-meeting-alt15:17
*** vkmc has joined #openstack-meeting-alt15:17
*** dprince has quit IRC15:20
*** SergeyLukjanov has joined #openstack-meeting-alt15:21
*** shivharis has joined #openstack-meeting-alt15:22
*** kgriffs_afk is now known as kgriffs15:23
*** jecarey has joined #openstack-meeting-alt15:25
*** rnirmal has joined #openstack-meeting-alt15:26
SumitNaiksatamhi15:30
SumitNaiksatamNeutron folks here?15:30
*** greg_r has joined #openstack-meeting-alt15:30
bmelandeHi Sumit! Bob Melander here15:30
yamahataHi Sumit15:30
SumitNaiksatamhi Bob, good to see you15:30
SumitNaiksatamhi yamahata15:31
obondarevHi15:31
SumitNaiksatamhi obondarev15:31
shivharishi sumit, hi all15:31
obondarevHi Sumit, folks15:31
greg_rhi, greg here15:31
SumitNaiksatamBob hopefully better time for you? :-)15:31
geoffarnoldhi there15:31
*** SridarK has joined #openstack-meeting-alt15:31
SumitNaiksatamhi shivharis greg_r15:31
SumitNaiksatamhi geoffarnold15:31
*** SergeyLukjanov is now known as _SergeyLukjanov15:31
SumitNaiksatamok lets get rolling15:31
bmelandeSumit: Yes, this time my brain will hopefully work15:32
bmelande:-)15:32
*** _SergeyLukjanov is now known as SergeyLukjanov15:32
enikanorovhi there15:32
SumitNaiksatambmelande: :-)15:32
SumitNaiksatam#startmeeting Networking Advanced Services15:32
openstackMeeting started Tue Oct 22 15:32:13 2013 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.15:32
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:32
*** openstack changes topic to " (Meeting topic: Networking Advanced Services)"15:32
openstackThe meeting name has been set to 'networking_advanced_services'15:32
SumitNaiksatamGreetings!15:32
SridarKHI15:32
*** SergeyLukjanov is now known as _SergeyLukjanov15:32
*** _SergeyLukjanov is now known as SergeyLukjanov15:32
SumitNaiksatamthanks all for joining, its a bit inconvenient for those in PDT, we can try and change that in the future15:32
SumitNaiksatamone request - let's have one conversation thread so as to avoid confusion on what is being discussed15:32
SumitNaiksatami have four broad topics on the agenda15:33
SumitNaiksatambut please feel free to suggest more as we go along15:33
amotokihi15:33
SumitNaiksatamlets first follow up from items we discussed last week15:34
SumitNaiksatamhi amotoki SridarK15:34
SumitNaiksatam#topic service insertion and chaining15:34
*** openstack changes topic to "service insertion and chaining (Meeting topic: Networking Advanced Services)"15:34
SumitNaiksatam#link https://blueprints.launchpad.net/neutron/+spec/neutron-services-insertion-chaining-steering15:34
geoffarnoldcan you list the 4 topics before we dive in15:34
*** HPC_ has joined #openstack-meeting-alt15:34
SumitNaiksatamyeah sure -15:34
SumitNaiksatamthe first one i just mentioned above15:35
SumitNaiksatamthe other three areL15:35
SumitNaiksatamService VMs - mechanism15:35
SumitNaiksatamService VMs - policy (this is your blueprint)15:35
SumitNaiksatamExtensible APIs for advanced services (this is enikanorov's topic)15:35
SumitNaiksatamanything more to add geoffarnold?15:36
geoffarnoldjust that the policy topic needs to embrace vms and physical resources15:36
SumitNaiksatamgeoffarnold: sure15:36
SumitNaiksatamlets discuss when we come to that15:36
SumitNaiksatamgeoffarnold: point well taken, its not just service VMs15:36
SumitNaiksatamok going back to "service insertion and chaining"15:37
obondarevSumitNaiksatam: saw also 'Service agents' topic in your email15:37
obondarevthere was 515:37
SumitNaiksatamquite a few folks posted comments on the google doc, and I have responded15:37
SumitNaiksatamobondarev: ah, sorry I missed that15:37
SumitNaiksatamthanks15:37
SumitNaiksatamI should have not relied on my memory :-)15:38
SumitNaiksatamyes, we will discuss that15:38
SumitNaiksatamok on "service insertion and chaining"15:38
*** HenryG has quit IRC15:38
SumitNaiksatamthis is still WIP, anyone has any thoughts/reservations?15:38
SumitNaiksatamthere were some face to face discussions as well15:38
*** HenryG has joined #openstack-meeting-alt15:38
SumitNaiksatamand good feedback15:38
SumitNaiksatamfolks got a chance to read the google doc?15:39
SumitNaiksatami know last time some folks had not yet read it15:39
SumitNaiksatamenikanorov: sent a couple of comments over email15:40
bmelandeSumit: Is the list of use cases indicating what will be targeted first?15:40
SumitNaiksatambmelande: good question15:40
*** enikanorov1 has joined #openstack-meeting-alt15:40
SumitNaiksatami don't think we can bite that much right away15:40
SumitNaiksatamseems like Nachi is not here15:41
*** enikanorov1 has quit IRC15:41
bmelandeAgree, seems ambitious to attempt to cover all in I15:41
SumitNaiksatamwe were discussing earlier - for implementation we might just try to do a basic chain first - firewall and VPN15:41
*** enikanorov has quit IRC15:41
*** enikanorov_ has joined #openstack-meeting-alt15:41
SumitNaiksatambmelande: hopefully the API and model can handle all other chains as well15:42
SumitNaiksatambmelande: but we won't target that for reference implementation15:42
SumitNaiksatambmelande: certainly vendors can support a lot more15:42
*** jcoufal has quit IRC15:43
SumitNaiksatamany thoughts on the single service insertion?15:43
amotokiSumitNaiksatam: I am reading it now. I will leave comment or mail to you. I haven't fully understand service_insertion_types BITW and tap are represented in neutron model.15:44
SumitNaiksatamso we all in agreement, so far on the proposal? ;-)15:44
enikanorov_the question on workflow: is it going to change if we introduce insertion mode?15:44
SumitNaiksatamamotoki: thanks15:44
SumitNaiksatamamotoki: there is currently no example of BITW and Tap15:45
enikanorov_workflow of service creation15:45
enikanorov_i meant15:45
SumitNaiksatamamotoki: actually currently we have only L3 based15:45
SumitNaiksatamamotoki: so in that context, I think the key is to be able to capture the insertion_context correctly for these modes15:46
SumitNaiksatamwhat we have in the design spec is a suggestion, but i think we can evolve that15:46
SumitNaiksatamlooking forward to your comments15:46
geoffarnoldI would like to see more end-to-end workflow analysis15:47
SumitNaiksatamenikanorov_: the workflow might not change if we use default insertion mode, right?15:47
enikanorov_yes, I guess the ability to use default should remain15:47
SumitNaiksatamenikanorov_: or you have identified some deviation?15:47
geoffarnoldall the way from EC2 API calls to low level actions15:47
SumitNaiksatamgeoffarnold: will try :-)15:48
enikanorov_that's only question i have at the moment on insertion15:48
SumitNaiksatamenikanorov_: ok let's work through the workflow for each of LBaaS, FWaaS and VPNaaS15:48
SumitNaiksatamnot here, offline that is :-)15:48
enikanorov_sure15:48
SumitNaiksatam#action SumitNaiksatam to work with enikanorov_ on workflow15:49
SumitNaiksatam#action geoffarnold to review :-)15:49
geoffarnoldyup ;-)15:49
SumitNaiksatamamotoki: more thoughts, or should we move to the next topic?15:49
amotokiSumitNaiksatam: go ahead now.15:50
geoffarnoldnext. tempos fugit15:50
SumitNaiksatam#topic common L3 agent framework15:50
*** openstack changes topic to "common L3 agent framework (Meeting topic: Networking Advanced Services)"15:50
SumitNaiksatamI believe Nachi is not here15:50
SumitNaiksatamobondarev: you had some thoughts?15:50
enikanorov_i'm not fuly aware of activity on this front. Have we moved to l3 agent that loads service drivers?15:51
SumitNaiksatamlast time we discussed: https://docs.google.com/presentation/d/1e85n2IE38XoYwlsqNvqhKFLox6O01SbguZXq7SnSSGo/edit#slide=id.p15:51
SumitNaiksatamenikanorov_: I don't think so15:52
SumitNaiksatamenikanorov_: at least not for fwaas15:52
bmelandeAre there additional documents/bps to the one that Nachi has made on this topic?15:52
SumitNaiksatamenikanorov_: and vpnaas still inherits15:52
enikanorov_i thought that was a consensus back in time when the code was pushed15:52
enikanorov_SumitNaiksatam: I see15:52
SumitNaiksatambmelande: not that i am aware off, sorry i should have researched15:53
amotokimy question is "do we need to implement all services on a single l3-agent?" An alternative is to chain l3-agent namespaces though i am not sure it can cover all possible cases.15:53
SumitNaiksatambmelande: i was thinking nachi was going to be here15:53
SumitNaiksatamamotoki: good point on chaining namespaces15:53
SumitNaiksatamamotoki: that makes it easier to realize service chains as well15:53
SumitNaiksatamamotoki: is that something you want to propose?15:54
amotokinothing from me15:54
SumitNaiksatamor if you have already, pointer will help15:54
SumitNaiksatamamotoki: ok15:54
amotokii have no material at now. just an idea.15:54
yamahataIs there any expecation of number of chains?15:54
enikanorov_folks, could you explain what is namespaces chaining?15:54
SumitNaiksatamamotoki: go ahead15:55
amotokiwhat i am thing is to create several namespace and create veth paris between two namespace.15:55
enikanorov_ok, i see15:55
SumitNaiksatamto add to that, each service specific construct will be in a different namespace15:56
shivhariswith namespaces we may be limited to one host service chainging?15:56
enikanorov_remember we have l3 agent scheduling, so in case of service chaining whole chaing should be scheduled to 1 agent15:56
enikanorov_(just thinking aloud)15:56
SumitNaiksatamso for example, fwaas rules in a different namespace15:56
*** markwash has joined #openstack-meeting-alt15:56
SumitNaiksatamamotoki: right?15:56
amotokiwhat do you mean by "fwaas rules in a different namespace"?15:57
amotokiwhat i think is VPNaaS in one ns and FWaaS in another.15:57
*** demorris has quit IRC15:58
SumitNaiksatamamotoki: the fwaas functionality is realized as iptables configuration in the same namespace as the router15:58
SumitNaiksatamamotoki: exactly15:58
SumitNaiksatamamotoki: thats what i meant15:58
shivharisamotoki: with namespaces we may be limited to one host service chainging?15:58
geoffarnoldDoes this assume L3 agent is managed by a driver under an L3 plugin (to accommodate alternative L3 providers, HW and SW)?15:58
SumitNaiksatamok folks, hang on15:58
geoffarnoldSame pattern as LBaaS15:58
bmelandeHow about evolving the L3 agent so it can configure remote "entities"?15:58
SumitNaiksatamwe have some questions in the buffer15:58
SumitNaiksatamone sec15:58
SumitNaiksatamlets answer yamahata's question first15:59
amotokiwe need to investigate it more...15:59
SumitNaiksatamyamahata: can you clarify what you mean by the number of chains?15:59
SumitNaiksatamyamahata: the API and model should be agnostic of the number of chains16:00
yamahataI concerned too many netns and veth. performance degradation.16:00
SumitNaiksatamyamahata: ah, ok16:00
amotokiyamahata: i agree.16:00
yamahataProbably it can be addressed later for performance and scalability.16:00
SumitNaiksatamyamahata: that is implementation16:00
*** devios_Lang has quit IRC16:00
SumitNaiksatamyamahata: right, but good point to keep in mind16:00
amotokiwe need to check the performance when we talk about l3-agent implementation.16:00
SumitNaiksatamamotoki: agreed16:01
yamahataSumitNaiksatam, agreed.16:01
bmelandeWon't that be part of scheduling16:01
bmelandei.e taking into account performance16:01
SumitNaiksatamnext question was from shivharis16:01
SumitNaiksatamshivharis: we are talking about this in the context of reference of implementation16:01
*** dkehn has joined #openstack-meeting-alt16:02
SumitNaiksatamshivharis: that already uses namespace implementation and is limited to the host on which the L3 agent runs16:02
SumitNaiksatamshivharis: chaining namespaces would not change any of that16:02
shivhariswe should be able to chain not only with namespace, but across hosts as well16:02
SumitNaiksatamnext question was from geoffarnold16:02
amotokishivharis: in the current model it may be limited on one host, but we can enhance neutron model and implemetnation to connect two interfaces on differnt host with p-to-p link.16:03
shivharisok, for now16:03
shivharismake it general purpose later16:03
geoffarnold"one host" is useless for real world16:03
SumitNaiksatamgeoffarnold: we are talking in the context of reference implementation, which only deals with SW not HW16:03
geoffarnoldso am i16:04
SumitNaiksatamgeoffarnold: :-)16:04
SumitNaiksatamgeoffarnold: thats reference implementation16:04
SumitNaiksatamgeoffarnold: we can have a separate discussion on how to enhance it16:04
geoffarnoldframework should accommodate both simple ref imll and real world16:05
shivharisfor reference implementation it should be ok16:05
geoffarnoldimpl16:05
SumitNaiksatambmelande: i think your question is along similar lines16:05
SumitNaiksatamgeoffarnold:  good point16:05
bmelandeSumitNaiksatam: Yes it was :-)16:05
SumitNaiksatam#action suggestion to enhance L3 agent framework, nacho to contact geoffarnold shivharis16:05
SumitNaiksatam#action suggestion to enhance L3 agent framework, nachi to contact geoffarnold shivharis16:06
geoffarnoldand bob16:06
SumitNaiksatamlets take the next topic16:06
SumitNaiksatam#action suggestion to enhance L3 agent framework, nachi to contact geoffarnold shivharis bmelande16:06
SumitNaiksatamhappy? :-)16:06
*** demorris has joined #openstack-meeting-alt16:06
bmelandegeoffarnold: Yes, thanks, I want to be part of that discussion too16:06
SumitNaiksatam#topic Service VMs - Mechanism16:06
*** openstack changes topic to "Service VMs - Mechanism (Meeting topic: Networking Advanced Services)"16:06
SumitNaiksatam#link https://blueprints.launchpad.net/neutron/+spec/adv-services-in-vms16:07
*** markwash has quit IRC16:07
SumitNaiksatamgreg_r: there?16:07
greg_ryes, thanks16:07
*** yamahata has quit IRC16:07
greg_rgood input from ftf last week16:07
SumitNaiksatamwant to give a quick summary of the discussion over the last week?16:07
*** yamahata has joined #openstack-meeting-alt16:07
*** lsmola has quit IRC16:07
greg_rgathering up feedback from comments and from the ftf16:08
greg_rmajor item is the data model16:08
greg_rand the use cases16:08
greg_rone point i would like to clarify is implementation16:08
greg_rof the 4 use cases identified, want to understand most common case16:09
greg_rthe 4 use cases are:  private, shared, multi-service, and scale-out16:09
greg_rmy guess is that the first one, private, is the simplest and most common case16:10
SumitNaiksatamgreg_r: i vote for starting with private16:10
bmelandegreg_r: I have been time to spend on implementation and is offering to help with that.16:10
greg_rand so would be most likely to be the first to implement16:10
bmelandegreg_r: have been -> have been given16:10
SumitNaiksatambmelande: thats great16:10
greg_rit sounds like we are in agreement?16:11
geoffarnoldclarification....?16:11
greg_rtop priority to implement is private use case.16:11
bmelandegreg_r: But nothing prevents going furhter than that right?16:11
geoffarnoldPrivate - app configures - vs. infrastructure - Neutron configures16:11
greg_rright, only time and resources16:11
geoffarnoldLet's put al of those use cases in an LBaaS context16:12
greg_rgeoffarnold: yes16:12
geoffarnoldrather than abstract16:12
greg_rgeoffarnold: lbaas implemented as a VM, right?16:13
amotoki+1. It is simple. In addition LBaaS instance can work with one port :-)16:13
geoffarnoldso the LBaaS driver cares about the distinction16:13
geoffarnoldyes16:13
SumitNaiksatamwe could do any of LBaaS, FWaaS, VPNaaS whichever is easier16:13
greg_rok, you mean to add in the spec?16:14
SumitNaiksatamenikanorov_ can correct me, but LBaaS is not a VM16:14
obondarevyes16:14
enikanorov_right. reference impl is a process on host16:14
enikanorov_not a vm16:14
geoffarnold"private" is confusing (conflated with "guest mode" where it's a really private part of an app topology)16:14
SumitNaiksatamenikanorov_ obondarev thanks16:14
SumitNaiksatamgeoffarnold: agree, private is confusing16:14
geoffarnoldBut LBaaS ref imll still has a driver, right?16:15
enikanorov_geoffarnold: sure16:15
*** devios_Lang has joined #openstack-meeting-alt16:15
SumitNaiksatamgeoffarnold: driver yes, but not VM16:15
SumitNaiksatamgeoffarnold: all services have drivers today16:15
enikanorov_:-)16:15
geoffarnoldpoint is, above driver nobody knows what the use case  - shared, scale out, etc. - is16:16
bmelandeAnything based on namespaces ought to be pretty easy to put in a VM, or?16:16
SumitNaiksatamat different levels of maturity (before enikanorov_ corrects me :-))16:16
SumitNaiksatambmelande: i agree16:16
geoffarnoldI'm just looking at abstractions16:16
SumitNaiksatamgeoffarnold: you have suggestion on better term to use instead of private?16:16
SumitNaiksatamor we can take this offline16:16
geoffarnoldoffline for taxonomy16:17
amotokiWho manages a service VM in the context "private"? neutorn or a tenant?16:17
SumitNaiksatam#action greg_r geoffarnold to brainstorm on taxonomy16:17
greg_rok16:17
enikanorov_amotoki: i guess neutron. throught the service driver16:17
geoffarnoldamotoki: better be neutron16:17
bmelandeamotoki: Me too, neutron should.16:17
greg_ryes, neutron16:17
SumitNaiksatamenikanorov_: i agree16:17
enikanorov_otherwise it's going to be quite complex for the user16:17
amotokii agree. it is same as what i think.16:18
geoffarnoldUninterested in tenant-managed VMs in this context16:18
SumitNaiksatamok we are running low on time16:18
SumitNaiksatamgreg_r: anything more to add or can we go to the next topic16:18
greg_rgo on16:18
geoffarnoldBut decision as to shared vs. multi-service is a driver issue16:18
SumitNaiksatamfolks, we will have this as on going meeting16:18
SumitNaiksatamso we will be back next week as well16:18
geoffarnoldand then in the bar in Hong Kong16:19
greg_r:)16:19
SridarKdecisions will be faster for sure16:19
SumitNaiksatamgeoffarnold: Ha! (a la chris matthews!)16:19
SumitNaiksatam#topic Service VMs - Policy16:19
*** openstack changes topic to "Service VMs - Policy (Meeting topic: Networking Advanced Services)"16:19
SumitNaiksatam#link https://blueprints.launchpad.net/neutron/+spec/dynamic-network-resource-mgmt16:19
SumitNaiksatamgeoffarnold: over to you16:20
geoffarnoldthis is all about allocating scarce/different resources16:20
SumitNaiksatamgeoffarnold: do you want to bring the rest of us unto speed as to where we are going with this16:20
geoffarnoldhw and sw16:20
geoffarnoldsure16:20
geoffarnoldthe DNRM BP is really all about the end-to-end use cases16:20
geoffarnoldthat makes it too big for OpenStack, but I really don't want to lose the context16:21
SumitNaiksatamgeoffarnold: you mentioned you were going to break it down?16:21
geoffarnoldcanonical use case: how do I (a cloud operator) set things up so production LB traffic goes to the physical F5 fleet and dev/test goes to virtual Netscalers?16:22
geoffarnoldObvious way to break it up is...16:22
geoffarnoldProducer-pool-consumer16:23
geoffarnoldProducer manages (discovers, provisions) resources16:23
geoffarnoldConsumer selects a resource from what's available based on a policy16:23
enikanorov_that looks like a higher level problem than what neutron is solving, no?16:23
geoffarnoldNot really. Look at the inventory blueprint for LBaaS16:24
geoffarnoldMultivendor support is essential16:24
*** ifarkas has joined #openstack-meeting-alt16:24
SumitNaiksatamgeoffarnold: i believe that's enikanorov_ blueprint? :-)16:24
geoffarnoldPhysical resources are (always) scarce16:24
geoffarnoldYup16:24
geoffarnoldSo we need a way of selecting a resource and from that locating the driver that handles it16:25
SumitNaiksatamgeoffarnold: can we make the strategy pluggable?16:25
geoffarnoldM0ost work so far assumes that Neutron API call provides selection criterion16:25
SumitNaiksatamstrategy for selection16:26
geoffarnoldBut that's too limiting - needs to be pluggable16:26
geoffarnoldBingo16:26
SumitNaiksatamok good16:26
SumitNaiksatamso i think one blueprint can be around the framework to support the strategy16:26
SumitNaiksatamwith a dumb default policy16:26
geoffarnoldIt affects all Neutron services where multiple resource from multiple vendors are in play16:27
SumitNaiksatamand then separate blueprints for different stategies16:27
geoffarnold"dumb policy" is right for ref arch16:27
SumitNaiksatamgeoffarnold: exactly16:27
geoffarnoldthat's what out PoC will show in hong kong16:27
SumitNaiksatamgeoffarnold: nice16:27
geoffarnoldour16:27
geoffarnoldBut it does cut across a lot of stuff :-(16:27
SumitNaiksatamgeoffarnold: its good to see end to end action16:28
SumitNaiksatamwe are running short on time16:28
geoffarnoldLet me do the carve-up before next week16:28
SumitNaiksatamgeoffarnold: great16:28
SumitNaiksatamlets move on the next topic?16:28
geoffarnoldAnyone wants to discuss offline, contact me16:28
SumitNaiksatam#topic Extensible API: deal with growing services16:28
*** openstack changes topic to "Extensible API: deal with growing services (Meeting topic: Networking Advanced Services)"16:29
enikanorov_ok16:29
SumitNaiksatamthis is Eugene's proposed topic for the Summit16:29
SumitNaiksatamhttp://summit.openstack.org/cfp/details/2216:29
SumitNaiksatamenikanorov_: over to you16:29
enikanorov_so this one is about how to exopose vendor-specific features through the API16:29
enikanorov_and this is not limited to adv services16:29
enikanorov_i saw similar session proposal for ml2 drivers from amotoki16:29
enikanorov_i guess the same could be applied there16:29
SumitNaiksatamenikanorov_: you mention moving advance services' api to core?16:29
enikanorov_that one of the steps in that direction16:30
enikanorov_but not essential, i guess16:30
SumitNaiksatamok, can you elaborate a little?16:30
enikanorov_in fact we already have extensions for extensions, i think16:30
SumitNaiksatambtw, folks we are at the hour mark16:30
*** bmelande has quit IRC16:30
SumitNaiksatambut i don't think there is another meeting16:30
enikanorov_ok, i'll try to make it short16:30
SumitNaiksatamso we can continue until we are kicked out16:30
SumitNaiksatamenikanorov_: sorry continue16:30
SumitNaiksatamenikanorov_: take your tie16:31
SumitNaiksatamtime16:31
enikanorov_so what i'd like to see is ability for vendors to make their specific extensions that are not in 'common' location16:31
SumitNaiksatamenikanorov_: some plugins are already doing this, right?16:31
enikanorov_that has some benefits, including more simple review/discussions penalty16:31
SumitNaiksatamnicira has some in their private directory structure16:32
enikanorov_*penalty=process16:32
SumitNaiksatamso does big switch and i believe Cisco as well16:32
enikanorov_right16:32
enikanorov_such framework would require dispatching mechanism that will forward rest call to a proper driver16:32
*** greg_r has quit IRC16:33
enikanorov_and at this point i'm insterested in how this could be applied for, say, fwaas16:33
enikanorov_for lbaas it looks relatively simple since we have 'plugin driver' notion16:33
enikanorov_and fwaas seems to have device drivers only16:33
enikanorov_and communication goes through the rpc/agent16:33
SumitNaiksatamenikanorov_: fwaas will comply with the service_type framework16:34
SumitNaiksatamenikanorov_: ok16:34
*** rakhmerov has quit IRC16:34
enikanorov_currently it seems to me that it would require to create the same 'plugin_drivers' for fwaas16:34
*** dmakogon has quit IRC16:34
enikanorov_although they can be trivial16:34
*** geoffarnold has quit IRC16:34
SumitNaiksatamenikanorov_: so the vendor extensions will be in the same neutron tree, right?16:34
*** dukhlov has quit IRC16:35
enikanorov_extensions will be in neutron tree, but they will not be loaded like common extensions16:35
SumitNaiksatamenikanorov_: ah ok16:35
SumitNaiksatamenikanorov_: i missed that part16:35
enikanorov_instead, I'm planning that REST API layer wil ask plugin for resources/attr maps and embed them into the resulting API16:35
enikanorov_instead of checking for 'supported ext alias' and using preloaded comon extension16:36
SumitNaiksatamenikanorov_: when we make an API call for /extensions it will return all the loaded extensions including the ones selectively loaded for the vendors?16:36
enikanorov_this way we could control API set by simply defining providers for the service, and also avoid the need to place vendor's extensions into common space16:36
enikanorov_SumitNaiksatam: that's a good question. I think it should return everything that is supported16:37
enikanorov_everything that is loaded i mean16:37
SumitNaiksatamenikanorov_: you mean supported, or loaded?16:37
SumitNaiksatamenikanorov_: ah ok16:37
SumitNaiksatamenikanorov_: i agree16:37
SumitNaiksatamenikanorov_: this seems like a good approach to me, but I have dived deeper16:38
SumitNaiksatamother folks have thoughts?16:38
SumitNaiksatami think this is pretty relevant with the proliferation of services and related extensions16:38
enikanorov_so essential part of such framework would be dispatching mechanism that will forward rest cals to appropriate driver16:38
SumitNaiksatamand extensions of extensions :-)16:38
SumitNaiksatamenikanorov_: ok16:38
SridarKsorry have not read the BP but where does the dispatching mechanism exist - in the vendor plugin ?16:38
enikanorov_SridarK: yes, i think it should go to the plugin (generic plugin)16:39
SumitNaiksatamenikanorov_: is there a blueprint?16:39
*** HPC_ has quit IRC16:39
SridarKenikanorov_:  thx ok makes sense16:40
*** anteaya has quit IRC16:40
enikanorov_i guess there is no bp for this particular task (dispatching). Currently I'm planning to use api-core-for-services as a scope16:40
SumitNaiksatamenikanorov_: ok16:40
enikanorov_probably it makes sense to break it down to parts16:40
SumitNaiksatamanyone else has thoughts on this?16:40
SumitNaiksatami guess we have slowly started to loose people16:41
enikanorov_i hope i didn't overload folks :)16:41
amotokienikanorov_: thanks. that totally make sense to me. i am thinking simlar but just start to study. I am half asleep....16:41
enikanorov_amotoki: thanks16:41
SumitNaiksatamamotoki: apologies for the timing, thanks a lot of attending16:41
SumitNaiksatam#topic open discussion16:42
*** openstack changes topic to "open discussion (Meeting topic: Networking Advanced Services)"16:42
SumitNaiksatamanything else to discuss, or to put on the agenda for next week?16:42
enikanorov_one remaining thing is16:42
SumitNaiksatamenikanorov_: go ahead16:42
enikanorov_vendor-specific configuration16:42
enikanorov_currently radware is working on their lbaas driver trying to put their conf in neutron.conf16:43
*** yamahata has quit IRC16:43
enikanorov_and they have reasonable question16:43
enikanorov_that it might be not the best place for their specific conf16:43
enikanorov_so it may make sense introduce yet another conf file for services16:43
enikanorov_what do you think?16:43
SumitNaiksatamenikanorov_: i had earlier suggested this for lbaas16:44
*** derekh has quit IRC16:44
SumitNaiksatamenikanorov_: if you recall in the reviews16:44
SridarKWe do this for fwaas16:44
SumitNaiksatamthat time you went with the approach of creating a new section in the neutron.con :-)16:44
SumitNaiksatamsince there seemed to be a proliferation of conf files16:44
SumitNaiksatami think separate might be better16:44
SumitNaiksatamany other items to discuss?16:45
enikanorov_yeah, agree16:45
amotokihow about craeting conf file per service and having "config files" parameter in [default] seciotn in neutron.conf?16:45
enikanorov_(now I agree :)16:45
SumitNaiksatamamotoki: that might work as well16:45
enikanorov_amotoki: what about just specifying needed files in cmd line?16:46
*** mestery has joined #openstack-meeting-alt16:46
amotokiIMO many --config-file is not easy to manage16:46
amotokis/--config-file/--config-file options/16:46
*** markwash has joined #openstack-meeting-alt16:46
enikanorov_so the difficulty is in cmd options or in the number of conf files?16:47
shivharisstuffing everything in neutron.conf should not be encouraged - since we can specify multiple conf files at startup16:47
SumitNaiksatamenikanorov_: will you be capturing this requirement somewhere?16:47
*** SridarK has left #openstack-meeting-alt16:47
SumitNaiksatami mean splitting up the conf file?16:47
enikanorov_SumitNaiksatam: under discussion right now. I hope it will be covered in HK16:47
SumitNaiksatam#action enikanorov_ to capture splitting up of conf files for advances services16:48
SumitNaiksatamok folks, I think its getting too late for amotoki, perhaps for enikanorov_ as well :-)16:48
*** rnirmal has quit IRC16:48
SumitNaiksatamunless there is something else to discuss, we can end this meeting16:48
enikanorov_seems that we had productive discussion :)16:48
SumitNaiksatam#info etherpad for pre-summit discussions on this meeting/topic is here: https://etherpad.openstack.org/p/NeutronAdvancedServices16:48
SumitNaiksatamenikanorov_: thanks for participating16:49
shivharisSumit: thanks for organizing16:49
SumitNaiksatamand to the others as well16:49
enikanorov_+1 shivharis16:49
enikanorov_!16:49
SumitNaiksatamshivharis: thanks16:49
amotokithanks everyone! good night.16:49
SumitNaiksatamamotoki: thanks16:49
SumitNaiksatamalright by everyone16:49
SumitNaiksatam#endmeeting16:49
*** openstack changes topic to "OpenStack meetings (alternate)"16:49
openstackMeeting ended Tue Oct 22 16:49:43 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_advanced_services/2013/networking_advanced_services.2013-10-22-15.32.html16:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_advanced_services/2013/networking_advanced_services.2013-10-22-15.32.txt16:49
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_advanced_services/2013/networking_advanced_services.2013-10-22-15.32.log.html16:49
SumitNaiksatambye16:50
shivharisbye16:50
enikanorov_bye16:50
*** eankutse1 has quit IRC16:50
amotokibye16:50
*** amotoki has quit IRC16:50
*** eankutse has joined #openstack-meeting-alt16:50
*** shivharis has quit IRC16:50
*** ozstacker has joined #openstack-meeting-alt16:53
*** jcoufal has joined #openstack-meeting-alt16:53
*** anteaya has joined #openstack-meeting-alt17:00
*** ozstacker has quit IRC17:00
*** amytron has quit IRC17:03
*** julim has quit IRC17:03
*** fvollero is now known as fvollero|gone17:04
*** julim has joined #openstack-meeting-alt17:06
*** boris-42 has joined #openstack-meeting-alt17:08
*** markmcclain has joined #openstack-meeting-alt17:11
*** IgorYozhikov has joined #openstack-meeting-alt17:17
*** eankutse has quit IRC17:17
*** anteaya has quit IRC17:17
*** colinmcnamara has joined #openstack-meeting-alt17:18
*** rudrarugge has joined #openstack-meeting-alt17:19
*** devios_Lang has quit IRC17:19
*** SergeyLukjanov has quit IRC17:22
*** akuznetsov has quit IRC17:22
*** tzumainn has joined #openstack-meeting-alt17:25
*** arborism has joined #openstack-meeting-alt17:28
*** arborism is now known as amcrn17:28
*** colinmcnamara has quit IRC17:28
*** rakhmerov has joined #openstack-meeting-alt17:29
*** rakhmerov has quit IRC17:29
*** gokrokve has quit IRC17:30
*** gokrokve has joined #openstack-meeting-alt17:31
*** SergeyLukjanov has joined #openstack-meeting-alt17:35
*** gokrokve has quit IRC17:35
*** IlyaE has quit IRC17:37
*** Barker has quit IRC17:40
*** eankutse has joined #openstack-meeting-alt17:41
*** Barker has joined #openstack-meeting-alt17:41
*** eankutse1 has joined #openstack-meeting-alt17:42
*** eankutse1 has quit IRC17:42
*** eankutse1 has joined #openstack-meeting-alt17:43
*** zehicle_at_dell has quit IRC17:44
*** dhellmann-afk is now known as dhellmann17:45
*** eankutse has quit IRC17:46
*** SumitNaiksatam has quit IRC17:51
*** gokrokve has joined #openstack-meeting-alt17:51
*** IlyaE has joined #openstack-meeting-alt17:58
*** nikhil is now known as nikhil|afk17:58
*** anteaya has joined #openstack-meeting-alt18:01
*** anteaya has quit IRC18:08
*** anteaya has joined #openstack-meeting-alt18:10
*** SumitNaiksatam has joined #openstack-meeting-alt18:12
*** amytron has joined #openstack-meeting-alt18:12
*** gokrokve has quit IRC18:14
*** gokrokve has joined #openstack-meeting-alt18:15
*** anteaya_ has joined #openstack-meeting-alt18:16
*** anteaya has quit IRC18:19
*** gokrokve has quit IRC18:19
*** lsmola has joined #openstack-meeting-alt18:25
*** rakhmerov has joined #openstack-meeting-alt18:30
*** gokrokve has joined #openstack-meeting-alt18:30
*** SergeyLukjanov has quit IRC18:31
*** ozstacker has joined #openstack-meeting-alt18:32
*** IlyaE has quit IRC18:33
*** viktors1 has joined #openstack-meeting-alt18:35
*** rakhmerov has quit IRC18:35
*** demorris has quit IRC18:35
*** viktors1 has left #openstack-meeting-alt18:37
*** viktors1 has joined #openstack-meeting-alt18:38
*** markmcclain has quit IRC18:38
*** viktors1 is now known as viktors_18:40
*** vipul is now known as vipul-away18:46
*** ozstacker has quit IRC18:49
*** anteaya_ is now known as anteaya18:53
*** jistr has joined #openstack-meeting-alt18:54
*** rpodolyaka1 has joined #openstack-meeting-alt18:55
*** derekh has joined #openstack-meeting-alt18:55
*** marios_ has joined #openstack-meeting-alt18:57
*** jrodom has joined #openstack-meeting-alt18:58
*** gokrokve has quit IRC18:59
SpamapSlifeless: ahoy!19:00
lifelessahoy19:00
rpodolyaka1o/19:01
pleia2o/19:01
lsmolahello19:01
lifeless#startmeeting tripleo19:01
jistrhi19:01
openstackMeeting started Tue Oct 22 19:01:05 2013 UTC and is due to finish in 60 minutes.  The chair is lifeless. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
viktors_hi19:01
marios_hi19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
ifarkashi19:01
*** openstack changes topic to " (Meeting topic: tripleo)"19:01
openstackThe meeting name has been set to 'tripleo'19:01
noslzzphi19:01
*** ccrouch has joined #openstack-meeting-alt19:01
jcoufalo/19:01
slaglehi19:01
tzumainnhiya19:01
*** gokrokve has joined #openstack-meeting-alt19:01
shadowerhola19:01
derekho/19:01
dkehnhi19:01
lifeless#agenda19:02
lifeless     bugs19:02
lifeless    reviews19:02
lifeless    Projects needing releases19:02
lifeless    CD Cloud status19:02
lifeless    CI virtualized testing progress19:02
lifeless    Insert one-off agenda items here19:02
lifeless    review kanban19:03
lifeless    review the tweaked reviewer rules19:03
*** Ng has joined #openstack-meeting-alt19:03
lifeless    open discussion19:03
lifeless#topic bugs19:03
*** openstack changes topic to "bugs (Meeting topic: tripleo)"19:03
lifeless#link https://bugs.launchpad.net/tripleo/19:03
lifeless#link https://bugs.launchpad.net/diskimage-builder/19:03
lifeless#link https://bugs.launchpad.net/os-refresh-config19:03
lifeless#link https://bugs.launchpad.net/os-apply-config19:03
lifeless#link https://bugs.launchpad.net/os-collect-config19:03
lifeless#link https://bugs.launchpad.net/tuskar19:03
lifeless#link https://bugs.launchpad.net/tuskar-ui19:03
lifeless#link https://bugs.launchpad.net/python-tuskarclient19:03
lifelessalso good morning everyone19:03
jtomasekhi19:03
lifelesswe have bug 1241042 which is a firedrill19:04
lifelessdevtest is broken19:04
*** dmakogon has joined #openstack-meeting-alt19:04
derekhSo https://bugs.launchpad.net/tripleo/+bug/1241042  , after I reported it and tried a few things my time got sucked away on something else19:04
lifelessand we have multiple untriaged bugs19:04
*** markmcclain has joined #openstack-meeting-alt19:04
dkehnithout a REALLY good reason19:04
lifelesse.g. https://bugs.launchpad.net/os-apply-config/+bug/124326319:05
* SpamapS closes one old untriaged bug19:05
rpodolyaka1lifeless: derekh's patch is very close to fix bug 1241042, I tested it today, there is one small issue with nova config template19:06
SpamapSOh, I just realized I'm not subscribed to bugmail for oac19:06
lifelessrpodolyaka1: sorry to pick on that bug19:06
lifelessrpodolyaka1: but you filed it without triaging it19:06
marios_lifeless: i think i hit https://bugs.launchpad.net/tripleo/+bug/1241042 be the reason heat stack create for overcloud falied (even though nova instances came up) on 2 separate boxes today19:06
lifelessrpodolyaka1: importance 'undecided'19:06
rpodolyaka1lifeless: for some reason being in tripleo team on launchpad I can't  triage in os-apply-config :(19:06
lifelessrpodolyaka1: ok, lets fix that!19:06
lifelesseveryone: if you find you can't do something you should be able to do, raise it!19:07
lifelessoac had a per-project team for no good reason, switching it to tripleo19:07
lifelessdone19:07
SpamapStuskar should be changed to tripleo too19:08
lifelesshttps://bugs.launchpad.net/tripleo/+bug/1240753 also wasn't triaged though19:08
* rpodolyaka1 triages19:08
lifelessI would ask 'is everyone making a little time to do triage'19:08
lifelessbut since we have bugs untriaged for > a week19:08
lifelessthe answer is no :(19:08
lifelessincluding me, obviuosly19:08
lifelessMy excuse this week is that we've had a super busy time @ HP with conference proposals for an internal thing19:09
* lifeless is sorry19:09
lifelesshowever, as a group - we need to do better.19:09
lifelessAny ideas on how ?19:09
SpamapSI am a big believer in a unified view that helps us drive to 019:10
SpamapSbut, in the past that has required writing little one-off launchpad scripty things to generate a report.19:10
lifelessok19:11
lifelessI agree, would be wonderful19:12
*** SergeyLukjanov has joined #openstack-meeting-alt19:12
lifelessbut ponies.19:12
lifelessUnless we want to commit to triaging all of OpenStakc19:12
lifelesswhich I think would be a bit tough until everyone gets on board19:12
SpamapSWe do deploy all of OpenStack.. so there would be value in doing so.. but I'm not sure we can absorb the cost of all the irrelevant things we'd have to filter out.19:13
lifelesshowever, can I get everyone to commit to - just one, one day, over the next week visiting the meetings page, ctrl-clicking on the bug section links, scrolling to the bottom and triaging all 'unknown' importance bugs ?19:13
rpodolyaka1+119:13
lifelessif we make a joint commitment to do that *once* each once a week, I think we can keep on top of it very easily.19:13
shadowerya19:13
* Ng nods19:13
jcoufal+119:14
tzumainnsounds reasonable19:14
lsmolaok19:14
jtomasekok19:14
lifeless#vote +1 if you will triage across all tripleo LP projects [see the meetings page] once a week19:14
jistrok19:14
ifarkas+119:14
shadower+119:14
tzumainn+119:14
lsmola+119:14
lifelesserm, clearly I don't know how to drive mootbot votes.19:14
marios_k19:14
jtomasek+119:14
SpamapS+119:14
Ngdo we want to try and somehow avoid all accidentally doing it all on the same day?19:14
viktors_+119:14
*** SumitNaiksatam has quit IRC19:14
lifelessNg: birthday paradox19:14
slagle+119:14
lifeless+1 from me19:15
ccrouchNg: thats like trying to avoid winning the lottery :-)19:15
*** markmcclain has quit IRC19:15
lifelessok, so thats triage handled.19:15
Ng+119:15
lifelessOnto the critical: this is a firedrill.19:15
*** markmcclain has joined #openstack-meeting-alt19:15
lifelessIt's a bit sad tht /noone/ managed to find time to drive it forwards19:15
derekhtried a updated patch about 2 hours ago that failed, havn't looked at why yet19:16
lifelessThis is another case of joint responsibilities. And yes, company stuff will draw us away : let me apologise again for the HP folk who had papers to write with a deadline19:16
SpamapSI did not know it was in need of driving (or even in existence actually)19:16
shadowerlifeless: I wasn't here, would you elaborate pls?19:16
lifelessSpamapS: ok, so last week we agreed to put firedrills: a) critical in the bug tracker, b) in the firedrill column in trello and c) in the #tripleo channel topic.19:16
*** nadya has joined #openstack-meeting-alt19:17
SpamapSDid not look at any of those since Friday.19:17
lifelessshadower: the change to remove file injection on the cd-undercloud broke devtest because devtest's undercloud isn't being deployed identically to the cd-undercloud19:17
SpamapS(so therein lies the problem.. "SpamapS is scatterbrained" bug has been open for decades)19:18
lifelessSpamapS: today is your tuesday afternoon ?19:18
lifelessSpamapS: anyhow it's not about you specifically19:18
rpodolyaka1so we basically need to use neutron_dhcp_agent and force use_file_injection=False? that should be done by derekh's patch with minor tweaks to nova config template19:19
lifelessthere are 15 odd folk driving tripleo as a whole, each with specialities sure19:19
SpamapSlifeless: aye Tue 12:19 to be exact19:19
*** ozstacker has joined #openstack-meeting-alt19:19
lifelessrpodolyaka1: right, my concern here is that noone - myself included - said 'moving that bug forward is the most important thing for the team'19:19
rpodolyaka1I managed to get working overcloud today but haven't tried to run a user VM yet19:19
lifelessrpodolyaka1: oh, but it sounds like you have - fantastic!19:19
lifelessanyhow, lets not obsess19:20
rpodolyaka1I was close to reproduce/check this yesterday but hit some strage bugs with ext4_resize_fs() :(19:20
derekhrpodolyaka1: I managed to get use_file_injection=False by forcing it to string in heat template (by wraping in quotes)19:20
marios_i got the overcloud vms up but they didn't get the ssh keys (so couldn't init the keystone setup etc)19:21
marios_though that happened very late in afternoon and i left work a few hours ago19:21
derekhrpodolyaka1: will update bug with details after this meeting19:21
lifelessderekh: oh, is this because oac has a bug too ? That bug probably needs to be critical as well, since it's blocking another critical bug.19:21
rpodolyaka1lifeless: no, oac bug looks similar but is irrelevant19:21
rpodolyaka1*it19:22
lifelessrpodolyaka1: oh, ok.19:22
lifelessah, I see, it's the template.19:22
lifelessLets get on that right after the meeting19:22
lifelessany other bug material?19:22
Ng819:22
Ngderp19:23
lifelessorly ? ;)19:23
lifeless#topic reviews19:23
lifeless    http://russellbryant.net/openstack-stats/tripleo-openreviews.html19:23
*** openstack changes topic to "reviews (Meeting topic: tripleo)"19:23
lifeless    http://russellbryant.net/openstack-stats/tripleo-reviewers-30.txt19:23
lifeless    http://russellbryant.net/openstack-stats/tripleo-reviewers-90.txt19:23
lifeless19:23
lifelessStats since the last revision without -1 or -2 (ignoring jenkins):19:23
lifeless    Average wait time: 1 days, 13 hours, 49 minutes19:23
lifeless    1rd quartile wait time: 0 days, 2 hours, 56 minutes19:23
dkehnhttps://review.openstack.org/#/c/50749/19:23
lifeless    Median wait time: 0 days, 4 hours, 3 minutes19:23
lifeless    3rd quartile wait time: 1 days, 4 hours, 29 minutes19:23
lifeless19:23
lifelessLongest waiting reviews (based on oldest rev without nack, ignoring jenkins):19:23
lifelessand19:23
lifeless    6 days, 8 hours, 37 minutes https://review.openstack.org/50341 (Add unique constraint to ResourceClass.)19:24
lifeless    5 days, 19 hours, 58 minutes https://review.openstack.org/52236 (add python-ironicclient to openstack-clients)19:24
lifeless    1 days, 4 hours, 29 minutes https://review.openstack.org/49729 (Add Glance image id to `resource_classes` table)19:24
lifeless    0 days, 4 hours, 20 minutes https://review.openstack.org/50477 (WIP : Add tempest elements)19:24
lifeless    0 days, 4 hours, 3 minutes https://review.openstack.org/53128 (Add James Slagle to tripleo-cd-admins.)19:24
lifelessso overall we're going ok, but there are reviews waiting nearly a week19:24
viktors_Add unique constraint to ResourceClass - there is already two +219:24
jistri'm gonna approve it19:24
viktors_thanks19:25
jistrwe didn't approve because we had failing jenkins at the time19:25
lifelessfair enough, do you know when jenkins got fixed ?19:25
jistrwell it's in the bug that we filled for it19:25
jistrlemme dig it up19:25
lifelessalso you can 'recheck bug XXXX' to probe and find out if jenkins is fixed without causing gate pipeline resets.19:25
lifelessjistr: cool thanks, I'm curious how long the review sat in inventory is all19:26
jistrlifeless: we did a common patch for it with pblaho https://bugs.launchpad.net/tuskar/+bug/124093419:26
lifelesshttps://review.openstack.org/#/c/52236/ looks like gerrit got confused19:26
lifelessI'll ask about that one in -infra19:26
lifelessslagle: btw its good seeing lots of reviews from you - thank you!19:28
lifelessmost folk seem to have stepped up to the plate in fact19:28
lifelesswhich is awesome19:28
slaglelifeless: thanks. been trying to keep up :)19:28
lsmolalifeless, ??  https://review.openstack.org/#/c/52236 , it is waiting for dependency to get in, right?19:29
*** ozstacker has quit IRC19:29
rpodolyaka1indeed19:29
lifelesslsmola: yeah19:29
lifelesslsmola: just had cluebat applied to me in -infra :)19:30
*** SumitNaiksatam has joined #openstack-meeting-alt19:30
lsmolalifeless, :-)19:30
lifelessso the review stats tool could benefit by taking that into account in some fashion19:30
*** rakhmerov has joined #openstack-meeting-alt19:30
lsmolalifeless, +119:30
lifelessoverall, I'm happy with where we are at with reviews: is anyone unhappy? Are you finding reviewing hard? Are you getting reviews in a timely manner? Are they supportive? Are you getting tossed all over by contradictory reviews?19:31
SpamapSlifeless: my only complaint is that non-tripleo programs do not review nearly as rapidly as tripleo programs. ;)19:31
lsmolahehe19:32
SpamapSI've gotten rather spoiled19:32
*** malini is now known as malini_afk19:32
lifelessSpamapS: from a centre of excelllence....19:32
dkehnlifeless: 625 St. Ann Street19:32
lifelessok, next topic19:32
dkehnlifeless: https://review.openstack.org/#/c/50749/19:32
lifeless#topic projects needing releases19:33
*** openstack changes topic to "projects needing releases (Meeting topic: tripleo)"19:33
lifelessdkehn: interesting, did you change the commit id on my draft? I'm going to guess it was 'abandoned' and thus you couldn't push to it19:33
lifelessNg: how did you go getting a release of everything out ?19:33
Nglifeless: tripleo-heat-templates and the three tuskars are still pending, I failed to drive those through in time for today19:34
lifelessNg: ok, want to take the challenge up for another week ?19:34
Ngall the other bits (incubator excepted) got releases last week19:34
Nglifeless: I absolutely do19:34
lifelessNg: since many things have had commits19:34
lifelessNg: we need more releases :)19:34
lifelessNg: cool!19:35
Ngok19:35
lifeless#action ng to push the release wheelbarrow19:35
*** rakhmerov has quit IRC19:35
*** nikhil|afk is now known as nikhil19:35
lifeless#action Ng to push the release wheelbarrow19:35
lifelessis it just me, or am I failing to drive mootbot?19:35
lifelessmeetbot19:35
lifelessok19:36
lifeless#topic CD cloud status19:36
*** openstack changes topic to "CD cloud status (Meeting topic: tripleo)"19:36
lifelessI'll take this one19:36
lifelessThe CD cloud is deploying very reliably *except*19:36
lifelessevery couple of days the mellanox ethernet adapter is losing the plot19:37
lifelessthe symptoms are that it starts failing19:37
lifelessand the logs show DNS lookup errors19:37
lifelessdoing a while true; do host cd-overcloud.tripleo.org; done loop19:37
lifelessresults in one in 20 or so failing19:37
lifelesspings /mtr to the name servers don't show a fail19:37
lifelessI've fixed this by19:38
lifelessrmmod mlx4_en mlx4_core; modprobe mlx4_en; ip address del <undercloud 10.x>/26 dev eth2; ovs-vsctl del-port eth2; ovs-vsctl add-port br-ctlplane eth219:38
lifelessand it comes good for another couple of days19:38
lifelessI've added a card to the 'make things better' column for someone to dig into WTF is going on.19:39
SpamapSlifeless: saucy is out, maybe we should try with its shiny new kernel. :)19:39
lifelessAnyone tried actual workloads on the overcloud ?19:39
lifelessSpamapS: I think that should wait for us being able to actually redeploy the undercloud :>19:39
SpamapSlifeless: yeah we have 3 whole months before raring is dead. :)19:40
* Ng has not tried workloads on the overcloud, I don't actually have any cloudy workloads I could retool for such a thing :/19:40
lifelessremember *everyone* can get overcloud accounts19:41
lifelessjust propose yourself to the incubator19:41
lifelessfree cloud accounts on top-grade hardware. Go for it!19:41
lifelessnext topic in 1 mon19:41
lifeless*min*19:41
Ngand they're only going to erase your data every few hours!19:41
marios_lol19:42
lifelesswell, the passwords are stable19:42
lifelessso if the deployment is automated19:42
lifelessshould be pretty straight forward19:42
lifelessand hey - next MVP is data persistence :P19:42
SpamapSwe should try juju on it19:42
lifeless#topic CI virtualized testing progress19:42
*** openstack changes topic to "CI virtualized testing progress (Meeting topic: tripleo)"19:42
lifelesspleia2: how goes?19:43
pleia2hey, so we now have an experimental check on the tripleo-incubator project19:43
lifeless\o/19:44
lifelessall hail automated tests19:44
pleia2can see it being run on this patch: https://review.openstack.org/#/c/52607/119:44
lifelesspleia2: whats next?19:44
pleia2right now it's just an echo script, but we have images being successfully built and managed in the tripleo cloud from nodepool19:44
pleia2next is Iteration 2 outlined here where we actually make it do something useful: https://etherpad.openstack.org/p/tripleo-test-cluster19:45
*** cody-somerville has joined #openstack-meeting-alt19:45
pleia2no updates on progress here really, have my test nodepool up to get some of the dependencies sorted first (it's currently erroring on some basic things that I need to work out)19:46
lifelessok cool19:46
lifelesspleia2: btw you shouldn't need nodepool for iteration 2 at all19:46
lifelesspleia2: it's all now within other components19:47
pleia2lifeless: hm, fair enough19:47
lifelesspleia2: so if I was hacking on it, I wouldn't be worrying about nodepool for now.19:47
pleia2ok19:47
lifeless#topic review kanban19:48
*** openstack changes topic to "review kanban (Meeting topic: tripleo)"19:48
lifelessso I added this one-off topic19:48
lifelessI'd like folks feedback on the use of kanban so far19:48
lifelesswhats good about it?19:48
lifelesswhats bad?19:48
lifelessWhat would you like changed?19:48
NgI'm bad at keeping track day-to-day of where we are in it19:49
SpamapSI have found its mere presence helps me focus on the immediate.19:49
lifelessNg: do you look at it day to day ?19:49
* derekh same as Ng, just not checking it enough19:49
SpamapSJust seeing trello in my open tabs reminds me "go work on MVP"19:49
rpodolyaka1it's convenient for finding out what folks are currently working on, what current MVPs are19:49
SpamapSand it is quite a sense of pride when I get to move a card to done :)19:50
Nglifeless: no :)19:50
SpamapSI do not look at it day to day, because I am following the "only have one thing assigned to yourself".. so unless I finish one thing a day.. it doesn't get a detailed look until I finish the thing I am doing now.19:51
Ngbetween bug triage and trello, I'm starting to think I need to have a stricter cadence to my days/week where I'm looking around at things more19:51
lifelessso the tension is between flow and unblocking other people19:51
lifelessif we just do our one thing19:51
lifelessit's easy19:51
lifelessbut other folk can get stuck19:51
lifelessrepresented by bugs [untriaged], firedrills [bug/topic/kanban], reviews[no -1/-2]19:52
SpamapSRight, so to me it is "unblock others" followed by "do MVP work"19:52
lifelessSpamapS: yeah19:52
SpamapSThough I admit that unblock has been 99% reviews.19:52
SpamapSAs evidenced by the lack of triage by all of us :)19:52
lifelessSpamapS: so it seems to me we need to poll the metadata for 'is someone out there blocked' at least once a day19:52
lifelessas a team19:53
lifelessbut possibly as individuals too.19:53
lifelessAny other thoughts?19:53
Ngmakes sense19:54
SpamapSseems like that would be worth a tool to do that19:54
lifelessSpamapS: add it to the roadmap ?19:54
Ngmy ponies and rainbows tool would be an IRC bot that notices when I come on in the morning and tells me if there's a firedrill, how many untriaged bugs there are, and suchlike19:55
SpamapSone person could probably whip up an "obvious blockers" report just pulling all of the obvious data into one place that we all start at. Given the number of people involved, probably worth the time to do it.19:55
lifelessSpamapS: as a card we can pickup ?19:55
SpamapSlifeless: yes doing that19:55
lifelesscool19:55
lifelessok, 2nd last topic19:55
lifelessoh and russel just fixed http://russellbryant.net/openstack-stats/tripleo-openreviews.html for us19:55
lifelessapproved patches will no longer show as stuck, because they aren't, its' their deps that are stuck and they will be getting evolved19:56
*** Barker has quit IRC19:56
lifeless#topic  review the tweaked reviewer rules19:56
*** openstack changes topic to "review the tweaked reviewer rules (Meeting topic: tripleo)"19:56
lifelessSo, last week we decided:19:56
lifeless - cd reviews could use two +2's from anywhere19:56
lifeless - multiple author reviews can use a +2 from the submitters19:57
lifelessFeedback on those changes?19:57
lifelessWorking? Keep it? Discard it?19:57
SpamapSkeep it, it has already been used and helped keep the train moving19:57
*** SergeyLukjanov is now known as _SergeyLukjanov19:57
jistrmultiple author rule worked well for us on the Jenkins critical bug19:57
Nglifeless: keep it19:57
rpodolyaka1+119:58
*** _SergeyLukjanov has quit IRC19:58
lifeless#agreed keep the review tweaks we introduced last week19:58
lifeless#topic open discussion19:58
*** openstack changes topic to "open discussion (Meeting topic: tripleo)"19:58
NgI did something on two reviews which I think was slightly outside those rules, but seemed pretty reasonable19:58
lifeless2 minutes y'll19:58
Ngthere was a +2 already, but a typo in the commit message, which I fixed and carried the existing +2 forwards, added my own and Approved19:58
*** ozstacker has joined #openstack-meeting-alt19:59
lifelessNg: thats inside the rules19:59
lifelessNg: you + original author - one +2. Other reviewer second +2. Done.20:00
Ng:)20:00
lifelessNg: the 'approve' button is orthogonal.20:00
lifelessok, tiems pu20:00
lifelessthanks everyone20:00
lifelesstimes up.20:01
lifeless#endmeeting20:01
*** openstack changes topic to "OpenStack meetings (alternate)"20:01
openstackMeeting ended Tue Oct 22 20:01:03 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:01
Ngthanks lifeless :)20:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tripleo/2013/tripleo.2013-10-22-19.01.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tripleo/2013/tripleo.2013-10-22-19.01.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tripleo/2013/tripleo.2013-10-22-19.01.log.html20:01
*** HenryG has quit IRC20:01
lsmolathanks everyone, good night20:01
jistrthanks all, good night20:01
rpodolyaka1night!20:01
*** rpodolyaka1 has left #openstack-meeting-alt20:01
tzumainnthanks all20:01
marios_night20:01
*** tzumainn has left #openstack-meeting-alt20:01
viktors_night20:01
*** viktors_ has left #openstack-meeting-alt20:01
*** jistr has left #openstack-meeting-alt20:02
*** Ng has left #openstack-meeting-alt20:02
*** pcm_ has quit IRC20:03
jcoufalnight20:03
*** Barker has joined #openstack-meeting-alt20:03
*** jcoufal has quit IRC20:03
*** ozstacker has quit IRC20:05
*** julim has quit IRC20:05
*** vkmc has quit IRC20:05
*** SergeyLukjanov has joined #openstack-meeting-alt20:08
*** SergeyLukjanov has quit IRC20:09
*** ccrouch has left #openstack-meeting-alt20:11
*** ccrouch has joined #openstack-meeting-alt20:18
*** sarob has joined #openstack-meeting-alt20:18
*** ccrouch has left #openstack-meeting-alt20:21
*** nadya has quit IRC20:25
*** demorris has joined #openstack-meeting-alt20:27
*** ifarkas has quit IRC20:30
*** vipul-away is now known as vipul20:31
*** rakhmerov has joined #openstack-meeting-alt20:31
*** jtomasek_ has joined #openstack-meeting-alt20:33
*** rakhmerov has quit IRC20:36
*** jtomasek has quit IRC20:36
*** ozstacker has joined #openstack-meeting-alt20:46
*** demorris has quit IRC20:50
*** Barker has quit IRC20:53
*** SergeyLukjanov has joined #openstack-meeting-alt20:53
*** mestery has quit IRC20:53
*** julim has joined #openstack-meeting-alt20:54
*** mestery has joined #openstack-meeting-alt20:54
*** vkmc has joined #openstack-meeting-alt20:55
*** julim has quit IRC20:55
*** ozstacker has quit IRC20:56
*** eankutse has joined #openstack-meeting-alt20:57
*** mestery has quit IRC20:58
*** sarob has quit IRC20:59
*** eankutse1 has quit IRC21:00
*** jcoufal has joined #openstack-meeting-alt21:01
*** Barker has joined #openstack-meeting-alt21:01
*** eankutse has joined #openstack-meeting-alt21:02
*** eankutse has quit IRC21:02
*** mestery has joined #openstack-meeting-alt21:03
*** pdmars has quit IRC21:04
*** cody-somerville has quit IRC21:04
*** malini_afk is now known as malini21:04
*** julim has joined #openstack-meeting-alt21:05
*** sacharya has quit IRC21:05
*** yamahata has joined #openstack-meeting-alt21:07
*** lblanchard has quit IRC21:07
*** julim has quit IRC21:07
*** IlyaE has joined #openstack-meeting-alt21:09
*** julim has joined #openstack-meeting-alt21:11
*** sarob has joined #openstack-meeting-alt21:16
*** jtomasek_ is now known as jtomasek21:18
*** yamahata has quit IRC21:23
*** rakhmerov has joined #openstack-meeting-alt21:31
*** rakhmerov has quit IRC21:36
*** vipul is now known as vipul-away21:37
*** vipul-away is now known as vipul21:39
*** lblanchard has joined #openstack-meeting-alt21:47
*** julim has quit IRC21:49
*** julim has joined #openstack-meeting-alt21:50
*** jcoufal has quit IRC21:59
*** dmakogon is now known as dmakogon_sleepy22:00
*** jcoufal has joined #openstack-meeting-alt22:00
*** vipul is now known as vipul-away22:00
*** amcrn has quit IRC22:03
*** ruhe has joined #openstack-meeting-alt22:04
*** dmakogon_sleepy has quit IRC22:05
*** malini is now known as malini_afk22:05
*** ruhe has quit IRC22:08
*** arborism has joined #openstack-meeting-alt22:09
*** sarob has quit IRC22:09
*** harlowja_ has joined #openstack-meeting-alt22:10
*** harlowja has quit IRC22:11
*** vipul-away is now known as vipul22:12
*** jecarey has quit IRC22:15
*** arborism is now known as amcrn22:16
*** Barker has quit IRC22:23
*** sarob has joined #openstack-meeting-alt22:23
*** rudrarug_ has joined #openstack-meeting-alt22:23
*** ozstacker has joined #openstack-meeting-alt22:25
*** rudrarugge has quit IRC22:26
*** rakhmerov has joined #openstack-meeting-alt22:32
*** harlowja_ has quit IRC22:35
*** harlowja has joined #openstack-meeting-alt22:35
*** derekh has quit IRC22:36
*** rakhmerov has quit IRC22:36
*** amytron has quit IRC22:37
*** rudrarug_ has quit IRC22:38
*** rudrarugge has joined #openstack-meeting-alt22:39
*** jrodom has quit IRC22:40
*** rudrarugge has quit IRC22:43
*** esker has quit IRC22:46
*** harlowja_ has joined #openstack-meeting-alt22:57
*** harlowja has quit IRC22:59
*** jtomasek has quit IRC23:03
*** lsmola has quit IRC23:04
*** lblanchard has quit IRC23:05
*** rudrarugge has joined #openstack-meeting-alt23:09
*** rudrarugge has joined #openstack-meeting-alt23:10
*** jrodom has joined #openstack-meeting-alt23:11
*** julim has quit IRC23:17
*** rudrarugge has quit IRC23:18
*** jcoufal has quit IRC23:18
*** rudrarugge has joined #openstack-meeting-alt23:19
*** jmontemayor has quit IRC23:28
*** rakhmerov has joined #openstack-meeting-alt23:32
*** malini_afk is now known as malini23:34
*** jodom has joined #openstack-meeting-alt23:34
*** jodom has quit IRC23:34
*** rakhmerov has quit IRC23:37
*** kgriffs is now known as kgriffs_afk23:37
*** jrodom has quit IRC23:39
*** lblanchard has joined #openstack-meeting-alt23:47
*** cody-somerville has joined #openstack-meeting-alt23:47
*** cody-somerville has joined #openstack-meeting-alt23:47
*** sarob has quit IRC23:47
*** sarob has joined #openstack-meeting-alt23:47
*** vipul is now known as vipul-away23:51
*** tanisdl has quit IRC23:54
*** vipul-away is now known as vipul23:57

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