Monday, 2015-06-08

*** fallenpegasus has joined #openstack-meeting-400:00
*** fallenpegasus has quit IRC00:04
*** eghobo has joined #openstack-meeting-400:04
*** sdake_ has joined #openstack-meeting-400:06
*** xingchao has quit IRC00:08
*** sdake has quit IRC00:10
*** eghobo has quit IRC00:16
*** markvoelker has joined #openstack-meeting-400:25
*** fallenpegasus has joined #openstack-meeting-400:29
*** markvoelker has quit IRC00:30
*** sdake has joined #openstack-meeting-400:32
*** sdake_ has quit IRC00:35
*** igordcard has quit IRC00:36
*** KunalGandhi has joined #openstack-meeting-400:39
*** saneax has quit IRC00:46
*** amotoki has joined #openstack-meeting-400:55
*** amotoki has quit IRC01:01
*** zehicle_IRL has quit IRC01:03
*** amotoki has joined #openstack-meeting-401:03
*** sdake_ has joined #openstack-meeting-401:06
*** dims__ has quit IRC01:06
*** sdake__ has joined #openstack-meeting-401:08
*** sdake has quit IRC01:09
*** sdake__ is now known as sdake01:09
*** sdake_ has quit IRC01:13
*** amotoki has quit IRC01:14
*** KunalGandhi has quit IRC01:15
*** zehicle_IRL has joined #openstack-meeting-401:18
*** jpeeler has joined #openstack-meeting-401:26
*** galstrom_zzz is now known as galstrom01:39
*** sdake_ has joined #openstack-meeting-401:43
*** sdake has quit IRC01:46
*** sdake has joined #openstack-meeting-401:54
*** sdake_ has quit IRC01:58
*** dims_ has joined #openstack-meeting-401:58
*** dims_ has quit IRC02:03
*** asselin_ has joined #openstack-meeting-402:07
*** markvoelker has joined #openstack-meeting-402:14
*** markvoelker has quit IRC02:19
*** amotoki has joined #openstack-meeting-402:22
*** sdake_ has joined #openstack-meeting-402:25
*** galstrom is now known as galstrom_zzz02:28
*** sdake has quit IRC02:29
*** davidlenwell has quit IRC02:33
*** sdake has joined #openstack-meeting-402:44
*** sdake_ has quit IRC02:48
*** eghobo has joined #openstack-meeting-402:54
*** dims_ has joined #openstack-meeting-403:03
*** aswadr has joined #openstack-meeting-403:04
*** eghobo has quit IRC03:07
*** asselin_ has quit IRC03:09
*** dims_ has quit IRC03:09
*** amotoki has quit IRC03:23
*** fallenpegasus has quit IRC03:23
*** zehicle_IRL has quit IRC03:26
*** cgoncalves has quit IRC03:27
*** bradjones|away has quit IRC03:27
*** mestery_afk has quit IRC03:27
*** asselin has quit IRC03:27
*** guimaluf has quit IRC03:27
*** cgoncalves has joined #openstack-meeting-403:27
*** guimaluf has joined #openstack-meeting-403:28
*** bradjones has joined #openstack-meeting-403:28
*** bradjones has quit IRC03:28
*** bradjones has joined #openstack-meeting-403:28
*** mestery has joined #openstack-meeting-403:28
*** asselin has joined #openstack-meeting-403:28
*** amotoki has joined #openstack-meeting-403:29
*** zehicle_IRL has joined #openstack-meeting-403:32
*** ivar-lazzaro has joined #openstack-meeting-403:46
*** eghobo has joined #openstack-meeting-403:53
*** davidlenwell has joined #openstack-meeting-403:55
*** eghobo has quit IRC03:56
*** armax has joined #openstack-meeting-403:59
*** zehicle_IRL has quit IRC04:01
*** galstrom_zzz is now known as galstrom04:02
*** eghobo has joined #openstack-meeting-404:03
*** galstrom is now known as galstrom_zzz04:03
*** galstrom_zzz is now known as galstrom04:03
*** armax has quit IRC04:04
*** fallenpegasus has joined #openstack-meeting-404:05
*** ivar-lazzaro has quit IRC04:07
*** KunalGandhi has joined #openstack-meeting-404:15
*** KunalGandhi has quit IRC04:20
*** irenab has quit IRC04:26
*** armax has joined #openstack-meeting-404:30
*** eghobo_ has joined #openstack-meeting-404:33
*** armax has quit IRC04:35
*** eghobo has quit IRC04:37
*** IlyaG has quit IRC04:39
*** IlyaG has joined #openstack-meeting-404:40
*** eghobo has joined #openstack-meeting-404:40
*** eghobo_ has quit IRC04:41
*** galstrom is now known as galstrom_zzz04:43
*** asselin_ has joined #openstack-meeting-404:45
*** belmoreira has joined #openstack-meeting-405:20
*** irenab has joined #openstack-meeting-405:25
*** saneax has joined #openstack-meeting-405:27
*** dannywilson has joined #openstack-meeting-405:36
*** dannywilson has quit IRC05:36
*** dannywilson has joined #openstack-meeting-405:37
*** eghobo_ has joined #openstack-meeting-405:38
*** eghobo has quit IRC05:41
*** IlyaG has quit IRC05:45
*** eghobo has joined #openstack-meeting-405:46
*** eghobo_ has quit IRC05:47
*** markvoelker has joined #openstack-meeting-405:52
*** markvoelker has quit IRC05:56
*** belmoreira has quit IRC06:06
*** numan has joined #openstack-meeting-406:22
*** KunalGandhi has joined #openstack-meeting-406:28
*** tobe has joined #openstack-meeting-406:45
*** ajayaa has joined #openstack-meeting-406:51
*** dannywilson has quit IRC06:57
*** GB21 has joined #openstack-meeting-407:08
*** svg has quit IRC07:09
*** eghobo has quit IRC07:16
*** svg has joined #openstack-meeting-407:18
*** KunalGandhi has quit IRC07:27
*** paramite has joined #openstack-meeting-407:31
*** sbalukoff has quit IRC07:32
*** markvoelker has joined #openstack-meeting-407:40
*** matrohon has joined #openstack-meeting-407:40
*** wojdev has joined #openstack-meeting-407:42
*** sbalukoff has joined #openstack-meeting-407:44
*** markvoelker has quit IRC07:45
*** belmoreira has joined #openstack-meeting-408:00
*** matrohon has quit IRC08:05
*** davidlenwell has quit IRC08:06
*** davidlenwell has joined #openstack-meeting-408:09
*** matrohon has joined #openstack-meeting-408:11
*** wojdev has quit IRC08:14
*** IlyaG has joined #openstack-meeting-408:17
*** wojdev has joined #openstack-meeting-408:20
*** IlyaG has quit IRC08:22
*** davidlenwell has quit IRC08:23
*** dims_ has joined #openstack-meeting-408:28
*** davidlenwell has joined #openstack-meeting-408:30
*** numan has quit IRC08:32
*** numan has joined #openstack-meeting-408:33
*** dims_ has quit IRC08:33
*** lazy_prince has joined #openstack-meeting-408:50
*** lazy_prince has quit IRC08:51
*** ajayaa has quit IRC09:00
*** wojdev_ has joined #openstack-meeting-409:16
*** ajayaa has joined #openstack-meeting-409:16
*** wojdev has quit IRC09:18
*** wojdev_ is now known as wojdev09:18
*** markvoelker has joined #openstack-meeting-409:29
*** wojdev has quit IRC09:32
*** markvoelker has quit IRC09:34
*** wojdev has joined #openstack-meeting-409:35
*** kbyrne has quit IRC09:45
*** kbyrne has joined #openstack-meeting-409:48
*** wojdev has quit IRC09:56
*** L33 is now known as lyarwood09:59
*** sdake has quit IRC10:00
*** wojdev has joined #openstack-meeting-410:02
*** dims_ has joined #openstack-meeting-410:09
*** paramite is now known as paramite|afk10:17
*** wojdev has quit IRC10:25
*** Kiall has quit IRC10:29
*** Kiall has joined #openstack-meeting-410:31
*** ajayaa has quit IRC10:46
*** wojdev has joined #openstack-meeting-410:47
*** fallenpegasus has quit IRC10:50
*** ajayaa has joined #openstack-meeting-410:58
*** saneax has quit IRC11:00
*** saneax has joined #openstack-meeting-411:01
*** GB21 has quit IRC11:15
*** paramite|afk is now known as paramite11:17
*** zehicle_IRL has joined #openstack-meeting-411:17
*** ajayaa has quit IRC11:18
*** fesp has joined #openstack-meeting-411:20
*** tobe has quit IRC11:26
*** markvoelker has joined #openstack-meeting-411:30
*** wojdev has quit IRC11:33
*** IlyaG has joined #openstack-meeting-411:33
*** marcusvrn has joined #openstack-meeting-411:35
*** markvoelker has quit IRC11:35
*** ajayaa has joined #openstack-meeting-411:37
*** IlyaG has quit IRC11:38
*** amotoki has quit IRC12:01
*** ajayaa has quit IRC12:07
*** wojdev has joined #openstack-meeting-412:08
*** GB21 has joined #openstack-meeting-412:11
*** xingchao has joined #openstack-meeting-412:13
*** wojdev has quit IRC12:14
*** saneax has quit IRC12:14
*** saneax has joined #openstack-meeting-412:16
*** xingchao has quit IRC12:18
*** fesp is now known as flaper8712:25
*** flaper87 has quit IRC12:25
*** flaper87 has joined #openstack-meeting-412:25
*** rfolco has joined #openstack-meeting-412:31
*** raginbajin has joined #openstack-meeting-412:33
*** lazy_prince has joined #openstack-meeting-412:34
*** VW has joined #openstack-meeting-412:35
*** xingchao has joined #openstack-meeting-412:36
*** klamath has joined #openstack-meeting-412:41
*** klamath has quit IRC12:41
*** klamath has joined #openstack-meeting-412:42
*** paramite is now known as paramite|afk12:43
*** gabriel-bezerra has quit IRC12:50
*** lazy_prince has quit IRC12:50
*** singlethink has joined #openstack-meeting-412:56
*** GeetikaBatra__ has joined #openstack-meeting-412:57
*** GB21 has quit IRC12:57
*** xingchao has quit IRC12:57
*** GeetikaBatra__ is now known as GB2112:58
*** paramite|afk is now known as paramite13:02
*** irenab has quit IRC13:04
*** frobware_ has joined #openstack-meeting-413:08
*** gabriel-bezerra has joined #openstack-meeting-413:08
*** VW has quit IRC13:09
*** xingchao has joined #openstack-meeting-413:11
*** zehicle_IRL has quit IRC13:11
*** markvoelker has joined #openstack-meeting-413:20
*** markvoelker has quit IRC13:25
*** yfried has joined #openstack-meeting-413:31
*** krotscheck has joined #openstack-meeting-413:34
*** frobware_ has quit IRC13:37
*** igordcard_ has joined #openstack-meeting-413:38
*** krotscheck has quit IRC13:38
*** krotscheck has joined #openstack-meeting-413:39
*** krotscheck has quit IRC13:40
*** krotscheck has joined #openstack-meeting-413:41
*** sdake has joined #openstack-meeting-413:48
*** sdake_ has joined #openstack-meeting-414:00
*** VW has joined #openstack-meeting-414:00
*** xingchao has quit IRC14:02
*** sdake has quit IRC14:04
*** IlyaG has joined #openstack-meeting-414:04
*** aventerav has joined #openstack-meeting-414:06
*** IlyaG has quit IRC14:09
*** sigmavirus24_awa is now known as sigmavirus2414:11
*** xingchao has joined #openstack-meeting-414:11
*** dvorak is now known as clayton14:13
*** numan has quit IRC14:20
*** rromans has quit IRC14:22
*** kenhui has joined #openstack-meeting-414:27
*** galstrom_zzz is now known as galstrom14:29
*** britthouser has quit IRC14:34
*** britthouser has joined #openstack-meeting-414:34
*** armax has joined #openstack-meeting-414:42
*** britthouser has quit IRC14:49
*** britthou_ has joined #openstack-meeting-414:49
*** belmoreira has quit IRC15:06
*** markvoelker has joined #openstack-meeting-415:08
*** fallenpegasus has joined #openstack-meeting-415:10
*** IlyaG has joined #openstack-meeting-415:11
*** fnaval has joined #openstack-meeting-415:12
*** carl_baldwin has joined #openstack-meeting-415:12
*** markvoelker has quit IRC15:13
*** jwagner_away is now known as jwagner15:17
*** irenab has joined #openstack-meeting-415:21
*** saneax has quit IRC15:22
*** jwagner is now known as jwagner_away15:25
*** adduarte has joined #openstack-meeting-415:26
*** lazy_prince has joined #openstack-meeting-415:26
*** sbalukoff has quit IRC15:26
*** fitoduarte has quit IRC15:29
*** jwagner_away is now known as jwagner15:29
*** killer_prince has joined #openstack-meeting-415:31
*** mugsie has joined #openstack-meeting-415:32
*** lazy_prince has quit IRC15:35
*** mugsie has left #openstack-meeting-415:37
*** praveens has joined #openstack-meeting-415:38
*** Sukhdev has joined #openstack-meeting-415:39
*** sdake_ has quit IRC15:42
*** naohirot has joined #openstack-meeting-415:42
*** matrohon has quit IRC15:46
*** sdake has joined #openstack-meeting-415:47
*** sdake_ has joined #openstack-meeting-415:48
*** singlethink has quit IRC15:51
*** sdake has quit IRC15:52
*** asselin_ has quit IRC15:55
*** sdake_ is now known as sdake15:56
*** daneyon has joined #openstack-meeting-415:56
*** yushiro has joined #openstack-meeting-415:57
*** eghobo has joined #openstack-meeting-415:58
*** eghobo has quit IRC15:58
*** killer_prince is now known as lazy_prince15:58
*** nlahouti has joined #openstack-meeting-416:00
SukhdevHello Ironic-neutron integration folks16:00
yushiroHello, all16:01
Sukhdevwill wait for a sec for others to show up16:01
pshigehello!16:01
*** rkukura has joined #openstack-meeting-416:01
*** viveknarasimhan has joined #openstack-meeting-416:01
Sukhdevjroll: are you here?16:02
jrollmorning :)16:02
*** kenhui has quit IRC16:02
SukhdevGood morning to all16:02
* jroll adds this to his calendar because he totally forgot16:02
*** rfolco has quit IRC16:02
Sukhdev#startmeeting ironic_neutron16:02
openstackMeeting started Mon Jun  8 16:02:48 2015 UTC and is due to finish in 60 minutes.  The chair is Sukhdev. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: ironic_neutron)"16:02
openstackThe meeting name has been set to 'ironic_neutron'16:02
Sukhdev#topic: Agenda16:03
*** openstack changes topic to ": Agenda (Meeting topic: ironic_neutron)"16:03
Sukhdev#link: https://wiki.openstack.org/wiki/Meetings/Ironic-neutron#Agenda16:03
lazy_princehi all...16:03
*** BertieFulton has joined #openstack-meeting-416:03
jlvillalo/16:03
SukhdevFolks we have a very concentrated agenda this morning16:03
*** devananda has joined #openstack-meeting-416:03
*** fallenpegasus has quit IRC16:03
Sukhdev#topic: Announcements16:03
*** openstack changes topic to ": Announcements (Meeting topic: ironic_neutron)"16:03
*** eghobo has joined #openstack-meeting-416:03
* devananda lurks16:03
SukhdevWe have couple of specs out16:04
*** selvakumar has joined #openstack-meeting-416:04
SukhdevWe should set a goal to get these reviewed and finalized to a point so that we can move forward with implementation16:04
*** JoshNang has joined #openstack-meeting-416:04
Sukhdevthat leads me to my question:16:04
SukhdevI know we have lots of people here who are in listen only mode - are there folks who are willing to jump in and help with the implementation?16:05
SukhdevWe can use volunteers16:05
lazy_princeI would be happy to help..16:05
Sukhdevlazy_prince: cool - thanks16:06
*** marutikamat has joined #openstack-meeting-416:06
Sukhdevanybody else?16:06
*** lauramoore has joined #openstack-meeting-416:06
Sukhdev#topic: Specs for review16:06
*** openstack changes topic to ": Specs for review (Meeting topic: ironic_neutron)"16:06
lazy_princeI think many ppl forgot about the meeting itself..16:06
yushiroSukhdev, Hi, I want to help about that16:07
Sukhdevlazy_prince: I am suspecting that is the case :-)16:07
* jroll will of course be helping16:07
Sukhdevyushiro: cool - thanks16:07
SukhdevLets go through the specs and then you can tell us which area would you like to participate16:07
*** GB21 has quit IRC16:07
SukhdevWe have two specs out - thanks to jroll  and BertieFulton16:07
*** eghobo has quit IRC16:08
SukhdevLets go through them one at a time -16:08
SukhdevFirst start with - https://review.openstack.org/#/c/188528/16:08
SukhdevI see lots of good comments16:08
SukhdevI think there are two critical points that need answered which can move us into the implementation, while the spec is being cleaned up16:09
*** praveens1 has joined #openstack-meeting-416:09
*** amotoki has joined #openstack-meeting-416:09
Sukhdev1) Agreement on the dict contents that needs to go to Neutron -16:09
SukhdevLook at the line 114 comments16:09
*** lucasagomes has joined #openstack-meeting-416:09
*** wanyen has joined #openstack-meeting-416:10
-amotoki- seems succefully joined the channel.16:10
SukhdevThis has to do with LAG/MLAGGed ports - there are several questions16:10
*** praveens has quit IRC16:10
*** eghobo has joined #openstack-meeting-416:10
*** viveknarasimhan has quit IRC16:10
Sukhdevwe need to be able to specify anywhere from one port to all the way 4 ports - that a BM could be connected with16:11
lazy_princeyup..16:11
SukhdevI made a suggestion - did you folks have any opportunity to review it?16:11
*** BertieFulton has quit IRC16:11
Sukhdevany agreements/disagreements/screems?16:11
*** ativelkov has left #openstack-meeting-416:12
*** daneyon_ has joined #openstack-meeting-416:12
* Sukhdev waiting 16:12
amotokiis it specific to ML2? I think we are discussing a general model among neturon/ironic/nova.16:12
jrollthis spec in particular is around what the ML2/ironic interaction and data model looks like16:13
Sukhdevamotoki: correct - but, this has to do with how do we want to represent ports - i.e. port channels, etc16:13
Sukhdevamotoki: ML2 will be the ultimate consumer of this information16:13
amotokiSukhdev: agree.  it is on how we describe a port.16:13
jrollSukhdev: so just one thing, I think the reply's to morgabra's question there are a different thing than what he's asking16:13
SukhdevHence, we need a concrete agreement - so that implementation can move forward16:14
jrollSukhdev: say we have two port groups. we want to connect two networks16:14
*** viveknarasimhan has joined #openstack-meeting-416:14
jrollis there a plan for picking which group connects to each network?16:14
*** daneyon has quit IRC16:14
*** yamahata has joined #openstack-meeting-416:15
*** rfolco has joined #openstack-meeting-416:15
Sukhdevjroll: yes, in this case, Ironic add_network() method (called out in your spec) will invoke neutron port_create() with one port-channel group only16:15
Sukhdevand will repeat port-create for each network16:15
lazy_princeyes but which one..?16:15
jrollSukhdev: how does the user decide? (or do they decide at all)16:15
jrollright16:15
jrollhow do I, as a user, tell ironic that I want port(group) A to connect to network Z, and port(group) B to connect to network X16:16
SukhdevLook at line 185 - API proposal that i have16:16
jrolland not the other way around16:16
lazy_princeI could have a one groups with two nics with 10Gb and another with two nics with 1Gb16:16
Sukhdevthey will pick the port group that they would have created16:16
*** shivharis has joined #openstack-meeting-416:17
jrollSukhdev: when I do 'nova boot' how do I decide what ports should connect to what network?16:17
SukhdevLine 185 comment was going to be my second critical point which requires agreement - so, you walked me right into it :-)16:17
amotokiWe need to agree is how to represent a port. A port may be a single port, aggregated port like lag, port-channel.16:17
amotokiwe can reprensent a port as either name or port number.16:18
Sukhdevjroll: Good question -16:18
jrollamotoki: that has been mostly decided; the spec outlines what we've generally agreed on16:18
viveknarasimhanironic should create networks for its port16:18
viveknarasimhanbefore creating the ports16:18
viveknarasimhanthemselves16:18
Sukhdevamotoki: jroll has a good question as to how to decide which port to connect to which network16:18
amotokiSukhdev: yes16:19
viveknarasimhanthere should be user-input to ironic interface (REST API ) which user provides information16:19
*** Swami has joined #openstack-meeting-416:20
jrollviveknarasimhan: ironic is an admin-only api. what about users that only interact with nova and don't have access to the ironic api?16:20
rkukuraIt seems to me that connecting a single NIC to multiple networks depends on neutron implementing trunk ports first. Am I missing something?16:20
Sukhdevjroll, amotoki : can we not pick any port - as long as the BM is connoted to correct network -16:20
lazy_princeviveknarasimhan: networks will be managed by Neutron... and network details are provided when performing nova boot..16:20
jrollSukhdev: technically, yes. in reality I might have a 10g nic that I want in a certain network, and a 1g nic I want in another network16:20
viveknarasimhanthen the nova user has to use a pre-created neutron network when port-create is done for ironic port16:20
jrollviveknarasimhan: sure, how does ironic know *which port* to attach to *which network*?16:21
Sukhdevjroll: Does nova allow today to pick a nic/port to specified at the nova boot time?16:21
jrollSukhdev: no, because all virtual nics are created equal :)16:21
amotokiI think we can know which interfcace/port group is connected to which network. It is a part covered by a process of discovery.16:21
lazy_princerkukura: correct.. but here, we need to decide access mode for port groups when multiple port groups are available..16:22
amotokiwoops..... which port is connected to which SWITCH PORT/NAMED PORT.16:22
Sukhdevjroll: So, I see two ways to address this - 1) Ironic picks without any user input 2) we add an option to mova boot to specify nic/port16:23
jrollSukhdev: right. I think (2) is the most useful, but as we'll need to fall back to (1) in the case of "I don't care", maybe we do (1) first and build on that16:23
Sukhdevamotoki: once we know the ports (through discovery), how do we know the wish of user that which port he wants to connect to which network - that is jroll's point16:24
jrollSukhdev: I just don't want to lose track of (2) while we're doing (1)16:24
Sukhdevjroll: I am in favor of 1) for now16:24
amotokiif there is no input from users, can't we pick up any port?16:24
lazy_princecan we first focus on functionality and then tailor it for specific use cases like pin pointing the network to a nic/port group..?16:24
Sukhdevjroll: agree - we can make a note of 2) in the spec (I can add to wiki as well) for long term items to track16:25
jrolllazy_prince: +116:25
Sukhdevamotoki: that will be option 1)16:25
Sukhdevlazy_prince: +116:25
morgabraSukhdev: jroll: another concerning thing I just heard: We should certainly allow the same port/port group to attach to multiple networks, there's no reason the neutron plugin could not trunk multiple networks over the same port16:25
morgabrain fact, we do that with our hacky plugin today16:25
jrollagree16:26
Sukhdevmorgabra: that work is in progress in neutron - but, not yet available - we will allow that as soon as it becomes available in neutron16:26
*** viveknarasimhan_ has joined #openstack-meeting-416:26
Sukhdevmorgabra: This was discussed in Summit during design - it is documented on the ehterpad16:26
lazy_princeyup.. lets focus on simple use cases like 1 nic to 1 network...16:26
SukhdevLets get back to the point where we started from16:27
*** viveknarasimhan has quit IRC16:27
SukhdevLets go back to line 114 comments - i.e. how do we want to represent the ports to neutron16:27
viveknarasimhan_checking connectivity to webchat server - ping16:28
SukhdevPlease see my comment - and see if you agree/disagree or want to screem :-)16:28
Sukhdevviveknarasimhan_ ?16:28
jrollviveknarasimhan_: 1 packets transmitted, 1 received, 0% packet loss, time 0ms16:28
jroll:)16:28
*** puranamr has joined #openstack-meeting-416:28
viveknarasimhan_Sukhdev: i missed your comment , was punted out of room :)16:28
viveknarasimhan_Sukhdev: can you please post your comment again16:29
Sukhdevviveknarasimhan_: see my comment on line 11416:29
*** selvakumar has quit IRC16:29
jrollSukhdev: so your proposal is a list of ports, which may or may not be a list of port groups?16:30
Sukhdevviveknarasimhan_: as to how do we represent the physical ports to neutron - morgabra and lauramoore had raised a concern, I sort of made a proposal there16:30
viveknarasimhan_list of local _link_information16:30
jrollI'm not sure I understand this proposal16:30
Sukhdevjroll: It is a list of port groups - and port group is a list of ports16:30
Sukhdevjroll: so this gives you ability to pass anywhere from 1 to 4 ports - or more port groups16:31
*** banix has joined #openstack-meeting-416:31
jrollit's port groups all the way down then?16:31
viveknarasimhan_Sukhdev:  i see that you propose a list of local_link_information for LAG Ports16:32
viveknarasimhan_Sukhdev: that is fine with me16:32
Sukhdevjroll: sorta - this gives you all possibilities - and see keeps things consistent and simple - unless anybody has a creative way16:32
Sukhdevs/see/still16:32
*** GB21 has joined #openstack-meeting-416:33
*** praveens1 has quit IRC16:33
*** singlethink has joined #openstack-meeting-416:33
jrollI don't see why a port group needs to be a maximum of two ports, personally16:33
Sukhdevjroll: it does not have to be - but, most of the times, I have seen it that way -16:34
lazy_princewhy not keep all available port in same port group for now...16:34
*** Nisha has joined #openstack-meeting-416:34
Sukhdevjroll: but, this proposal does not limit you to only 2 - I only used it as an example16:34
jroll+116:34
jrolla port group defines a single logical connection16:34
lazy_princeand relook at it when thhings start working..16:34
viveknarasimhan_Sukhdev:  Neutron would come to know16:35
Sukhdevjroll: port-group is really a list of ports - its does not limit to only 2 - it can be 1 or more ports16:35
viveknarasimhan_Sukhdev: Or would neutron need to know if its being passed a port group at all16:35
*** mitchj has quit IRC16:36
lauramoorei don't see a reason to have to have a limit either16:36
lazy_princeprobably it would.. as neutron will need the MAC ID for the port group..16:36
Sukhdevviveknarasimhan_: Neutron will be given a list of port-groups - if there are more items in the list, it assumes a port-group otherwise, it is a single port16:36
jrollSukhdev: so it should be [port.local_link_information for port in port_group.ports]16:36
viveknarasimhan_Sukhdev: This port and port-group terminology is maintained purely in Ironic side, right?  We see only neutron port with network information as many of them equal to side of list of local_link_information16:36
Sukhdevjroll: yup - something like that16:37
lauramoorei agree with jroll suggestion16:37
amotokiI am confused with the terminology...16:37
viveknarasimhan_Sukhdev:  Ok, the list size of local_link_information16:37
Sukhdevviveknarasimhan_: correct16:37
viveknarasimhan_determines for neutron if its a port-group or just a port16:37
viveknarasimhan_Sukhdev: Ok clear!16:37
jrollSukhdev: perhaps the wording of your proposal is confusing me, then, I don't understand "list of port groups"16:37
jrollok, I see16:37
jrolldoes neutron care if it's a port group vs a port? (i.e. are there special things configured for a LAG on the switch)16:38
rkukuraSukhdev: Can you clarify whether “port-group” is a list of neutron ports or a list of switch ports?16:38
Sukhdevjroll: if we are in agreement on the concept, I will work with Bertie lauramoore to get the terminology all cleared up16:38
Sukhdevrkukura: one neutron port maps to  one port-group16:38
jrollrkukura: list of ironic ports, which correspond 1:1 with physical nics / switch ports16:38
*** xingchao has quit IRC16:39
viveknarasimhan_rkukura:  a port-group is a list of switch ports not Neutron ports16:39
pshigerkukura: I can't see some characters16:39
viveknarasimhan_rkukura:  It is a LAG of which all switch ports will belong to the same network and so same segment16:39
SukhdevWe are running out of time - lets start summarizing things16:39
rkukurathanks16:40
SukhdevSo, I assuming, we are in general good with line 114 comments -16:40
*** sarob has joined #openstack-meeting-416:40
Sukhdevlets quickly talk about line 185 comments - this is API modification16:40
viveknarasimhan_Sukhdev: +1 from me on port-group terminology for LAG ports16:40
SukhdevI threw it out there as straw man proposal for API modification -16:41
Sukhdevviveknarasimhan_: thanks16:41
jrollSukhdev: seems mostly good to me... API impact should be fairly easy, add keys to the json body for create/update16:41
Sukhdevjroll: correct16:41
jrollSukhdev: I don't think there's much to debate there, we just need to list what's changing16:41
jrollseems like more of a "need time to do this" rather than "let's decide what this looks like"16:42
viveknarasimhan_Have a query on Sukhdev comment L 18516:42
lauramoorewe should have this in the next patch in the next day or two16:42
Sukhdevjroll: correct - but, we need closures so that implementation can begin while the spec is being cleaned up16:42
SukhdevNow on to my question - who would like to jump in to implement this?16:42
*** fallenpegasus has joined #openstack-meeting-416:43
Sukhdevyushiro, lazy_prince - any one of you want to take a crack at it?16:43
jrollSukhdev: it's just a rest api. I think people can figure it out while the spec gets tidied up :)16:43
*** belmoreira has joined #openstack-meeting-416:44
lazy_princei could take a look at the rest api..16:44
lauramooreSukhdev, i'm also interested in giving this a go16:44
Sukhdevjroll: that is my point - so that we can start to move forward with API changes16:44
viveknarasimhan_Well, I guess Sukhdev requests about Ironic side REST API feeding information16:44
viveknarasimhan_Sukhdev: can  you please let us know if am i right ?16:44
SukhdevCool - we have two people - can lauramoore and lazy_prince work out on this one16:45
*** bnemec has quit IRC16:45
Sukhdev#action: lauramoore and lazy_prince to come up with a patch for API modification16:45
jrollSukhdev: sure, I just don't think there's much to debate about a rest api. it's a json representation of the object. just update it to add the new fields16:45
jrollSukhdev: though we need to add it to the spec16:45
Sukhdevlazy_prince, lauramoore : I gave you action to work on a patch16:45
lazy_princecool..16:45
lauramooresure16:45
Sukhdevjroll: +116:46
Sukhdev#topic: the second spec16:46
*** openstack changes topic to ": the second spec (Meeting topic: ironic_neutron)"16:46
lauramoorebut i will aim to update the spec first16:46
jrollthe api changes need to be based on top of the db changes, fwiw, or else they won't work at all :P16:46
*** bnemec has joined #openstack-meeting-416:46
SukhdevNow lets dive into the next spec -16:46
lazy_princewe only have 14 minutes..16:46
viveknarasimhan_Sukhdev: Neutron side changes in ML2 plugin, do you foresee any effects there , based on the bind_requested flag?16:46
Sukhdevjroll: correct - I am assuming lauramoore and lazy_prince will figure it out - and shout for help, if needed, we are here every week to help/address issues16:47
Sukhdevviveknarasimhan_: not really -16:47
jrollyep16:47
viveknarasimhan_Sukhdev: Ok16:47
jroll#link https://review.openstack.org/#/c/187829/1/specs/liberty/network-provider.rst16:47
Sukhdevlazy_prince: thanks for reminder - that is why I am rushing through :-)16:47
jrollare there any major concerns in here we must hash out during the meeting?16:47
SukhdevI see the second spec is in a good shape - I had only one critical issue with it16:48
* Sukhdev - looking for my comment16:48
rkukuraI’m a bit concerned about the bind_requested flag, but need to read the spec more closely. Note that ML2 already has a way to control whether binding is requested - setting the binding:host_id attributes. Any chance ironic could simply set binding:host_id to empty when it doesn’t want the port bound?16:49
Sukhdevjroll: my comment on line 18516:49
jrollrkukura: AIUI that will set the port to "binding failed", which isn't really great from an ops perspective16:49
jrollSukhdev: ok, there's two reasons for this16:49
jroll1) I'd like this to be a pluggable layer such that someone could write a plugin for a network provider that is not neutron, if they wish16:50
rkukurajroll: Setting binding:host_id to empry should result in binding:vif_type being “unbound”16:50
Sukhdevrkukura: yes, that can be used - we thought there is no reason to overload it16:50
rkukuraSukhdev: I wouldn’t consider this to be overloading it, since that’s already what it does.16:50
jroll2) see Om Kumar's comment, I agree here. though maybe per-port would be better. either way we need the option, whether it's a db field or a config option16:50
viveknarasimhan_Sukhdev: agree with rkukura, to reuse host_id field16:51
lazy_princehmm.. That Om kumar is me.. :)16:51
jrollcan we keep this to one topic please?'16:51
lazy_princewanted to check of that comment makes sense..16:51
jrolllazy_prince: TIL! :)16:51
Sukhdevrkukura: perhaps then we can use it - this is a minor modification - I will work with you offline on this and get it incorporated - if that makes sense16:51
viveknarasimhan_Sukhdev: in lieu of adding a new field bind_requested16:51
jrolllazy_prince: I like the idea behind per-port config for that16:51
Sukhdevjroll: sorry16:52
Sukhdevjroll: so, I see the following issue - Perhaps it is my thinking which is skewed here  - bear with me for a sec16:52
jrollSukhdev: let me put it this way, there are people using ironic without neutron today.16:53
jrollSukhdev: and those folks wish to continue to do so.16:53
jrollwe don't want to force neutron (or any openstack services) on ironic users16:53
Sukhdevin order for ironic to connect a port to the network, neutron needs to know about this network - i.e. somebody needs to do neutron net-create before it can be used16:53
lazy_princeIronic can work as a standalone app too16:53
jroll^16:54
pshige :)16:54
jrollironic has a clear goal of being useful without any of the rest of openstack16:54
Sukhdevand, when a network is created, that is when a VLAN is associated with the network - which will be used to plumb the ports16:54
Sukhdevso, in my mind that creates a chicken-n-egg problem16:54
lazy_princeit could also happen that some drivers may want to do deployment without changing the network.. in which case this pluggable model helps..16:55
Sukhdevjroll, lazy_prince : so I see your use case - looks like we have two use cases to address then16:55
amotokiwhat is assumed when ironic is in a standalone mode? what network model is expected?16:55
jrollSukhdev: it's not *my* use case, it's an explicit goal of the ironic project16:55
jrollamotoki: flat16:55
amotokiflat network?16:55
jrollstatic dhcp etc16:55
amotokisounds reasonable16:56
jrollSukhdev: what's the problem with neutron being optional?16:56
*** killer_prince has joined #openstack-meeting-416:56
Sukhdevjroll: there is no problem - however, when we want to use neutron for plumbing, we need to provide it the information it needs to plumb things correctly16:57
killer_princefoo now, its flat.. but it does not have to be flat always..16:57
killer_princes/foo/for/16:57
*** markvoelker has joined #openstack-meeting-416:57
jrollSukhdev: right, so we make a pluggable layer with the right methods. the other option is 'none' or something, which will just ignore those calls16:57
Sukhdevjroll: OK now we are on to something16:58
killer_princemore precisely, we would like to controll it from ironic..16:58
jrollSukhdev: lines 39-48 or so16:58
Sukhdevjroll: but, I am interested in covering the case when neutron is in play - we want to make sure we have things in correct order so that it will work16:58
pshigelots of princes :)16:58
Sukhdevpshige, we need kings :-)16:59
killer_prince1min left..16:59
jrollSukhdev: sure, but this spec should also cover the pluggability, from an ironic perspective16:59
*** marutikamat has quit IRC16:59
Sukhdevjroll: I was not aware of the stand alone use case - let me go back and re-review in this light16:59
jrollSukhdev: it also means we need to think about the "uses neutron but not nova" case, which may be painful17:00
Sukhdevmoreover, we are out of time - lets add comments on the spec and take it from there - jroll I will catch you on ironic irc for questions17:00
*** lazy_prince has quit IRC17:00
jrollI guess we're out of time now... I'm in ironic and neutron channels if anyone wants to continue :)17:00
pshigethanks!17:01
SukhdevOK folks thanks for attending - this was a very productive discussion17:01
*** lucasagomes is now known as lucas-dinner17:01
Sukhdevthanks and bye17:01
Sukhdev#endmeeting17:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:01
openstackMeeting ended Mon Jun  8 17:01:11 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
yushiroall, sorry for slow reply...17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic_neutron/2015/ironic_neutron.2015-06-08-16.02.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic_neutron/2015/ironic_neutron.2015-06-08-16.02.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic_neutron/2015/ironic_neutron.2015-06-08-16.02.log.html17:01
*** viveknarasimhan_ has left #openstack-meeting-417:01
SukhdevHello L2 GW folks are you here?17:01
SukhdevIt is the time for L2 Gateway meeting17:02
*** yushiro has quit IRC17:02
amotokiit's too late to me. I need to follow. night17:02
Sukhdevarmax: are you here?17:02
Sukhdevamotoki: have a good night17:02
*** markvoelker has quit IRC17:02
*** marutikamat has joined #openstack-meeting-417:03
SukhdevStill waiting for L2 Gateway folks to show up17:03
armaxSukhdev: yes17:03
*** naohirot has quit IRC17:03
marutikamatHi Sukhdev, armax17:03
*** amotoki has left #openstack-meeting-417:04
armaxhi marutikamat17:04
Sukhdev#startmeeting networking_l2gw17:04
openstackMeeting started Mon Jun  8 17:04:29 2015 UTC and is due to finish in 60 minutes.  The chair is Sukhdev. Information about MeetBot at http://wiki.debian.org/MeetBot.17:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:04
*** openstack changes topic to " (Meeting topic: networking_l2gw)"17:04
openstackThe meeting name has been set to 'networking_l2gw'17:04
Sukhdev#topic: Agenda17:04
*** openstack changes topic to ": Agenda (Meeting topic: networking_l2gw)"17:04
Sukhdev#link: https://wiki.openstack.org/wiki/Meetings/L2Gateway17:04
Sukhdevsorry folks jumping from one meeting to another17:05
*** daneyon has joined #openstack-meeting-417:05
Sukhdevarmax marutikamat : did you have a chance to look at the agenda?17:05
armaxyes17:05
marutikamatYes I did17:06
SukhdevAre we good with it - or want to cover anything else?17:06
Sukhdev#topic: Announcements17:06
*** openstack changes topic to ": Announcements (Meeting topic: networking_l2gw)"17:06
marutikamatI will add something in the end17:06
Sukhdevmarutikamat: cool17:06
*** daneyon_ has quit IRC17:07
SukhdevThe presentation at summit went very well - I got lots of queries -17:07
SukhdevI am sure you got many as well17:07
marutikamatYes17:07
*** ivar-lazzaro has joined #openstack-meeting-417:07
Sukhdev#link: https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/bringing-provider-networks-into-openstack-using-l2-gateway17:07
*** dims has joined #openstack-meeting-417:07
SukhdevI was hoping that we will have many additional people joining us today17:07
Sukhdevanybody in this meeting who has not introduced themselves yet? Please do so…now...17:08
*** lucas-dinner has left #openstack-meeting-417:08
Sukhdev#topic: L2 GW Wiki updated17:08
*** openstack changes topic to ": L2 GW Wiki updated (Meeting topic: networking_l2gw)"17:08
SukhdevI took some time to update the wiki yesterday17:09
Sukhdev#link: https://wiki.openstack.org/wiki/Neutron/L2-GW17:09
SukhdevPlease have a look and feel free to update as needed - I also added links to the demos17:10
*** dims_ has quit IRC17:10
Sukhdev#topic: Requested features in Liberty17:10
*** openstack changes topic to ": Requested features in Liberty (Meeting topic: networking_l2gw)"17:10
marutikamatThanks Sukhdev17:10
armaxthanks Sukhdev, it looks good17:10
*** bradjones has quit IRC17:10
SukhdevI have listed one new feture17:10
SukhdevOVSDB server connection initiation -17:11
*** bradjones has joined #openstack-meeting-417:11
*** bradjones has quit IRC17:11
*** bradjones has joined #openstack-meeting-417:11
SukhdevI briefly chatted with you about it in Vancouver17:11
armaxSukhdev: I wonder if we should have a ‘roadmap’ section that shows what we do/did each release17:11
SukhdevWe need ability to be able to initiate connection from either side17:11
Sukhdevarmax: excellent idea17:12
marutikamat+1 with armax17:12
Sukhdevarmax: you want to add, or you want me to do the honors?17:12
Sukhdevmarutikamat: that goes for you too - I did not mean to exclude you17:13
*** rkukura has left #openstack-meeting-417:13
marutikamatI got the idea Sukhdev what you are asking. However, we will need a BP for this.17:13
armaxSukhdev: I can sketch something out?17:13
Sukhdevarmax: cool thanks - let me know if you need any help from me17:13
armaxmarutikamat: either a bp or a bug fix17:13
armaxmarutikamat: I mean bug report17:13
SukhdevI would think a bug should be sufficient - unless you want to go through the hassle of BP17:14
marutikamatPer the original spec, all the connections are opened by the gw agents. But in this  change, the connections will be opened by the OVSDB server itself.17:14
SukhdevI could open a bug, if you like17:14
*** lauramoore has quit IRC17:14
marutikamatok17:15
Sukhdevmarutikamat: OK - as in OK to open a bug? :-)17:15
marutikamatAre we giving an option to the use in ini file?17:16
marutikamats/use/user17:16
Sukhdevmarutikamat: yes, it will better - but, I am OK either way17:16
marutikamatplease file a bug17:16
Sukhdevmarutikamat: will do17:16
marutikamatok, we will figure out after investigation17:17
Sukhdevarmax marutikamat : any other feature you are considering for Liberty?17:17
*** killer_prince has quit IRC17:17
armaxWe’ve been saying we wanted a softweare l2gw17:17
armaxbut no-one is stepping up and volunteer17:18
armaxthey all want the cake but not pay for it :)17:18
Sukhdevarmax: correct :-)17:18
marutikamatYes. Just to inform you, myself and selva have been pulled out and put into some other projects. I was also thinking of support for service node and supporting l2gw through ODL17:18
Sukhdevarmax: I am a bit disappointed - I was hoping to see lot more new people here asking for all kinds of features17:18
marutikamatarmax i will send out a separate e-mail on the l2gw-ODL integration17:19
armaxmarutikamat: ok, let’s sync up offline17:19
armaxSukhdev: perhaps we need more advertising, during the neutron irc meeting?17:19
Sukhdevarmax: I did few times in the past - I'll put it on next week's meeting17:20
marutikamatnsx supports service node for unknown traffic. we should also support it.17:20
Sukhdevmarutikamat: you mean punt all BUM traffic to service node?17:21
marutikamatone more item s DVR with l2gw17:21
armaxwe should start building a backlog of items, via bug list and whatnot17:22
marutikamatyes Sukhdev17:22
Sukhdevarmax: Actually, we can list them on the wiki - when you list roadmap, perhaps we can add a section for future (long term) items -17:22
Sukhdevarmax: that may generate interest among others17:23
armaxSukhdev: I was thinking that the roadmap should capture big ticket items17:23
armaxand duplicating the list is a bit of a pain to keep in sync17:23
*** paramite has quit IRC17:23
Sukhdevarmax: we can create a bug and put the pointer under roadmap - that will keep things easy17:23
Sukhdevmarutikamat: can you open bugs for each of the items you mentioned?17:24
marutikamatok sure Sukhdev.17:24
marutikamatplease put action item on me17:24
armaxSukhdev: ok, let me see what we put together17:24
marutikamatIs Isaku there in the meeting?17:25
Sukhdev#action: marutikamat to create bugs for each of the new feature enhancements for L2 Gateway17:25
Sukhdevmarutikamat: I do not see him here17:25
marutikamatHe was keen in software l2gw.17:25
Sukhdevyes, he expressed interest, but, never came forward with anything concrete17:26
*** KunalGandhi has joined #openstack-meeting-417:26
Sukhdev#action: Sukhdev to open a bug for OVSDB connection initiation from OVSDB server17:27
Sukhdev#topic: Bugs17:27
*** openstack changes topic to ": Bugs (Meeting topic: networking_l2gw)"17:27
Sukhdevmarutikamat: I had discussed with you about the flood list issue17:27
marutikamatSukhdev, people are facing problems while backporting the fixes17:27
Sukhdevmarutikamat: what is the issue?17:28
Sukhdevarmax: is expert in this kinds of issues - I usually bug him when I get stuck :-):-)17:28
marutikamatOur test enginners (Ashish and Alok) are able to ping from bare metal server to the VM first.17:28
Sukhdevbut, I can help17:28
marutikamatvikas sent you an email on that. the branch shows as master even if he is trying to commit on kilo/stable.17:29
Sukhdevmarutikamat: after the first ping from VM or adding arp entry solves it17:29
marutikamatthey do not ping from VM first. The first ping itself from BM to VM works for them.17:29
armaxmarutikamat: are you saying that this is a regression?17:30
armaxmarutikamat: or in other works did the test case ever pass?17:30
marutikamatI was expecting their email reply to you but they missed it out today,17:30
Sukhdevmarutikamat: the best way to do is to go on the review board - open the patch which merged in master - and click on a tab called cherry pick - click on it and rest is easy17:30
marutikamatI will check with them again tomorrow.17:30
armaxif so, a good tool to use would be git bisect17:30
*** shivharis has quit IRC17:31
*** shivharis has joined #openstack-meeting-417:31
marutikamatthanks to both of you for the suggestion17:31
Sukhdevmarutikamat: I think the best way to go about is to dump the OVSDB contents and paste it - I sent you the paste from my side17:31
armaxmarutikamat: that’s a handy and quick tutorial http://webchick.net/node/9917:31
marutikamatSukhdev: I will request Alok/Ashish to get in touch with you for the ping problem17:32
Sukhdevmarutikamat: I see that HS VTEP publishes the flood list and SW VTEP does not17:32
armaxmarutikamat: basically ‘bisect’ will help you identify what commit broke the feature17:32
Sukhdevmarutikamat: cool -17:32
armaxand then it’s easier to understand what’s going, that assumed that it is a regression17:32
marutikamatarmax: thanks17:32
Sukhdevarmax: thanks for sharing this tool - I did not know about it17:33
armaxSukhdev: sure thing17:34
SukhdevAs to the bugs - I approved few17:34
SukhdevI will review more and approve them this week17:34
marutikamatthanks Sukhdev17:34
Sukhdevwe are looking good from the bugs point of view17:35
Sukhdevmarutikamat: I have exhausted my agenda items17:35
Sukhdevyou mentioned you wanted to bring something ?17:35
Sukhdev#topic OpenDiscussion17:35
*** openstack changes topic to "OpenDiscussion (Meeting topic: networking_l2gw)"17:35
SukhdevLets hear it17:35
marutikamatI already mentioned above. Additional backlog items17:36
SukhdevOh I see - cool17:36
marutikamatI will submit bugs for those17:36
Sukhdevgood17:36
Sukhdevanything else?17:36
marutikamatnothing from me17:37
SukhdevLooks like we are done -17:37
Sukhdevthanks folks17:37
marutikamatthanks both of you17:37
Sukhdev#endmeeting17:38
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:38
openstackMeeting ended Mon Jun  8 17:38:02 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_l2gw/2015/networking_l2gw.2015-06-08-17.04.html17:38
armaxSukhdev: I’ll add a roadmap shortly, check it out in a bit17:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_l2gw/2015/networking_l2gw.2015-06-08-17.04.txt17:38
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_l2gw/2015/networking_l2gw.2015-06-08-17.04.log.html17:38
*** nlahouti has left #openstack-meeting-417:38
*** shivharis has quit IRC17:38
Sukhdevarmax: OK17:38
*** shivharis has joined #openstack-meeting-417:38
*** zehicle_IRL has joined #openstack-meeting-417:39
*** Sukhdev has quit IRC17:39
*** xingchao has joined #openstack-meeting-417:39
*** Sukhdev has joined #openstack-meeting-417:40
*** marutikamat has quit IRC17:41
*** KunalGandhi has quit IRC17:44
*** xingchao has quit IRC17:44
*** daneyon_ has joined #openstack-meeting-417:45
*** daneyon has quit IRC17:48
*** bharath has joined #openstack-meeting-417:48
*** aswadr has quit IRC17:51
*** rods1 has joined #openstack-meeting-417:52
*** KunalGandhi has joined #openstack-meeting-417:56
*** kenhui has joined #openstack-meeting-418:01
*** sdake_ has joined #openstack-meeting-418:02
*** sdake has quit IRC18:02
*** sdake has joined #openstack-meeting-418:02
*** banix has quit IRC18:03
*** sdake_ has quit IRC18:06
*** shivharis has quit IRC18:08
*** sbalukoff has joined #openstack-meeting-418:12
*** jwagner is now known as jwagner_lunch18:12
*** wojdev has joined #openstack-meeting-418:19
*** krotscheck is now known as krotscheck_confe18:21
*** krotscheck_confe is now known as krotsch_at_con18:21
*** wanyen has quit IRC18:23
*** s3wong has joined #openstack-meeting-418:26
*** daneyon_ has quit IRC18:26
*** wojdev has quit IRC18:30
*** banix has joined #openstack-meeting-418:39
*** Sukhdev has quit IRC18:41
*** kenhui has quit IRC18:44
*** zz_zz_zz_zz_ja is now known as ja18:45
*** krotsch_at_con is now known as krotsck_at_con18:46
*** markvoelker has joined #openstack-meeting-418:46
*** Swami has quit IRC18:50
*** ivar-lazzaro has quit IRC18:51
*** markvoelker has quit IRC18:52
*** marcusvrn has quit IRC18:52
*** Rockyg has joined #openstack-meeting-418:58
*** bharath has quit IRC19:07
*** fallenpegasus has quit IRC19:07
*** yfried has quit IRC19:10
*** yfried has joined #openstack-meeting-419:10
*** jckasper has joined #openstack-meeting-419:11
*** tony_v has quit IRC19:12
*** Kiall_ has joined #openstack-meeting-419:13
*** Kiall has quit IRC19:15
*** igordcard has joined #openstack-meeting-419:15
*** ja is now known as zz_ja19:21
*** mitchj has joined #openstack-meeting-419:30
*** wojdev has joined #openstack-meeting-419:31
*** ivar-lazzaro has joined #openstack-meeting-419:31
*** jwagner_lunch is now known as jwagner19:33
*** bharath has joined #openstack-meeting-419:34
*** wojdev has quit IRC19:44
*** Nisha has quit IRC19:44
*** wojdev has joined #openstack-meeting-419:56
*** singleth_ has joined #openstack-meeting-419:59
*** banix has quit IRC20:00
*** ivar-laz_ has joined #openstack-meeting-420:01
*** singlethink has quit IRC20:02
*** GB21 has quit IRC20:02
*** ivar-lazzaro has quit IRC20:04
*** wojdev has quit IRC20:08
*** dannywilson has joined #openstack-meeting-420:19
*** ivar-laz_ has quit IRC20:20
*** fallenpegasus has joined #openstack-meeting-420:21
*** ivar-lazzaro has joined #openstack-meeting-420:21
*** eghobo has quit IRC20:22
*** wojdev has joined #openstack-meeting-420:22
*** Rockyg has quit IRC20:29
*** IlyaG has quit IRC20:29
*** ajmiller has joined #openstack-meeting-420:31
*** chuckC_ has joined #openstack-meeting-420:34
*** markvoelker has joined #openstack-meeting-420:35
*** wojdev has quit IRC20:39
*** dannywilson has quit IRC20:39
*** markvoelker has quit IRC20:40
*** wojdev has joined #openstack-meeting-420:40
*** Swami has joined #openstack-meeting-420:41
*** wojdev has quit IRC20:41
*** banix has joined #openstack-meeting-420:48
*** Sukhdev has joined #openstack-meeting-420:50
*** IlyaG has joined #openstack-meeting-420:51
*** belmoreira has quit IRC20:56
*** wojdev has joined #openstack-meeting-420:58
*** jckasper has quit IRC21:07
*** jwagner is now known as jwagner_away21:19
*** sdake_ has joined #openstack-meeting-421:19
*** sdake has quit IRC21:23
*** klamath has quit IRC21:31
*** KunalGandhi has quit IRC21:32
*** KunalGandhi has joined #openstack-meeting-421:32
*** zehicle_IRL has quit IRC21:38
*** fallenpegasus has quit IRC21:38
*** EmilienM is now known as EmilienM|afk21:41
*** rods1 has quit IRC21:42
*** VW has quit IRC21:46
*** singleth_ has quit IRC21:54
*** krotsck_at_con is now known as krotscheck22:08
*** VW has joined #openstack-meeting-422:16
*** galstrom is now known as galstrom_zzz22:20
*** markvoelker has joined #openstack-meeting-422:21
*** KunalGandhi has quit IRC22:21
*** markvoelker has quit IRC22:26
*** mitchj has quit IRC22:26
*** VW_ has joined #openstack-meeting-422:38
*** VW has quit IRC22:38
*** Sukhdev has quit IRC22:50
*** VW_ has quit IRC23:00
*** VW has joined #openstack-meeting-423:01
*** saneax has joined #openstack-meeting-423:05
*** VW has quit IRC23:06
*** daneyon has joined #openstack-meeting-423:10
*** daneyon_ has joined #openstack-meeting-423:11
*** daneyon has quit IRC23:15
*** IlyaG has quit IRC23:17
*** Sukhdev has joined #openstack-meeting-423:19
*** EmilienM|afk is now known as EmilienM23:20
*** aventerav has quit IRC23:37
*** dannywilson has joined #openstack-meeting-423:40
*** dannywilson has quit IRC23:44
*** wojdev has quit IRC23:45
*** ajmiller has quit IRC23:52
*** tony_v has joined #openstack-meeting-423:53
*** xingchao has joined #openstack-meeting-423:54
*** carl_baldwin has quit IRC23:55
*** tonyv has joined #openstack-meeting-423:57

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