Tuesday, 2015-11-17

*** baoli has joined #openstack-meeting-400:00
*** rbak_ has quit IRC00:01
*** sigmavirus24 is now known as sigmavirus24_awa00:03
*** baoli has quit IRC00:05
*** baoli has joined #openstack-meeting-400:06
*** itisha has quit IRC00:11
*** baoli has quit IRC00:12
*** morgabra_ is now known as morgabra00:15
*** morgabra has quit IRC00:15
*** morgabra has joined #openstack-meeting-400:15
*** daddyjoseph97 has quit IRC00:20
*** yamamoto has joined #openstack-meeting-400:22
*** yamamoto has quit IRC00:22
*** bogdando has quit IRC00:29
*** bogdando has joined #openstack-meeting-400:35
*** limao has joined #openstack-meeting-400:37
*** jckasper has joined #openstack-meeting-400:38
*** jckasper has quit IRC00:40
*** IlyaG_ has joined #openstack-meeting-400:43
*** jckasper has joined #openstack-meeting-400:45
*** jckasper has quit IRC00:46
*** IlyaG has quit IRC00:46
*** IlyaG_ has quit IRC00:50
*** Swami has quit IRC01:01
*** baoli has joined #openstack-meeting-401:03
*** stanchan has quit IRC01:08
*** salv-orlando has quit IRC01:12
*** bobh has joined #openstack-meeting-401:12
*** stanchan_ has quit IRC01:16
*** bobh has quit IRC01:17
*** SimonChung has quit IRC01:35
*** markvoelker has joined #openstack-meeting-401:37
*** baohua has joined #openstack-meeting-401:39
*** shimura_ken has joined #openstack-meeting-401:42
*** bogdando has quit IRC01:43
*** bogdando has joined #openstack-meeting-401:43
*** Sukhdev_ has quit IRC01:47
*** bogdando has quit IRC01:49
*** bobh has joined #openstack-meeting-401:55
*** sdake has joined #openstack-meeting-401:55
*** fitoduarte has quit IRC01:58
*** bpokorny_ has joined #openstack-meeting-402:02
*** bogdando has joined #openstack-meeting-402:04
*** prashantD has quit IRC02:04
*** jmccrory has joined #openstack-meeting-402:05
*** fawadkhaliq has joined #openstack-meeting-402:05
*** bpokorny has quit IRC02:06
*** bpokorny_ has quit IRC02:07
*** baoli has quit IRC02:11
*** baoli has joined #openstack-meeting-402:11
*** nate_gone is now known as njohnston02:12
*** IlyaG has joined #openstack-meeting-402:15
*** shimura_ken has quit IRC02:16
*** sdake has quit IRC02:16
*** sdake has joined #openstack-meeting-402:17
*** banix has joined #openstack-meeting-402:22
*** woodard has joined #openstack-meeting-402:22
*** armax has joined #openstack-meeting-402:24
*** woodard has quit IRC02:26
*** sdake has quit IRC02:32
*** baoli has quit IRC02:45
*** baoli has joined #openstack-meeting-402:45
*** vikasc_ has joined #openstack-meeting-402:47
*** vikasc_ has quit IRC02:49
*** baoli has quit IRC02:52
*** vikasc has joined #openstack-meeting-402:55
*** tfukushima has joined #openstack-meeting-402:55
*** baoli has joined #openstack-meeting-402:58
*** sdake has joined #openstack-meeting-403:00
banix#startmeeting kuryr03:00
openstackMeeting started Tue Nov 17 03:00:43 2015 UTC and is due to finish in 60 minutes.  The chair is banix. Information about MeetBot at http://wiki.debian.org/MeetBot.03:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.03:00
*** openstack changes topic to " (Meeting topic: kuryr)"03:00
openstackThe meeting name has been set to 'kuryr'03:00
banixWho is around for the kuryr meeting at this alternate meeting time? :)03:01
vikascHi everybody03:01
tfukushimao/03:01
vikasco/03:01
fawadkhaliqhello everyone!03:01
*** s3wong has quit IRC03:01
banix#link https://wiki.openstack.org/wiki/Meetings/Kuryr#Agenda03:02
vikascfawadkhaliq: Hi fawad03:02
banixHi vikasc tfukushima fawadkhaliq03:02
banixThis may be a short meeting but that’s what we say everytime03:02
vikascbanix: :)03:02
fawadkhaliqlol03:03
banix#topic Announcements03:04
*** openstack changes topic to "Announcements (Meeting topic: kuryr)"03:04
banixI updated the IRC meeting for the new time; It was incorrectly updated but that should get sorted out shortly:   https://review.openstack.org/#/c/245868/03:04
tfukushimaSo obviously this is the new starting time for the alternated schedule.03:04
banixtfukushima: yes indeed03:05
tfukushimabanix: It's already merged.03:05
fawadkhaliqbanix: great. btw, I was wondering if we should also add this information on Kuryr Wiki as well like other projects?03:05
banixwe will probably need to send another email the dev list in case there is any doubts03:05
banixfawadkhaliq: yes indeed; will do03:05
fawadkhaliqbanix: thanks!03:05
banixAnyone else has any announcements?03:06
*** bapalm has quit IRC03:06
tfukushimaNothing from my side.03:06
vikascvikasc: not from my side too03:06
banix#topic Action Items03:06
*** openstack changes topic to "Action Items (Meeting topic: kuryr)"03:06
*** harshs has quit IRC03:06
banixWe hade a few action items from last week as listed on the agenda; let’s go through them quickly03:07
banix1. gsagie to check conntrack for security groups in the mitaka cycle03:07
tfukushimaI think it's too early for gsagie and too late for apuimedo.03:07
banixGal is probably fast asleep :)03:07
vikasclol03:08
banixbut I think we know for sure the use of native OVS conntrack has not been implemented yet; Do we know if the plan is to have it included in Mitaka?03:08
fawadkhaliqbanix: i think it is03:08
fawadkhaliqlet me share a link03:08
fawadkhaliq#link http://openvswitch.org/pipermail/dev/2015-November/062228.html03:09
fawadkhaliqNot in Neutron ofcourse03:09
tfukushima I'm still catching up...03:10
banixfawadkhaliq: thanks for the link; yes the question is when that will be available through the Neutron OVS driver03:10
vikascvikasc: AFAIK currently ovs can lookup tcp flags only so based on that stateful conntrack can be implemented using this feature of ovs03:10
vikascfawadkhaliq: any idea03:11
banixThere was a blueprint and someone working on it a while back but since things had not merged on the OVS side, that work got stopped; Sooner or later that will be picked up again03:11
fawadkhaliqMakes sense. I am not aware of Mitaka plan on this. Didn't see any discussions on the summit either03:12
vikascbanix: seems it will take a bit of time03:12
vikascmay be someone from team can takeup this action to explore on this03:12
fawadkhaliqWith OVN being the priority for many folks, I am not sure who will spend time porting these to existing driver?03:12
banixRegardless, as we keep track of the conntrack, we will probably need to support Hubrid OVS plgu/unplug which leads us to the 2nd action item from last week03:13
banixfawadkhaliq: true03:13
banix2. banix to work with diga on the ovs binding (with the hybrid as follow up patches if necessary)03:13
fawadkhaliqagree with vikasc: perhaps we can take an action item and see if there is any plan. I can follow up with relevant folks. Please assign an action to me.03:13
vikascfawadkhaliq: great03:14
banixfawadkhaliq: thanks Fawad; since Gal has already taken the action don’t spend too much time tracking this03:14
fawadkhaliqbanix: sounds good03:14
banix#action fawadkhaliq to also check on the status of Neutron OVS driver use of OVS conntrack03:15
banixAnyone has been in touch with Diga?03:15
*** harshs has joined #openstack-meeting-403:16
*** salv-orlando has joined #openstack-meeting-403:16
tfukushimabanix: No. I haven't heard anything for more than a month. Have you?03:16
vikascnegative03:16
*** sdake has quit IRC03:16
banixI couldn’t find him on IRC and sent him an email. If we don’t hear back in a day or so I will add the plug/unplug piece for OVS03:16
vikascbanix: makes sense03:17
banix#action banix to get the plug/unplug for OVS ready for review03:17
tfukushimaOk, thanks.03:17
vikascthats an important missing piece03:17
vikascbanix: thanks03:17
*** jerryz has quit IRC03:17
banixvikasc: yes, sure. will get it in this week.03:18
banixmoving on to the next action item from last week:03:18
*** devananda has quit IRC03:18
banix3. apuimedo to review validation vikasc patches03:18
vikascthats done03:18
banixvikasc: Any patches left for review?03:19
vikasconly https://review.openstack.org/#/c/241134/03:19
fawadkhaliqvikasc: can you please share the links?03:19
fawadkhaliqoh its here03:19
vikascbut this is not a validation patch03:19
fawadkhaliqthanks03:19
tfukushimaLet's talk about it later.03:19
vikascsure03:19
vikascbanix: this is dhcp disable/enable one.03:19
banixvikasc: ok sounds good; will talk about the above later today03:20
vikascvthanks03:20
banix4. apuimedo to review the external network connectivity blueprint03:20
vikasci guess this is pending yet03:20
tfukushima#link the external network connectivity blueprint https://blueprints.launchpad.net/kuryr/+spec/external-network-connectivity03:21
banixtfukushima: thanks for the link03:21
banixvikasc: I have not looked at it yet; Others have any comments?03:21
vikascbanix: nope03:21
fawadkhaliqbanix: vikasc: I will review it and add my comments.03:22
vikascfawadkhaliq: thanks fawad03:22
banix#action All to reviewexternal connectivity blueprint  #link  https://blueprints.launchpad.net/kuryr/+spec/external-network-connectivity03:22
banixanything else on the Action Items from last week?03:23
banix#topic vif plug/unplug (binding)03:24
*** openstack changes topic to "vif plug/unplug (binding) (Meeting topic: kuryr)"03:24
vikascbanix: fyi..currently working on ipam implementation. will take one or two days more03:24
banixvikasc: will get to that topic shortly03:25
vikascbanix: ok03:25
banixJust wanted to mention that the os-vif repository has been created: #link  https://github.com/openstack/os-vif03:25
banixNo content in it yet but I believe this is something which we will hopefully use03:26
tfukushimaI'm not familiar with os-vif but it's a tiny component takes care of the vif binding decoupled from Neutron and Nova in my understanding.03:26
fawadkhaliqanyone aware of when the basic structure will be in place? then we can start filling in.03:26
fawadkhaliqtfukushima: thats correct. So the vif code moves out of Nova tree.03:26
banixtfukushima: my understanding is that it will do what Nova currently does for plug/unplug of different vif types03:27
banixand that’s what we do in our binding directory03:27
banixAs we work on adding support for OVS, etc, we should keep an eye on the os-vif progress and remain in sync wrt the api as much as possible03:28
vikascbanix: sure03:28
*** yamamoto has joined #openstack-meeting-403:28
banixregardless, we need to use the binding as we do right now until the os-vif is ready03:29
tfukushima#link the os-vif blueprint https://review.openstack.org/#/c/193668/03:29
fawadkhaliqbanix: +103:29
vikasctfukushima: thanks for the link Taku03:29
banixShall we move on to the next topic?03:30
tfukushimaYes. We can catch up with it but there's no implementation so far.03:30
banixtfukushima: yes, jay pipe has a poc kind of implementation under hit github: #link https://github.com/jaypipes/os_vif03:31
*** devananda has joined #openstack-meeting-403:31
*** jerryz has joined #openstack-meeting-403:32
banixso there has been some work already done but as you mention the repo is empty and it may take a while before it becomes consumable03:32
tfukushimaLet's move to the IPAM driver.03:33
banixGeneral discussion from the summit here: #link https://etherpad.openstack.org/p/mitaka-nova-os-vif-lib03:33
banix#topic IPAM driver03:33
*** openstack changes topic to "IPAM driver (Meeting topic: kuryr)"03:33
banixvikasc: please go ahead03:33
vikascbanix: sorry banix03:33
vikascneed to go offline03:33
vikascwill be back in couple of minutes03:33
vikascunavoidable03:33
banixvikasc: sure03:34
banixnp03:34
banix#undo03:34
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0xab0d650>03:34
banix#topic devstack integration03:34
*** openstack changes topic to "devstack integration (Meeting topic: kuryr)"03:34
fawadkhaliq#link gsagie added the DevStack plugin https://review.openstack.org/#/c/242838/03:35
banixI see Gal had uploaded his patch. Anything we need to discuss here?03:35
banixthanks for the link03:35
vikascbanix: i am back :)03:35
fawadkhaliqToni saw some errors, I will see if I can reproduce.03:35
tfukushimaAccording to apuimedo, he got stuck with it.03:35
tfukushimaI reviewed it and I guess KURYR_HOME is not set appropriately.03:36
banixyeah saw that. So let’s give it a try and see how far we go and give feedback03:36
vikascbanix: sure.. i will also try it03:36
tfukushimaapuimedo is in DockerCon EU and showing the demo of Kuryr BTW.03:37
banixtfukushima: cool03:37
vikasctfukushima: great news03:37
fawadkhaliqgood luck apuimedo!03:37
banixI wonder if libnetwork people will …. never mind :)03:37
fawadkhaliqbanix: lol03:37
banixyes sending good vives to Toni03:38
banix#topic IPAM driver03:38
*** openstack changes topic to "IPAM driver (Meeting topic: kuryr)"03:38
banixvikasc: please go ahead03:38
vikascI had a small discussion with tfukushima also and implmenattion is going on.03:38
vikascwill be submitting first patch shortly03:39
tfukushimaSo vikasc is working on the "null" IPAM driver, which basically does nothing but delegate the IPAM to Neutron.03:39
banixvikasc: is what is needed a null driver or ….03:40
vikasctfukushima: true03:40
banixok got it03:40
fawadkhaliqthanks tfukushima i was just going to ask this03:40
tfukushimaAnd I found --ip-range accidentally works with the current Kuryr implementation.03:40
vikasctfukushima:  lol03:40
vikasc"accedently"03:40
*** salv-orlando has quit IRC03:41
fawadkhaliqvikasc: is there a link where you have captured the proposed mapping or it trivial enough to not need one?03:41
vikascfawadkhaliq: its very trivial enough fawadkhaliq03:41
fawadkhaliqvikasc: cool03:41
tfukushimaSo here's the thing:03:41
tfukushima$ sudo docker network create -d kuryr foo --subnet 10.0.0.0/24 --gateway 10.0.0.1 --ip-range 10.0.0./2403:41
tfukushima--ip-range 10.0.0.0/2403:42
vikasctfukushima: that made life easy :)03:42
tfukushimaThis --ip-range passes the subnet CIDR to the default IPAM driver.03:42
fawadkhaliqright03:42
fawadkhaliqgot it. thanks tfukushima03:43
tfukushimaAnd the default IPAM driver takes it, allocate the IP addresses and give one from the range to /NetworkDriver.CreateEndpiont as Address or IPv6Address.03:43
vikasctfukushima: makes sense03:44
banix#action vikasc to have the IPAM driver ready soon03:44
tfukushimaKuryr already supports Address and IPv6Address in the request against  /NetworkDriver.CreateEndpiont and create  a new subnet if theres no one corresponding to the given Address and IPv6Address.03:44
*** IlyaG has quit IRC03:45
tfukushimaSo if we --ip-range is set appropriately, Kuryr takes care of things well.03:45
*** IlyaG has joined #openstack-meeting-403:45
tfukushimaBut in this case the default IPAM driver of Docker and the Neutron IPAM are coordinated appropriately.03:46
vikasctfukushima: thanks Taku for nice finding03:46
tfukushimaFor instance the DHCP port needs to be disabled.03:46
*** harshs has quit IRC03:46
banixtfukushima: so this is sounding a bit confusing now03:46
*** ivar-laz_ has joined #openstack-meeting-403:46
vikascbanix: now this is related to this patch https://review.openstack.org/#/c/241134/03:47
banixtfukushima: that is when the default IPAM driver is used, and it turns out libnetwork and Neutron use the same serial allocation of IPs03:47
banixis that correct?03:47
tfukushimaYes, because in the current codebase Kuryr allocates all IP addresses greedily.03:48
tfukushimaThat allocation is done by Neutron.03:49
*** ivar-lazzaro has quit IRC03:49
tfukushimaSo the IPAM drivers are out of sync, we are screwed.03:49
banixtfukushima: are you simply saying that the default driver works ok if we disable dhcp? or suggesting that is what we should use03:49
*** IlyaG has quit IRC03:49
tfukushimaThat's why I told it worked "accidentally" and the DHCP port needs to be disabled.03:49
vikasctfukushima: To be more precise, can we say ip allocation is done by docker default ipam and neutron has to honor that allocation03:50
banixexactly which means we should use our own driver (the null driver).03:50
fawadkhaliqvikasc: Neutron can only honor if you ask Neutron to use fixed IPs for each port, right?03:50
banixi meant exactly to taku’s comment03:50
vikascfawadkhaliq: yes03:51
vikascand neutron dont know that the ip neutron has used for the dhcp port can also be allocated by docker default ipam03:51
banixvikasc: sure and thats why we need our own driver. relying on the above won’t be reasonable03:52
vikascbanix: true03:52
fawadkhaliqvikasc: from what I understand, Neutron not knowing the IP for DHCP port, is a problem contained in the DHCP enable/disable area and that should fix it.03:52
vikascfawadkhaliq: yes03:52
tfukushimaYeah, ideally we should have our own IPAM driver which is synced with Neutron, or Neutron itself.03:53
fawadkhaliqjust to be sure, since I dont know the implementation, we are not relying on something like banix mentioned above. The two systems assumed to have same IP allocation mechanism, right? That might break.03:53
*** IlyaG has joined #openstack-meeting-403:53
banixhaving to independent IPAM modules is something we can and have to avoid03:54
banixtwo independent03:54
vikascbanix: thats what we will address by disabling dhcp03:54
vikascbanix: by two ipams you mean here default docker ipam and neutron dhcp?03:55
banixvikasc: I don’t think that’s good enough03:55
tfukushimaYes, but this little hack is useful until we implement the IPAM driver.03:55
banixvikasc:  yes, that case may be ok for just demonstration but not as a solution. Do we have an agreement here?03:55
fawadkhaliqbanix: +103:55
vikascbanix: +103:55
vikascwe have just 4 mins left03:56
banixtfukushima: ok i understand now :) so our solution will be having a null driver and delegating all IPAM activities to Neutron03:56
tfukushimaSo I'll keep working on creating the IPAM spec.03:56
fawadkhaliqfor the proper solution, we should consider drafting a blueprint perhaps?03:56
fawadkhaliqgreat tfukushima03:56
fawadkhaliqthanks03:56
banixnow I am confused again :)03:56
vikasctfukushima: thanks Taku03:56
banixisn’t vikas working on a solution already?03:57
fawadkhaliqbanix: perhaps they are working as a team ;)03:57
banixand by a solution I mean the proper solution that does not rely on two IPAMs being in sync03:58
vikascbanix: tfukushima spec will be more than just null ipam and he will cover neutrons pluggable ipam also in that. is that correct Taku?03:58
tfukushimaYes. I'm still figuring out and if it's not necessary, I'll move on to another task.03:59
banixok03:59
tfukushimaWe're running our time out.03:59
fawadkhaliqhm, Neutron pluggable IPAM in Kuryr when Neutron is the interface to Kuryr. Can't quite understand why would that be needed.03:59
banixand as the car talk brothers used to say, we managed to spoil another hour of your time :)04:00
vikasclol04:00
banixfawadkhaliq: agree04:00
banixthanks everybody04:00
vikascthanks everybody04:00
banix#endmeeting04:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"04:00
openstackMeeting ended Tue Nov 17 04:00:44 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2015/kuryr.2015-11-17-03.00.html04:00
fawadkhaliqthanks04:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2015/kuryr.2015-11-17-03.00.txt04:00
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2015/kuryr.2015-11-17-03.00.log.html04:00
fawadkhaliqbye!04:00
*** vikasc has quit IRC04:04
*** ivar-laz_ has quit IRC04:05
*** dims has quit IRC04:06
*** MarkAtwood has joined #openstack-meeting-404:11
*** tfukushima has quit IRC04:36
*** bobh has quit IRC04:40
*** IlyaG_ has joined #openstack-meeting-404:40
*** banix has quit IRC04:42
*** sdake has joined #openstack-meeting-404:42
*** IlyaG has quit IRC04:43
*** harshs has joined #openstack-meeting-404:46
*** SimonChung has joined #openstack-meeting-404:49
*** jwang__ has joined #openstack-meeting-404:50
*** SimonChung1 has joined #openstack-meeting-404:51
*** baigk1 has joined #openstack-meeting-404:53
*** salv-orlando has joined #openstack-meeting-404:53
*** SimonChung has quit IRC04:54
*** sdake has quit IRC04:55
*** _d34dh0r53_ has joined #openstack-meeting-404:57
*** cfarquhar_ has joined #openstack-meeting-404:58
*** Kiall_ has joined #openstack-meeting-404:58
*** sdake has joined #openstack-meeting-404:59
*** tfukushima has joined #openstack-meeting-404:59
*** baoli has quit IRC05:00
*** palendae has quit IRC05:00
*** sigmavirus24_awa has quit IRC05:00
*** SergeyLukjanov has quit IRC05:00
*** jwang_ has quit IRC05:00
*** dolphm has quit IRC05:00
*** serverascode has quit IRC05:00
*** flaper87 has quit IRC05:00
*** baigk has quit IRC05:00
*** cloudnull has quit IRC05:00
*** d34dh0r53 has quit IRC05:00
*** mgagne has quit IRC05:00
*** jroll has quit IRC05:00
*** sbadia has quit IRC05:00
*** KLuka__ has quit IRC05:00
*** kbyrne has quit IRC05:00
*** jpeeler has quit IRC05:00
*** cfarquhar has quit IRC05:00
*** notmyname has quit IRC05:00
*** Kiall has quit IRC05:00
*** jroll has joined #openstack-meeting-405:00
*** baigk1 is now known as baigk05:00
*** mgagne has joined #openstack-meeting-405:00
*** SergeyLukjanov has joined #openstack-meeting-405:00
*** dolphm has joined #openstack-meeting-405:01
*** flaper87 has joined #openstack-meeting-405:01
*** jpeeler has joined #openstack-meeting-405:01
*** sigmavirus24_awa has joined #openstack-meeting-405:01
*** KLuka__ has joined #openstack-meeting-405:01
*** kbyrne has joined #openstack-meeting-405:01
*** palendae has joined #openstack-meeting-405:01
*** jroll has quit IRC05:02
*** jroll has joined #openstack-meeting-405:02
*** jroll is now known as Guest8904005:02
*** sigmavirus24_awa has quit IRC05:02
*** sigmavirus24_awa has joined #openstack-meeting-405:02
*** sigmavirus24_awa is now known as Guest8755305:02
*** Guest86181 has joined #openstack-meeting-405:02
*** notmyname has joined #openstack-meeting-405:03
*** fitoduarte has joined #openstack-meeting-405:04
*** serverascode has joined #openstack-meeting-405:04
*** salv-orlando has quit IRC05:05
*** sbadia has joined #openstack-meeting-405:07
*** Guest86181 is now known as cloudkiller05:08
*** amotoki has joined #openstack-meeting-405:10
*** IlyaG_ has quit IRC05:13
*** tfukushima has quit IRC05:14
*** lazy_prince has joined #openstack-meeting-405:16
*** carl_baldwin has quit IRC05:17
*** ashtokolov has quit IRC05:18
*** GheRivero has quit IRC05:18
*** aglarendil has quit IRC05:18
*** masteinhauser_ has joined #openstack-meeting-405:18
*** tpeoples_away has quit IRC05:19
*** bnemec has joined #openstack-meeting-405:19
*** spredzy has quit IRC05:25
*** beekneemech has quit IRC05:25
*** erikmwilson has quit IRC05:25
*** sballe has quit IRC05:25
*** yhvh has quit IRC05:25
*** masteinhauser has quit IRC05:25
*** markmcclain has quit IRC05:25
*** spredzy_ has joined #openstack-meeting-405:25
*** erikmwilson has joined #openstack-meeting-405:25
*** yhvh has joined #openstack-meeting-405:26
*** masteinhauser_ is now known as masteinhauser05:26
*** masteinhauser is now known as Guest4832705:27
*** sdake has quit IRC05:27
*** amotoki has quit IRC05:27
*** amotoki has joined #openstack-meeting-405:28
*** tpeoples_away has joined #openstack-meeting-405:28
*** aglarendil has joined #openstack-meeting-405:28
*** sballe has joined #openstack-meeting-405:30
*** markmcclain has joined #openstack-meeting-405:31
*** GheRivero has joined #openstack-meeting-405:32
*** tfukushima has joined #openstack-meeting-405:32
*** sdake has joined #openstack-meeting-405:33
*** tfukushima has quit IRC05:35
*** ashtokolov has joined #openstack-meeting-405:35
*** carl_baldwin has joined #openstack-meeting-405:36
*** lakshmiS has joined #openstack-meeting-405:39
*** bobh has joined #openstack-meeting-405:41
*** bpokorny has joined #openstack-meeting-405:43
*** bobh has quit IRC05:45
*** jmccrory has quit IRC05:48
*** jmccrory has joined #openstack-meeting-405:51
*** baohua has quit IRC06:06
*** baohua has joined #openstack-meeting-406:08
*** bpokorny has quit IRC06:09
*** harshs has quit IRC06:11
*** galstrom_zzz is now known as galstrom06:13
*** zeih has joined #openstack-meeting-406:16
*** pbourke has quit IRC06:18
*** pbourke has joined #openstack-meeting-406:18
*** zeih has quit IRC06:20
*** jpekkari has joined #openstack-meeting-406:24
*** salv-orlando has joined #openstack-meeting-406:34
*** salv-orlando has quit IRC06:37
*** adduarte has joined #openstack-meeting-406:43
*** fitoduarte has quit IRC06:44
*** duartea has joined #openstack-meeting-406:45
*** adduarte has quit IRC06:49
*** angdraug has joined #openstack-meeting-406:53
*** jerryz has quit IRC06:55
*** MarkAtwood has quit IRC07:01
*** dhellmann has quit IRC07:01
*** dhellmann has joined #openstack-meeting-407:02
*** pkoniszewski has quit IRC07:04
*** tfukushima has joined #openstack-meeting-407:23
*** lakshmiS has quit IRC07:24
*** lakshmiS has joined #openstack-meeting-407:25
*** tfukushima has quit IRC07:26
*** sdake has quit IRC07:30
*** numans has joined #openstack-meeting-407:35
*** spredzy_ is now known as spredzy07:36
*** galstrom is now known as galstrom_zzz07:37
*** nkrinner has joined #openstack-meeting-407:37
*** sambetts has quit IRC07:40
*** bobh has joined #openstack-meeting-407:41
*** sambetts has joined #openstack-meeting-407:45
*** bobh has quit IRC07:46
*** qwebirc53761 has joined #openstack-meeting-407:51
*** qwebirc53761 has quit IRC07:51
*** alex_didenko has joined #openstack-meeting-407:54
*** irenab has quit IRC07:54
*** irenab has joined #openstack-meeting-407:54
*** mfedosin has joined #openstack-meeting-408:05
*** zeih has joined #openstack-meeting-408:13
*** matrohon has joined #openstack-meeting-408:15
*** lakshmiS_ has joined #openstack-meeting-408:26
*** lakshmiS has quit IRC08:30
*** tfukushima has joined #openstack-meeting-408:38
*** alex_didenko has quit IRC08:40
*** salv-orlando has joined #openstack-meeting-408:45
*** lakshmiS_ has quit IRC08:48
*** tfukushima has quit IRC08:52
*** mfedosin has quit IRC08:58
*** salv-orlando has quit IRC08:59
*** yamamoto has quit IRC09:12
*** salv-orlando has joined #openstack-meeting-409:15
*** salv-orlando has quit IRC09:15
*** salv-orlando has joined #openstack-meeting-409:15
*** salv-orlando has quit IRC09:20
*** salv-orlando has joined #openstack-meeting-409:20
*** ekarlso has quit IRC09:22
*** gb21_ has quit IRC09:33
*** ekarlso has joined #openstack-meeting-409:37
*** ekarlso has quit IRC09:38
*** ekarlso has joined #openstack-meeting-409:38
*** bobh has joined #openstack-meeting-409:43
*** baohua has quit IRC09:48
*** bobh has quit IRC09:48
*** belmoreira has joined #openstack-meeting-409:52
*** yamamoto has joined #openstack-meeting-409:52
*** ekarlso has quit IRC09:57
*** limao has quit IRC10:03
*** markvoelker has quit IRC10:05
*** subscope has joined #openstack-meeting-410:30
*** alex_didenko has joined #openstack-meeting-410:35
*** ekarlso has joined #openstack-meeting-410:36
*** ekarlso has quit IRC10:39
*** yamamoto has quit IRC10:49
*** subscope has quit IRC10:50
*** yamamoto has joined #openstack-meeting-410:56
*** baohua has joined #openstack-meeting-410:56
*** jpekkari has quit IRC11:03
*** markvoelker has joined #openstack-meeting-411:06
*** dims has joined #openstack-meeting-411:08
*** jpekkari has joined #openstack-meeting-411:09
*** markvoelker has quit IRC11:11
*** salv-orl_ has joined #openstack-meeting-411:15
*** salv-orlando has quit IRC11:17
*** dzamboni has joined #openstack-meeting-411:26
*** flaper87 has quit IRC11:27
*** flaper87 has joined #openstack-meeting-411:27
*** salv-orl_ has quit IRC11:31
*** salv-orlando has joined #openstack-meeting-411:32
*** bobh has joined #openstack-meeting-411:44
*** bobh has quit IRC11:49
*** amotoki has quit IRC11:49
*** lakshmiS has joined #openstack-meeting-411:49
*** lakshmiS has quit IRC11:54
*** tremble has joined #openstack-meeting-412:02
*** fawadkhaliq has quit IRC12:26
*** fawadkhaliq has joined #openstack-meeting-412:27
*** woodard has joined #openstack-meeting-412:29
*** woodard has quit IRC12:29
*** woodard has joined #openstack-meeting-412:30
*** fawadkhaliq has quit IRC12:31
*** pkoniszewski has joined #openstack-meeting-412:32
*** Guest89040 is now known as jroll12:36
*** markvoelker has joined #openstack-meeting-412:37
*** markvoelker has quit IRC12:42
*** jgjhgsonchn88523 has joined #openstack-meeting-412:44
*** pkoniszewski is now known as pkoniszewski_12:50
*** baoli has joined #openstack-meeting-412:52
*** jgjhgsonchn88523 has quit IRC13:00
*** jruano has joined #openstack-meeting-413:01
*** bobh has joined #openstack-meeting-413:06
*** bobh has quit IRC13:07
*** klamath has joined #openstack-meeting-413:10
*** nkrinner has quit IRC13:12
*** bobh has joined #openstack-meeting-413:15
*** nkrinner has joined #openstack-meeting-413:15
*** ff has joined #openstack-meeting-413:18
*** ff has quit IRC13:18
*** bobh has quit IRC13:19
*** limao has joined #openstack-meeting-413:21
*** cloudkiller is now known as cloudnull13:26
*** markvoelker has joined #openstack-meeting-413:27
*** amotoki has joined #openstack-meeting-413:34
*** jruano_ has joined #openstack-meeting-413:36
*** jruano has quit IRC13:37
*** zeih has quit IRC13:41
*** zeih_ has joined #openstack-meeting-413:41
*** jruano has joined #openstack-meeting-413:44
*** jruano_ has quit IRC13:47
*** jruano_ has joined #openstack-meeting-413:53
*** jruano has quit IRC13:55
*** jgjhgsonchn88523 has joined #openstack-meeting-413:57
*** jpekkari has quit IRC13:57
*** mclaren has joined #openstack-meeting-414:00
flaper87Courtesy Glance Drivers' meeting reminder: nikhil_k, flaper87, sigmavirus24, rosmaita, mclaren, dhellmann, jokke_14:01
flaper87#startmeeting Glance Drivers14:01
openstackMeeting started Tue Nov 17 14:01:08 2015 UTC and is due to finish in 60 minutes.  The chair is flaper87. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: Glance Drivers)"14:01
openstackThe meeting name has been set to 'glance_drivers'14:01
mclareno/14:01
rosmaita_o/14:01
*** rosmaita_ is now known as rosmaita14:01
flaper87w000h000014:01
*** jckasper has joined #openstack-meeting-414:01
*** ekarlso has joined #openstack-meeting-414:01
flaper87I just added 1 topic to the agenda as there are some things to discuss. mclaren has raised some concerns that would be great to have a short discussion on14:02
nikhil_ko/14:02
flaper87#topic Glance image import process: https://review.openstack.org/#/c/232371/ (flaper87 / mclaren)14:02
*** openstack changes topic to "Glance image import process: https://review.openstack.org/#/c/232371/ (flaper87 / mclaren) (Meeting topic: Glance Drivers)"14:02
flaper87nikhil_k: helloooooooo14:02
rosmaitai also want to discuss some of doug's comments14:02
nikhil_kyehlooo!14:02
flaper87nikhil_k: :P14:02
flaper87rosmaita: +114:03
flaper87so, mclaren you've 15 mins14:03
flaper87:D14:03
flaper87go crazy14:03
mclarenheh, ok14:03
mclarenI guess I have two things on my mind14:03
mclaren1) What we're proposing seems like a like of code/maintenance -- we just need to ensure it's all absolutely required14:04
*** jruano_ has quit IRC14:04
mclaren2) It's unclear to me what will happen to boring old image upload -- which is actually the closest we currently have to a standard way to get your images into clouds14:05
*** pmesserli has joined #openstack-meeting-414:06
mclarenfollowing on from (1) I guess in part I don't want us to write something that doesn't end up being used, is there a risk that folks would just keep using direct upload?14:06
flaper87I think 1 and 2 are somewhat related and it'll depend on us to provide a way to move from the old way of doing things to the new one14:06
mclarenyes 1 and 2 are related, I agree14:07
flaper87In the future, we can even switch the old one to admin only14:07
flaper87by default14:07
rosmaitamclaren: we are not going to use direct upload in the public cloud, for sure14:07
mclarenrosmaita: you're also not going to use the import from glance14:07
*** igordcard has joined #openstack-meeting-414:07
rosmaitano, we are going to align with upstream14:08
rosmaitaotherwise i wouldn't be working on this at all!14:08
nikhil_kI would like to think of it as a popular way rather than standard way as there are technical limitations/questions around it (direct upload).14:08
flaper87nikhil_k: ++14:08
flaper87I like that14:08
rosmaitanikhil_k: +114:08
mclarenthe question is more around folks who currently allow direct upload -- how happy are they? Are they strongly motivated to switch? Do they want that to be effectively de-emphasissed14:08
flaper87I'm not willing to assume things about how they feel and instead, I think we should focus on the current technical issues that have been identified14:09
rosmaitai have sent requests for comments to product WG, didn't get anything14:10
flaper87As far as moving from one to the other goes, I still think providing a smooth way to transition will be the key14:10
rosmaitai was hoping they could tell us how they see the cloud being used for image import14:10
rosmaitaalso, API WG is silent ... i am beginning to get a complex14:10
rosmaitaguess i need to attend a meeting and ask directly14:11
mclarenWe can't ignore it's what 99% of sites are doing right now, and that means user's have certain expectations. It would be ironic to break users' stuff in the name of interoperability. I'm not saying we can't go there, but I'd feel better if we had clear feedback from operators.14:11
flaper87rosmaita: that'd be great14:11
rosmaitaok, i will do that14:11
nikhil_kI think the # of users/operators who are preferring direct uploads are more as they are smaller deployments, mostly private and are not necessarily exposed to security, scalability and reliability threats.14:11
flaper87one of the main points of every discussion has been not breaking existing users, how are we doing that?14:11
mclarenIf sites switch off direct upload14:12
mclarenin favor of a new mechanism14:12
flaper87nikhil_k: the numbers we have are all from public clouds14:12
rosmaitabut they will do what their users want14:12
flaper87mclaren: but again, that doesn't mean we'd break them14:12
rosmaitai don't see the problem, stuart ... if the old way works, they can use it, if there's a new/better/safer way, they can work with their end users to adopt it14:13
flaper87we've talked about mechanisms to help this transition (Even from a client perspective)14:13
*** todin has joined #openstack-meeting-414:13
nikhil_kOTOH, we don't really have many larger public clouds coming and giving feedback as to what their issues are. or have they at the summit? (like cisco, walmart, bloomberg, verizon (not public but large) ) ?14:13
flaper87nikhil_k: ah, I meant the numbers w.r.t how many folks are using upload as an endpoint14:13
flaper87nikhil_k: but yeah, what you said is true as well14:13
flaper87rosmaita: Stuart's concern is that adding `/bikeshed` is too much work and that we may end up in a place where no one migrates to it14:14
flaper87which means we'd waste time14:14
rosmaitaok, i misunderstood14:14
rosmaitasorry, stuart14:14
mclarenpretty much, and you have three ways to upload images!14:14
rosmaitaso i kind of agree with him there14:14
flaper87My current point is, I don't think there's a way we can use the old `/file` endpoint without breaking the interoperability14:15
flaper87We talked about re-using it at the summit but we ended up agreeing it's not a good idea14:15
rosmaitawell, maybe we just say phase 1: import with task processing is via swift only14:15
mclarenSo I think the potential 'killer app' of the 'new way' is allowing asynchronous processing of the image (to either validate or convert it)14:15
rosmaitamclaren: ++14:16
flaper87right14:16
flaper87one of the things we discussed yday on -glance was to break this into 2 cycles14:16
mclarenbut it's not clear if that would be sufficient for operators/users to get over the complacency of just using the existing way14:16
flaper87because it's getting bigger and we're close to M-1 already14:16
*** julim has joined #openstack-meeting-414:16
rosmaitaflaper87: ++14:16
flaper87I don't mind holding off the `/bikeshed` work until N as long as we disable this "new way" by default until it's complete14:17
mclarenI guess it comes down to "what do operators want"? If there's a real appetite for the 'new way' then we go for it14:17
nikhil_kThat's true, can we break this down into baby steps?14:17
flaper87mclaren: fwiw, we've asked that already14:17
flaper87the spec is part of their feedback14:17
flaper87I don't think we're ignoring what operators want14:18
rosmaitais there any appetite for just using the current tasks framework, maybe with a more specified schema?14:18
flaper87wait, wait, wait. I still think we should do this work, we can start with things we've agreed on already14:18
mclarenflaper87: hmm, really? Can you be more specific? Do you mean the vancouver summit feedback?14:18
rosmaitabecause basically, that's what we're doing anyway, just with a fancier front end14:19
*** jckasper has quit IRC14:19
flaper87mclaren: not just vancouver. IIRC, the etherpad and the spec had some OPs chiming in. The summit session had OPs as well. Some of the complains/requests are being considered (automatic task trigger)14:19
mclarenflaper87: some indication that operators in the real world would actulally switch to using the 'new way' once it's been implemented would be great14:20
rosmaitaflaper87: here's my frustration ... when i talk to people individually at the product wg, people either (A) don't want to expose end-user upload at all, or (B) want the ability to validate end-user data before using it14:21
flaper87If I can be completely honest, I'm kind of sad we're back to discussing this because I feel like we're going backwards. I think it's healthy to ask ourselves answered questions from time to time but we've been talking about this since ~2 months before the summit14:21
rosmaitabut there is silence on the spec14:21
flaper87we're close to M-1 and now we're back to "why ware we doing this?" "Do we have all the info?"14:21
flaper87rosmaita: yeah, silence on the spec is sad14:22
flaper87but at this point, I believe this has been communicated quite openly14:22
*** bobh has joined #openstack-meeting-414:22
nikhil_khas anyone sent the spec link and review request to the operator and general openstack MLs?14:22
flaper87I'll join one of the OPs meetings14:22
flaper87nikhil_k: yeah14:22
rosmaitanikhil_k: i did last week14:22
nikhil_kcool14:22
mclarenSo let me explain my queries at this point ... I thought we were going to be forced to have a single API that looked the same everywhere. After the summit having different paths for swift and glance seemed to be considered ok14:22
mclarenSo at this point I'm hitting on 'what does the different glance path look like'14:23
rosmaitaright, because it would still "look the same" with the upload method clearly specified14:23
mclarenand tbh, I'd find it hard to spend 6 months writing the code while still wondering that :-)14:24
flaper87But the current way is not discoverable14:24
*** banix has joined #openstack-meeting-414:24
rosmaitaflaper87: that can be fixed easily14:24
rosmaitaadd "use import task" to POST /v2/images response header14:24
nikhil_kyes, when I had this conversation with month 8 months back, I proposed a simple discovery mechanism to simplify users experiece14:25
rosmaitaand define the task schema more clearly14:25
flaper87I guess but we also wanted to unify things in a single process. For example, the old `/file` endpoint doesn't trigger the task engine14:25
nikhil_koops,14:25
mclarenthe discoverability will look the same no matter what the actual calls are. The discoverability just tells us which fork of the path we go down ... glance or swift14:25
nikhil_kwith Monty* :)14:25
*** watanabe_isao has joined #openstack-meeting-414:26
*** jckasper has joined #openstack-meeting-414:26
nikhil_kI see 3 main concerns broken down from mclaren's raise14:26
mclarenflaper87: yes, the 'old way' doesn't give asynchronous processing. If there's a clear signal from operators that they want *and will deploy* that, then the debating is done I think14:26
flaper87mclaren: there have been several signals14:27
flaper87you can read that in my automatic-task-triggering spec14:27
flaper87there were at the vancouver summit14:27
mclarenok, more specifically, are they happy to switch off direct upload in order to get async processing14:27
flaper87Yes, that's my understanding from their feedback and the feedback from other folks in the community14:28
flaper87if we want to go and ask again on the OPs mailing list, then fine14:28
nikhil_k1) we have to maintain 2 old APIs as we have API contract (right?) 2) we need to add a bunch of code to support interop that needs to converge into defcore standards and we don't have a BETA with testing done, so that will involve code writing, testing and improvements 3) the support value and documentation for all 3 APIs would be massive even to the extent that a new operator and user would be a bit taken a14:28
nikhil_kback by the number of ways to upload image and would need bit of handholding14:28
nikhil_kumm, I am not too sure about it14:29
mclarenI'd personally feel happier with some direct feedback from ops on this. I'd be happy to send the mail myself.14:30
nikhil_kat least the operators who have openstack deployed in small labs, offices want the easier way14:30
nikhil_keasier == direct upload (or even just ability to set location)14:30
flaper87mclaren: please do. As I said, there has been direct feedback from ops some more won't hurt14:30
nikhil_kflaper87: I realized that there is one potential look hole into using location setting even with the new way, I will add that comment on the spec and continue the convo there14:31
nikhil_kloop*14:31
* nikhil_k is quite sleepy14:31
flaper87nikhil_k: awesome, thanks14:31
flaper87we ran out of time14:31
flaper87thanks folks, I guess we need to discuss this more14:31
mclarenwill disabling direct upload will require two glance clusters?14:32
rosmaitaso action items? rosmaita - product WG mtg, stuart - ops list14:32
flaper87rosmaita: yes14:32
flaper87rosmaita: also, API wg14:32
flaper87:)14:32
rosmaitaty!14:32
rosmaitawill do14:32
flaper87nope, thank YOU14:32
flaper87:D14:32
mclarenwill do14:32
flaper87#endmeeting14:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:32
openstackMeeting ended Tue Nov 17 14:32:47 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance_drivers/2015/glance_drivers.2015-11-17-14.01.html14:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance_drivers/2015/glance_drivers.2015-11-17-14.01.txt14:32
openstackLog:            http://eavesdrop.openstack.org/meetings/glance_drivers/2015/glance_drivers.2015-11-17-14.01.log.html14:32
*** ttx has quit IRC14:36
*** nikhil_k is now known as nikhil14:39
*** ekarlso has quit IRC14:40
*** ttx has joined #openstack-meeting-414:40
*** salv-orl_ has joined #openstack-meeting-414:45
*** mkarpin has joined #openstack-meeting-414:47
*** fawadkhaliq has joined #openstack-meeting-414:48
*** salv-orlando has quit IRC14:48
*** baohua has quit IRC14:49
*** woodard has quit IRC14:49
*** degorenko has joined #openstack-meeting-414:51
*** radez has joined #openstack-meeting-414:51
*** IvanBerezovskiy has joined #openstack-meeting-414:52
*** skolekonov has joined #openstack-meeting-414:52
*** rbak has joined #openstack-meeting-414:53
*** luis_ has joined #openstack-meeting-414:54
*** mdorman has joined #openstack-meeting-414:54
*** lakshmiS has joined #openstack-meeting-414:54
*** lakshmiS has left #openstack-meeting-414:55
*** richm has joined #openstack-meeting-414:58
*** mwhahaha has joined #openstack-meeting-415:00
EmilienM#startmeeting puppet-openstack15:00
openstackMeeting started Tue Nov 17 15:00:05 2015 UTC and is due to finish in 60 minutes.  The chair is EmilienM. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: puppet-openstack)"15:00
openstackThe meeting name has been set to 'puppet_openstack'15:00
mwhahahahi15:00
iurygregoryhello15:00
mkarpinhi15:00
degorenkohey o/15:00
mentathi all15:00
EmilienM#link agenda https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-2015111715:00
crinkleo/15:00
claytono/15:00
*** luis_ has quit IRC15:00
EmilienMI missed you guys15:00
EmilienM#topic review past items15:00
*** openstack changes topic to "review past items (Meeting topic: puppet-openstack)"15:00
mdormano/15:01
*** myatsenko1 has joined #openstack-meeting-415:01
EmilienMsbadia to investigate Trove bring broken in RDO (openstack-trove-taskmanager appears to be missing)15:01
sbadiahello15:01
EmilienMsbadia: do you have any status on this so far?15:01
richmhello15:01
angdraugo/15:01
sbadiaon the root issue yes (it's linked to the voting change of integration jobs)15:02
sbadiabut for taskmanager the package is in testing on centos repos15:02
EmilienMok, and not in GA repo, right?15:02
sbadiaand wasn't in stable yet15:02
aderyugin0/15:02
sbadiayep15:02
EmilienMok, thanks for working on that, we need to make sure it lands soon15:02
sbadiaheikel confirmed that15:03
sbadiayep shure!15:03
EmilienM#topic keystone federation status15:03
*** openstack changes topic to "keystone federation status (Meeting topic: puppet-openstack)"15:03
EmilienMiurygregory: o/15:03
EmilienMwhat's up?15:03
iurygregoryLet's go15:03
iurygregoryWell, to have K2K federation working we need https://review.openstack.org/#/c/216821/15:04
iurygregoryService Provider use Shibboleth, and to have this working on RedHat osfamily it is necessary to enable other repo15:04
iurygregoryhttps://github.com/puppetlabs/puppetlabs-apache/blob/master/manifests/params.pp#L8815:04
iurygregoryIn Debian everything is working15:05
EmilienMwe won't enable any exteral third party repo15:05
EmilienMit will be up to people deploying that feature15:05
iurygregoryyeah ;) i know15:05
iurygregoryso i think we have two options15:05
iurygregoryFail when try to use keystone::federation::shibboleth on RedHat15:06
*** chem has joined #openstack-meeting-415:06
EmilienMthough for testing purpose, I think it's ok to add the repo in acceptance15:06
iurygregoryShow a warning about not configuring Keystone VirtualHost (Should we configure keystone configuration file? /etc/keystone/keystone.conf15:06
chemEmilienM: I think this should be included in the module ...15:06
*** spredzy is now known as spredzy|afk15:06
EmilienMchem: the third party repo?15:06
EmilienMchem: http://lists.openstack.org/pipermail/openstack-dev/2015-September/075491.html15:07
chemEmilienM: because the apache module can use it15:07
EmilienMrichm: any thoughts?15:07
chemiurygregory is it epel ?15:07
richmI think it is fine if this is not supported on Red Hat family platforms for now15:07
richmOr, you have to somehow manually tell it that you are using the 3rd party repo to make it work15:08
EmilienMI don't think puppet-keystone should take care of Shibboleth apache mod15:08
claytonagreed/15:08
EmilienMI would rather patch puppetlabs-apache15:08
richmwhy not?  It takes care of mod_wsgi?15:08
claytonI think at most we document that it's missing on some distros and point people at where to get it15:09
EmilienMrichm: mod_wsgi is packages everywhere afik15:09
EmilienMclayton: +115:09
iurygregorychem, the repo is from opensuse http://wiki.aaf.edu.au/tech-info/sp-install-guide15:09
*** xarses has joined #openstack-meeting-415:09
*** dane has joined #openstack-meeting-415:10
xarseshi15:10
*** amotoki_ has joined #openstack-meeting-415:10
iurygregoryi think show a warning about not installing and configure shibboleth on redhat is fine15:10
EmilienMso I guess a first step would be to deliver it for debian only now, and add documentation explaining this repo thing15:10
iurygregoryyeah15:10
EmilienMiurygregory: a puppet warning?15:10
iurygregoryyep =)15:10
*** yottatsa has joined #openstack-meeting-415:11
EmilienMthat sounds good to me15:11
*** amotoki has quit IRC15:11
iurygregoryit's fine with me =)15:11
EmilienMany concern?15:11
claytonit would show a warning in what cases?15:12
EmilienMclayton: iiuc, when deploying shibboleth on redhat systems15:12
degorenkoin case of redhat15:12
degorenko+1 goodto me15:12
claytonand you'd have a flag to disable the warning?15:12
iurygregorywhen using redhat say that we will not configure shibboleth in the keystone virtualhost =)15:12
EmilienM+1 for the flag, yes. But by default we need to send it15:13
iurygregoryyeah clayton15:13
richmI think Red Hat is more focused on mellon than shibboleth15:13
chemEmilienM: why i though it would be a good idea is because of this https://github.com/puppetlabs/puppetlabs-apache/blob/master/manifests/params.pp#L12215:13
iurygregorywe can do this ^^15:13
claytonsure, but someone that's already solved that problem isn't going to want to see the warning all the time.  I think this is probably going too far to protect people from themselves personally.15:13
chemEmilienM: (took me a while to retrieve it)15:13
claytonI'd just document that it's missing on redhat and point people at where to look to fix it15:13
*** amotoki_ is now known as amotoki15:13
EmilienMchem: mhh, interesting o_O15:13
chemEmilienM: iurygregory richm it's supported in the puppet apache module, provided we give the repo15:14
richmok15:14
*** holser has joined #openstack-meeting-415:14
chemEmilienM: iurygregory richm that's why I think that it's a good thing to leverage the official upstream code15:14
holsero/15:14
*** Guest87553 is now known as sigmavirus2415:15
EmilienMiurygregory: have you tried what chem suggests?15:15
iurygregoryi didn't try to set the repo and see how is working on centos15:15
*** MarkAtwood has joined #openstack-meeting-415:15
*** Guest80875 is now known as mfisch15:16
EmilienMiurygregory: maybe you should first try it15:16
*** Guest48327 is now known as masteinhauser15:16
chemEmilienM: iurygregory richm it would be obviously a exeption to a good rule (no external repo), but in the end I'm not that strong minded about this, it's just that the code is there ...15:16
*** mfisch is now known as Guest2059415:17
iurygregoryok EmilienM ^^15:17
Guest20594sorry Im late15:17
claytonnp Guest2059415:17
EmilienMGuest20594: hey matt15:17
Guest20594dang it15:17
*** itisha has joined #openstack-meeting-415:18
*** Guest20594 is now known as mfisch15:18
*** mfisch has quit IRC15:18
*** mfisch has joined #openstack-meeting-415:18
EmilienMiurygregory: ok, let's continue the discussion on Gerrit. Please test if the module is in centos : https://github.com/puppetlabs/puppetlabs-apache/blob/master/manifests/params.pp#L122 and if not, we send a warning15:18
iurygregoryok =)15:18
chemEmilienM: it is not : https://github.com/puppetlabs/puppetlabs-apache/blob/master/manifests/params.pp#L8815:19
iurygregoryif we enable the repo it will be i think XD15:19
chemiurygregory correct :)15:19
chemok, I'm done15:19
EmilienMfor now, we won't add an extra repo in puppet-keystone15:20
iurygregoryso we go with the warning right?15:20
EmilienMwe need to investigate if fedora is interested by packaging this module, (not sure regarding what richm said)15:20
EmilienMotherwise, yes a warning *for now*15:20
chemack15:20
iurygregoryok ;) could some cores review https://review.openstack.org/#/c/216821/?15:20
iurygregoryTks ^^15:20
EmilienM#action review federation patche https://review.openstack.org/#/c/21682115:21
EmilienMiurygregory: anything else?15:21
iurygregorynp15:21
EmilienMthanks for this work15:21
iurygregorytks people15:21
EmilienM#topic os_service_defaults15:21
*** openstack changes topic to "os_service_defaults (Meeting topic: puppet-openstack)"15:21
EmilienMclayton, spredzy|afk: o/15:21
claytonWe've got a lot of pending reviews that are using this.  I think the concensus is that we can start using it, but just to be careful about not accidently changing existing values15:22
claytonbut I'd like to make sure that's the case15:22
EmilienMthat's sounds a great plan: 1/ switch to the new feature 2/ keep backward compatible15:23
iurygregory+115:23
mfischwhat else is holding it back from being uses everywhere?15:23
claytonok, I'd also like to know if people have any thoughts on requiring it for new changes?15:23
EmilienMclayton: like any new patch should require it?15:23
claytonConverting everything to use it is going to be a ton of work, but we can try not to make it worse15:23
claytonEmilienM exactly15:24
EmilienMclayton: I guess that's something we need to do *after* it lands15:24
claytonafter what lands?15:24
EmilienMand perform a iterative migration15:24
EmilienMfirst, a big patch per module15:24
EmilienMbut for sure we will miss some params, because WIP patches in the same repo15:24
claytonI don't think we should block new uses of it on existing params being converted.  Not sure if that's what you're proposing15:24
EmilienMso I guess we can drop a comment in all patches, but not -1 maybe, if the patch is ready to be merged15:25
EmilienMclayton: I agree15:25
claytonI'm fine with grandfathering existing patches, but anything new past x date should use it15:25
EmilienMclayton: +115:25
claytonwhat is x?  This week?  Next?15:25
EmilienMtoday15:26
claytonSounds good.15:26
mfisch+115:26
iurygregory+115:26
EmilienM#info os_service_defaults feature can be implemented in all modules from today15:26
EmilienMthe only concern I'm aware of was the logging stuff15:27
*** daneyon has joined #openstack-meeting-415:27
*** dane has quit IRC15:27
EmilienMclayton: I haven't followed yet but is it fixed^ ?15:27
claytonno, I think we were kind of waiting for a decision on service defaults, since I think it was generally agreed that was probably the best solution15:27
EmilienMthe best solution is to keep backward compatible, even if upstream is different15:28
EmilienMfor now, I think that's the best solution15:28
claytonthis was introduced in liberty, so only people on master should have this issue15:28
*** daneyon_ has joined #openstack-meeting-415:28
EmilienMif we really want to align with upstream, we will need to send some warnings to our users and change the default later one day15:28
claytonand it's potentially a huge problem for people upgrading from kilo, since it will double the number of db connections for people on stable/kilo15:28
EmilienMclayton: the logging stuff?15:28
*** vinsh has joined #openstack-meeting-415:29
EmilienMare we talking about the same thing?15:29
claytonoh, sorry, I misread, I thought we were on the db topic.15:29
EmilienMnope15:29
claytonI jumped ahead :)15:29
claytonEmilienM: yes, I agree on the logging, I think it should stay where it is15:29
EmilienMok great15:29
claytonI think the puppet module defaults are more sane than the upstream ones15:29
EmilienMand also for any other potential divergence15:29
claytonI think that is a rare situation, but one that will occasionally occur15:29
EmilienMuse os_service_defaults when we can, but if different from upstream -> use the default we had15:30
EmilienMwe need to document that15:30
degorenko+1 to this approach15:30
EmilienMany volunteer to write something in https://wiki.openstack.org/wiki/Puppet/Coding_style ?15:30
EmilienMif not clayton :-P15:31
claytonyou can assign it to me15:31
iurygregorylike add a section about when use os default?15:31
EmilienM#action clayton to update https://wiki.openstack.org/wiki/Puppet/Coding_style about os_service_defaults15:32
*** daneyon has quit IRC15:32
EmilienMclayton: thanks a lot15:32
claytoniurygregory : yeah, I think that's the idea15:32
EmilienM#topic incorrect defaults for *::db classes15:32
*** openstack changes topic to "incorrect defaults for *::db classes (Meeting topic: puppet-openstack)"15:32
EmilienMclayton, degorenko: hey15:32
iurygregoryif you need help you can ping ^^15:32
claytonthis is the topic I thought we were on :)15:32
EmilienM#link https://bugs.launchpad.net/puppet-tuskar/+bug/1515273)15:32
openstackLaunchpad bug 1515273 in puppet-tuskar "Defaults for *::db classes are incorrect" [Undecided,New]15:32
degorenkoyep :)15:32
EmilienMnot sure spredzy|afk is aroung15:32
EmilienMaround*15:33
*** galstrom_zzz is now known as galstrom15:33
*** numans has quit IRC15:33
degorenkoregarding https://bugs.launchpad.net/puppet-tuskar/+bug/1515273  i guess we should use defaults we had and raise warnings15:33
EmilienMclayton: what do you prefer?15:34
claytonI think we should use $::os_service_default for all of these values15:34
EmilienMI vote for keeping old default, which is 10 iirc15:34
EmilienMclayton: why? because openstack changed it?15:34
claytonthe default in sqlalchemy is currently 515:34
EmilienM(in liberty)15:34
claytonand it's always been 5 afaict15:35
claytonit's documented incorrectly in the neutron config file15:35
EmilienMwhat is the impact on the migration?15:35
claytonso the current way of doing it will double the number of connections most deployers have to their databases15:35
EmilienMis it fine for people who upgrade?15:35
claytonwhen they upgrade15:35
claytonwhich would be fine if we had a good reason for it and we documented it, but spredzy indicated it was basically an accident15:36
* xarses checks in fuel15:36
claytonI did the math for us, and it would take us from around 3k db connections in production to 6k.  Given load balancer and process fd limits, it would likely break some people, for probably no good reason15:36
*** woodard has joined #openstack-meeting-415:36
iurygregorywow15:37
mwhahahaso we never released those values15:37
EmilienMmwhahaha: right15:37
mwhahahaso if we switch them before the liberty release, then they won't have been released15:37
EmilienMmwhahaha: double right15:37
mwhahahaso we should fix them now :D15:37
mfisch+115:37
EmilienM+115:37
iurygregory+115:37
xarseshow do we end up with 3/6k from this value?15:38
claytonxarses let me explain15:38
*** blahRus has joined #openstack-meeting-415:38
claytonfor us, we have nova, neutron, heat, glance and cinder running on our control nodes, so 5 services, each has one process that connects to the db15:38
claytoneach of them spawns one worker per cpu core by default, so for us, 32 or 4015:38
*** galstrom is now known as galstrom_zzz15:38
claytonand previously we had 5 db connections for *each* of those processes, and this changes it to 1015:39
claytonoh, and we have 3 control nodes15:39
*** zeih_ has quit IRC15:39
claytonso 5 * 40 * 5 * 3 vs 5 * 40 * 10 * 315:39
claytonand that's the *minimum* number of db connections15:39
claytonoverflow allows it to go over that number, although we rarely see that happening15:40
claytongiven the number of workers15:40
*** bpokorny has joined #openstack-meeting-415:40
*** bpokorny has quit IRC15:40
EmilienMclayton: can you send a patch in puppet-cinder with the fix so we can start from here and help to fix it before the release?15:41
*** bpokorny has joined #openstack-meeting-415:41
claytonit's actually already fixed in puppet-cinder15:41
claytonthat's why it's not listed in the bug report15:41
EmilienMoh nice15:41
claytonbecause it's been converted over already15:41
xarsesok, thanks15:42
EmilienMclayton: so we need to use $::os_service_default for these params?15:42
claytonI think that's the best way to go15:42
EmilienMok15:43
EmilienMany concern about it?15:43
claytonnope, we're already doing it for puppet-cinder.  We have the code in production for that already15:43
EmilienMjust a stupid question: is someone working on $::os_service_default conversion for our modules?15:44
EmilienMmwhahaha, degorenko, clayton, spredzy|afk ^ ?15:44
iurygregorydegorenko, i think15:44
degorenkoyep15:44
xarseswe are frequently setting max_pool_size = min($::processorcount * 5 + 0, 30 + 0)15:44
iurygregoryi've see some patches15:44
*** amotoki_ has joined #openstack-meeting-415:44
mwhahahawas going to try and get some of the initial test stuff started for everything if someone else hadn't yet15:44
EmilienMdegorenko: great. Do you have a LP to track the work?15:44
degorenkoEmilienM, https://review.openstack.org/#/q/status:open+branch:master+topic:os_service_default,n,z15:44
xarsesas a result of scale testing we have preformed15:44
EmilienMor a topic, nice!15:44
mwhahahai know we have some outstanding items for the os_package_type too15:45
degorenkoEmilienM, our trello board15:45
degorenkohttps://trello.com/c/XLJJJBF0/71-move-modules-to-the-os-service-default-pattern15:45
EmilienMdegorenko: great15:45
EmilienManything else about this topic?15:46
xarsesclayton: ^15:46
claytonnope15:46
EmilienM#topic Open Discussion, Bug and Review triage15:46
*** yamamoto has quit IRC15:46
*** openstack changes topic to "Open Discussion, Bug and Review triage (Meeting topic: puppet-openstack)"15:46
degorenkonope, i'm good with solution from clayton15:46
EmilienMif you have questions, patches, bugs, or just want to say something, go ahead now15:46
mwhahahahttps://review.openstack.org/#/c/244900/15:47
mwhahahai ran into that when trying out the upstream modules in fuel15:47
*** amotoki has quit IRC15:47
myatsenko1Guys plz review this patch https://review.openstack.org/#/c/233011/ , its about floating ip range support.15:47
mwhahahaas well as https://review.openstack.org/#/c/243912/15:48
aderyuginhttps://review.openstack.org/#/c/220238/15:48
EmilienMmwhahaha: sounds good to me15:48
degorenkoone more bug faced in fuel :) https://review.openstack.org/24587615:48
*** bnemec has quit IRC15:48
chemmwhahaha: that's strange the default should be taken into account15:49
chemmwhahaha: that's strange the default case should be taken into account15:49
chemmwhahaha: that is, "if default don't add the domain suffix"15:49
*** armax has quit IRC15:49
chemmwhahaha: I'll look into the whole thing, and review later.  Thank for bringing this up15:50
xarsesclayton: We set them high in fuel as a result of scale testing up to 30 / 60. https://github.com/openstack/fuel-library/blob/master/deployment/puppet/osnailyfacter/modular/openstack-controller/openstack-controller.pp#L67-L7115:50
*** jpena has joined #openstack-meeting-415:50
mwhahahachem it's from the fact that when it goes to look up the resources the names get changed to include the domain15:50
mwhahahachem: that review is a workaround but we need to touch that code (it's really old from 2013)15:50
*** Piet has quit IRC15:50
*** britthou_ has joined #openstack-meeting-415:51
EmilienMaderyugin: where is functional testing on https://review.openstack.org/#/c/220238/ ?15:51
chemmwhahaha: but to keep backward comptatibility if the domain is default, the module shouldn't add "::Default" suffix to the name15:51
chemmwhahaha: that's how I though it was working anyway :)  but maybe I missed something15:51
mwhahahachem: right but we broke backwards compatibility with the review that put it in i thought :D15:52
chemmwhahaha: not for this15:52
mwhahahawe don't specify the resource in our catalog so it only affects lookups on tenants15:52
chemmwhahaha: anyway I'll have a look today.15:52
mwhahahasure15:52
degorenkoEmilienM, do you mean acceptance? for 22023815:52
EmilienMdegorenko: yes15:53
*** britthouser has quit IRC15:53
EmilienMmwhahaha: one question - are all modules on the same page about https://github.com/openstack/puppet-cinder/commit/70daad9ea4a25471f4d40b78ad70ae0aa2f99a1e ?15:54
degorenkoEmilienM, we can try to add it, but probably in upstream murano packages missed one file :)15:54
EmilienMdegorenko: ok, just asking15:54
degorenkoaderyugin, can provide more information i guess15:54
mfischI will review the murano one today15:54
EmilienMdo we have anything else for today?15:55
aderyuginEmilienM: right now application provider will not pass acceptance, since default application is missing from upstream package15:55
mwhahahayea i think they are15:55
EmilienMaderyugin: ok - please make sure it's wip by packaging people15:55
EmilienMmwhahaha: ok, just checking15:55
aderyuginEmilienM: ok15:56
EmilienMaderyugin: it won't block anything15:56
degorenkoone more request for review :) https://review.openstack.org/#/c/216654/15:56
EmilienM#action emilien to check https://github.com/openstack/puppet-cinder/commit/70daad9ea4a25471f4d40b78ad70ae0aa2f99a1e is consistent across all modules15:57
myatsenko1and this one https://review.openstack.org/#/c/233011/15:57
mfischwe should use the meeting commands for reviews so they're in the logs15:57
delatteif possible would like this reviewed as well https://review.openstack.org/#/c/197572/  I know clayton reviewed but was looking for others15:57
mfischyou have a -1 from ody15:58
EmilienMmfisch: #action is here for that15:58
mfischEmilienM: yes lets use it15:58
mfisch#action everyone to use #action when posting reviews they want reviewed15:58
degorenko#action review https://review.openstack.org/24587615:58
degorenko#action review https://review.openstack.org/#/c/216654/15:59
EmilienMok, anything else but reviews before closing the meeting?15:59
myatsenko1#action review https://review.openstack.org/#/c/233011/15:59
xarsesI have not so much as a problem, but I need some help splitting up some of the ci in puppet-ceph and was wondering if any one was up to helping me through the process15:59
delattemfisch:  if you read his comments, it a "way we do things" -1.  was hoping for cores to weigh in15:59
*** johnsom has joined #openstack-meeting-415:59
EmilienMxarses: you come up 30s before the end :(15:59
mkarpin#action review https://review.openstack.org/#/c/241614/15:59
aderyugin#action review https://review.openstack.org/#/c/220238/15:59
iurygregory#action review  https://review.openstack.org/#/c/216821/15:59
EmilienMxarses: mailing list15:59
xarsesEmilienM: its not so important to address here15:59
EmilienMthanks everyone, have a great day16:00
mfischwe're out of time16:00
EmilienM#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Tue Nov 17 16:00:06 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/puppet_openstack/2015/puppet_openstack.2015-11-17-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/puppet_openstack/2015/puppet_openstack.2015-11-17-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/puppet_openstack/2015/puppet_openstack.2015-11-17-15.00.log.html16:00
*** mwhahaha has left #openstack-meeting-416:00
*** richm has left #openstack-meeting-416:00
*** holser has left #openstack-meeting-416:00
*** chem has left #openstack-meeting-416:01
*** xarses has left #openstack-meeting-416:01
*** iurygregory has left #openstack-meeting-416:01
mugsiehey16:03
mugsiewhos where?16:03
johnsomo/16:03
*** bnemec has joined #openstack-meeting-416:03
mugsie#startmeeting Kosmos16:03
openstackMeeting started Tue Nov 17 16:03:49 2015 UTC and is due to finish in 60 minutes.  The chair is mugsie. Information about MeetBot at http://wiki.debian.org/MeetBot.16:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:03
*** openstack changes topic to " (Meeting topic: Kosmos)"16:03
openstackThe meeting name has been set to 'kosmos'16:03
*** jpena has left #openstack-meeting-416:03
mugsie#topic roll call16:03
*** openstack changes topic to "roll call (Meeting topic: Kosmos)"16:03
*** mkarpin has left #openstack-meeting-416:04
johnsomo/16:04
johnsomHi there16:04
mugsiehey16:04
mugsiemight just be us ...16:04
johnsomThe important folks!  grin16:04
mugsieexactly :)16:04
mugsiexgerman: dougwig courtesty ping16:05
johnsomI am triple booked today, so this is fun.16:05
xgermanpong16:05
xgermanI am only double booked16:05
johnsomOne muted, one presenting, and reading the other.16:05
mugsiehaha16:05
mugsie#topic Action Items16:06
*** openstack changes topic to "Action Items (Meeting topic: Kosmos)"16:06
mugsiexgerman to follow up with Yahoo16:06
xgermanyep, I did they want us eventually present to them16:06
johnsomHe did that.16:06
mugsiecool.... what sort of presentation?16:06
mugsie"this is a POC" ?16:06
mugsieor "this is a finished product"16:07
xgermanwell, mostly LBNaaS related and how they can contribute16:07
mugsieah, ok16:07
mugsie#topicOpen Discussion16:07
mugsie#topic Open Discussion16:07
*** openstack changes topic to "Open Discussion (Meeting topic: Kosmos)"16:07
mugsieso, I have just finished a 5k line diff for designate16:08
mugsieso once that merges I am on Kosmos dev16:08
johnsomFun!16:08
mugsieanyone have any other topics?16:08
johnsomCool.  I was going to ask how we can light a fire under this thing16:08
xgermanyeah, we were thinking of adding a more Junior dev to the project16:08
*** SimonChung1 has quit IRC16:09
mugsiefor midcycle - its looking like seattle 13-16 right for octavia?16:09
xgermansan anotnio came up agian16:09
xgermanso I think we will get the final call on Wednesday16:09
johnsomDefinitely Jan 13-16th16:09
mugsiewell, if it is seattle, we should be able to have a mini Kosmos one the day before.16:09
mugsieif it is not, it does not look like I will get travel approval16:10
johnsomYeah, that would be good16:10
xgermanyeah, and I will try to colocate FWaaS as well16:10
mugsieso, if we can push Octavia to seattle - ++16:10
mugsie:D16:10
*** BjoernT has joined #openstack-meeting-416:10
xgermanwell, no trip to Ireland for me and hohnsom :-(16:10
johnsomOk.  Your travel restriction is a good reason, so I will push for Seattle16:11
*** IlyaG has joined #openstack-meeting-416:11
mugsieok, anyone have any other topics?16:11
mugsieor will we let the double and triple booked people get back to the other meetings?16:11
xgermanyeah, do you want us to assign a Junior Dev/16:12
xgerman?16:12
xgermando you have bandwidth to mentor?16:12
johnsomYeah, and do we have a starting point planned?16:12
mugsieI would like a few days / a week to sit down before being able to relyable answer that16:12
*** lazy_prince has quit IRC16:12
mugsierelyably*16:12
mugsieI think I would, but not right now16:13
*** belmoreira has quit IRC16:13
mugsieonce the base frame is in place, it would be a lot easier16:13
johnsom+116:13
xgermanok, just holler and we will put it in our sprint16:13
mugsiecool16:13
mugsieOK then.16:15
mugsie#endmeeting16:15
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:15
openstackMeeting ended Tue Nov 17 16:15:27 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:15
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kosmos/2015/kosmos.2015-11-17-16.03.html16:15
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kosmos/2015/kosmos.2015-11-17-16.03.txt16:15
openstackLog:            http://eavesdrop.openstack.org/meetings/kosmos/2015/kosmos.2015-11-17-16.03.log.html16:15
mugsiejohnsom: I will let you read and listen :)16:15
johnsomThanks!16:15
*** johnsom has left #openstack-meeting-416:16
*** limao has quit IRC16:17
*** mdorman has left #openstack-meeting-416:18
*** BjoernT has left #openstack-meeting-416:18
*** bpokorny_ has joined #openstack-meeting-416:19
*** bpokorny has quit IRC16:19
*** amotoki_ has quit IRC16:19
*** _d34dh0r53_ is now known as d34dh0r5316:22
*** salv-orl_ has quit IRC16:26
*** nkrinner has quit IRC16:27
*** julim_ has joined #openstack-meeting-416:27
*** armax has joined #openstack-meeting-416:28
*** bogdando has quit IRC16:29
*** julim has quit IRC16:30
*** Piet has joined #openstack-meeting-416:31
*** tbh has joined #openstack-meeting-416:33
*** jwagner_away is now known as jwagner16:36
*** armax has quit IRC16:37
*** cloudtrainme has joined #openstack-meeting-416:40
*** armax has joined #openstack-meeting-416:40
*** yamamoto has joined #openstack-meeting-416:47
*** gjayavelu has joined #openstack-meeting-416:47
*** yamamoto has quit IRC16:52
*** IlyaG_ has joined #openstack-meeting-416:54
*** ALUvial has joined #openstack-meeting-416:55
*** jbratton has joined #openstack-meeting-416:55
*** vishwana_ is now known as vishwanathj16:55
*** harshs has joined #openstack-meeting-416:58
*** IlyaG has quit IRC16:58
*** Sukhdev has joined #openstack-meeting-416:58
*** angdraug has quit IRC16:59
*** britthou_ is now known as britthouser17:00
*** Sukhdev has quit IRC17:00
*** brucet has joined #openstack-meeting-417:00
*** Sukhdev has joined #openstack-meeting-417:01
*** santoshkumark has joined #openstack-meeting-417:01
*** natarajk has joined #openstack-meeting-417:01
*** watanabe_isao has quit IRC17:01
*** sridhar_ram has joined #openstack-meeting-417:02
sridhar_ram#startmeeting tacker17:02
openstackMeeting started Tue Nov 17 17:02:50 2015 UTC and is due to finish in 60 minutes.  The chair is sridhar_ram. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: tacker)"17:02
openstackThe meeting name has been set to 'tacker'17:02
sridhar_ram#topic Roll Call17:02
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"17:03
natarajkhi17:03
sridhar_ramwho is here for tacker ?17:03
vishwanathjo/17:03
sridhar_ramnatarajk: hi17:03
bobho/17:03
natarajko/17:03
*** Swami has joined #openstack-meeting-417:04
sridhar_ramlets get started...17:04
sridhar_ram#topic Announcement17:04
*** openstack changes topic to "Announcement (Meeting topic: tacker)"17:04
*** tpeoples_away is now known as tpeoples17:04
sridhar_ramAgenda #link https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Nov_17.2C_201517:05
tbho/17:05
sridhar_ramrather lite today.. any open items welcome!17:05
sridhar_ramtbh: hi there17:05
tbhsridhar_ram, Hi17:06
brucethello17:06
santoshkumarkHello all17:06
brucetI did not see any new Blueprints this past week17:06
sridhar_ramSripriya is offically a new core member!17:06
sridhar_rambrucet: hi there, hang on a bit.. we will get to it17:06
brucetOK17:06
sridhar_ramI believe Sripriya is traveling and not here today17:07
sridhar_ram#topic Mitaka Blueprints and RFEs17:07
*** openstack changes topic to "Mitaka Blueprints and RFEs (Meeting topic: tacker)"17:07
sridhar_rambobh: any quick update on the tosca-parser activities ?17:08
bobhI created the tosca-parser BP and Sahdev has replied that they will review it soon.  I believe I need to create a corresponding heat-translator BP and one in tacker-specs too17:08
bobhI've been working on the tosca-parser changes in the background, hopefully something will be working soon17:09
sridhar_rambobh: sounds good. provide gerrit links when available..17:10
*** s3wong has joined #openstack-meeting-417:10
bobhwill do17:10
s3wongsorry, a bit late17:10
*** IvanBerezovskiy has left #openstack-meeting-417:10
sridhar_rambobh: have you thought about how the tacker part of the BP will look like ?17:10
bobhsridhar_ram: There are several pieces - (1) incorporating the new tosca-parser library, (2) changes to the existing tosca parsing code to handle the "new" and the "old" formats, and (3) incorporating the new heat-translator capabilities17:11
bobh(2) could be an issue - there are significant differences between what we support today and the official TOSCA NFV Profile17:12
sridhar_rambobh: exactly .. that's what I'm curious about.. the level of feature parity between the two17:12
sridhar_rambobh: anyway, it is fair for you to write up your thoughts in the BP and have everyone here review & comment17:13
bobhsridhar_ram: I need to do a full comparison but I think the differences may be significant17:13
brucetWhat about existing heat resources? Anything needed there??17:13
bobhbrucet: Do you mean new resources?17:13
brucetYes. Heat resources17:14
sridhar_rambobh: the two stand out items for us to carry over is mgmt_driver and mon_driver to the new format17:14
brucetTosca translator >> Heat template, right??17:14
*** jbratton has left #openstack-meeting-417:14
*** yottatsa has quit IRC17:15
bobhbrucet: right - I think that the existing heat-translator supports (many) more Heat resources than our home-grown translator does today17:15
brucetOh. This is not built on existing Tosca >> Heat translator??17:15
bobhbrucet: we may find additional things we need in the heat-translator bp/spec after the tosca-parser work is done17:15
bobhbrucet: Existing tacker code generates heat from tosca "manually"17:16
sridhar_rambrucet: at high level, what is currently in heat-translator is tosca-simple-profile --> heat .. for Mitaka we want to get to tosca-nfv-profile --> heat17:16
bobhbrucet: so by moving to the official tosca-parser/heat-translator codebase we will gain a lot of capabilities17:16
sridhar_rambrucet: that is the scope of this effort, bobh correct if I'm wrong17:16
brucetOK17:17
bobhsridhar_ram: correct17:17
brucetGot it, thx17:17
sridhar_rambrucet: sure17:17
sridhar_ramlets discuss more on tosca-parser once some BPs write up show up17:18
sridhar_rambobh: thanks for the update.. looks things chugging nicely here!17:18
sridhar_ramtbh: I know you picked up Auto Flavor / Auto Network creation.17:18
sridhar_ramtbh: can you provide your thoughts & updates ?17:19
tbhsridhar_ram, I have seen the new rfe reported by you for flavor17:19
sridhar_ramhttps://bugs.launchpad.net/tacker/+bug/151619317:19
openstackLaunchpad bug 1516193 in tacker "Automatic Flavor Creation based on VNFD Template" [Medium,New] - Assigned to bharaththiruveedula (bharath-ves)17:19
sridhar_ramtbh: I still need to write on for Auto Network creation :(17:20
tbhsridhar_ram, but I think we will continue with automatic flavor creation once we get the done with tosca parser intergration?17:20
sridhar_rams/on/one/17:20
sridhar_ramtbh: no, I would prefer for us not to put tosca-parser dependency for the things in flight17:21
tbhsridhar_ram, I will write that17:21
tbhsridhar_ram,  you mean to use existing tosca parse/heat translator for that?17:21
sridhar_ramtbh: bobh: this is the part I need some clarification17:22
sridhar_ramtbh: bobh: how do you envision tosca-nfv-parser work will help in this auto-flavor effort ?17:23
*** SimonChung has joined #openstack-meeting-417:23
bobhsridhar_ram: We need to determine if the existing heat-translator code can generate a heat template that auto creates a flavor, network, etc17:23
bobhsridhar_ram: if it does/can, we will get that functionality for "free" when we move to using tosca-parser/heat-generator17:24
tbhbobh, no, it wont create. It just maps vnf details -> flavor name17:24
bobhtbh: ok, so the next question is where should that capability go?17:24
tbhbobh, sridhar_ram  but that too heat-translator is not using nova client to get flavor details17:24
bobhtbh: sridhar_ram I think we could argue that this is an enhancement to heat-translator?17:25
*** matrohon has quit IRC17:25
bobhsridhar_ram: Since we want to get out of the heat generation business right?17:25
tbhbobh, sridhar_ram  this is related BP https://blueprints.launchpad.net/heat-translator/+spec/match-custom-flavor17:26
*** gjayavel_ has joined #openstack-meeting-417:26
tbhbobh, yes, I think it must go in heat translator17:27
bobhtbh: Agree - and if there are admin issues around creating custom flavors that will need to be addressed too - maybe Tacker is "admin"-enough that it's not a problem17:27
sridhar_rambobh: true, but flavor has lot more things riding on it .. it is not just cpu, mem. there are aspect of efficient VNF placement that goes into Nova flavor17:27
bobhsridhar_ram: agree17:28
sridhar_ramlooks we need more data here.17:28
sridhar_ramvishwanathj: you also need to get your efficient placement requirements into the mix and have it supported by what bobh and tbh are building17:29
*** gjayavelu has quit IRC17:29
vishwanathjsridhar_ram, agree17:30
sridhar_rambut this criss-cross dependency scares me a bit.. lets see if we can break these into smaller work items among us17:30
sridhar_ramif tacker needs to be in the business of flavor create - say using vnfd-create17:31
sridhar_ramthat will give us some control to handle different performance level metadata17:31
*** salv-orl_ has joined #openstack-meeting-417:32
bobhsridhar_ram: that would be one solution - initial analysis during vnfd-create, but it doesn't prevent the available flavors from changing between vnfd-create and vnf-create17:32
sridhar_rambobh: true, in fact I'd suggest we SHOULD NOT rely on existing flavors in the nova flavor-list17:32
sridhar_rambobh: flavor shd always be created using custom uuid and live thru' the lifetime of the vnfd17:33
sridhar_ramthere is a section in tosca called host_properties: .17:33
bobhsridhar_ram: so it might be that we want to put a layer between the tosca-parser output and the heat-translator input where we do flavor analysis and inject some custom flavor creation into the tree17:34
bobhsridhar_ram: need to ensure that heat-generator will support creating custom flavors17:34
sridhar_rambobh: spot on.. that's a clear value that tacker can bring in17:34
tbhsridhar_ram, bobh yeah, but I don't think new flavor for every vnfd, but analyse flavor details of tacker created flavors17:34
tbhbobh, heat generator you mean tacker heat generator, or heat code?17:36
sridhar_ramtbh: in trying to analyze existing flavors, we are mostly trying to be db efficient..17:36
bobhtbh: Flavors are "cheap" - they don't use any resources by themselves, so I think it is reasonable to tie them to the VDU/VNFD17:36
sridhar_ramtbh: I don't think that's an issue17:36
sridhar_rambobh: +117:36
bobhtbh: sorry - heat-translator - my brain keeps saying heat generator17:36
vishwanathjheat-generator is expected to work only for the OpenStack VIM, right? if we support other VIMs, a different tosco to that particular VIM generator would be needed17:36
bobhvishwanathj: correct17:37
sridhar_ramvishwanathj: that's a good point.. current code intermingles tacker functions in heat-parser.17:37
tbhagree17:37
sridhar_ramhope we can clean that a bit and get a nice layer of separation17:38
sridhar_rambobh: no pressure ;-)17:38
bobhsridhar_ram: yeah right17:38
sridhar_ramtbh: once you've some data .. you can use the RFE bug to write up how you are planning to implement17:39
sridhar_ramtbh: we can get to impl after that. fair ?17:39
tbhsridhar_ram, sure17:39
sridhar_ramtbh: quickly on network creation, the note I got from tosca folks is .. if network param indicates a "name" we should assume the network is already available (like the way it is today)17:40
sridhar_ramif the network: is described as ip_addr/netmask/vlan .. that's the cue to do auto-network creation17:41
sridhar_ramanything else to discuss auto-flavor / net area?17:42
tbhsridhar_ram, I think even in second case we can specify name17:42
tbhis that correct?17:42
sridhar_ramtbh: sure.. it become more a well known name17:43
*** prashantD has joined #openstack-meeting-417:43
sridhar_ramlets move on to the next topics17:43
sridhar_ram#topic Bugs / Docs / Infra17:43
*** openstack changes topic to "Bugs / Docs / Infra (Meeting topic: tacker)"17:43
sridhar_ramanyone (include tacker users) want to bring up any significant bugs to our attention ?17:44
*** Piet has quit IRC17:44
*** jmccrory has quit IRC17:44
santoshkumarksridhar_ram i have a bug on monitoring, looking for bugid..17:44
sridhar_ramsantoshkumark: sure...17:45
sridhar_ramone thing from my side that is bothering me is https://bugs.launchpad.net/tacker/+bug/150546817:45
openstackLaunchpad bug 1505468 in tacker "Error status after creating a vnf - TypeError: <type 'NoneType'> can't be decoded" [High,New]17:45
sridhar_ramthis  shows up periodically with "Port in conflict vdu1_mgmt_port still in use" or something like that17:46
sridhar_ramif anyone hits this issue please provide some data in the above bug17:46
sridhar_ramsantoshkumark: got the bug id ?17:47
santoshkumarkhttps://bugs.launchpad.net/tacker/+bug/151397217:47
openstackLaunchpad bug 1513972 in tacker "vnf monitoring fails after multiple vnf create/delete operations" [Undecided,New]17:47
*** salv-orl_ has quit IRC17:47
*** salv-orlando has joined #openstack-meeting-417:48
santoshkumarkthis bug is seen when vnf creation goes to ERROR state,17:48
s3wongsorry, need to drop off17:48
*** s3wong has quit IRC17:48
*** GheRivero has quit IRC17:49
santoshkumarkWhy will vnf create might be error: one reason is if number of vm limits are exceeded while vnf create..17:49
*** aglarendil has quit IRC17:49
*** alex_didenko has quit IRC17:49
sridhar_ramsantoshkumark: in those situation i would expect the system to gracefully fail...17:50
santoshkumarksridhar_ram: this bug is not a stopper..but can cause monitoring to fail..17:50
*** ashtokolov has quit IRC17:50
sridhar_ramsantoshkumark: looks a respawn failed due to resource limits exhaustion ?17:50
tbhsridhar_ram, do we need to monitor, if the VNF goes to ERROR state?17:51
sridhar_ramanyway, lets see if anyone have bandwidth to take it up..17:51
sridhar_ramtbh: no17:51
* sridhar_ram 10mins left17:51
santoshkumarksridhar_ram: not sure if respawn..17:51
tbhany comments on this bug patch https://bugs.launchpad.net/tacker/+bug/1503477 will be appreciated17:52
openstackLaunchpad bug 1503477 in tacker "Provide respawn limit for respawn failure policy" [Medium,In progress] - Assigned to bharaththiruveedula (bharath-ves)17:52
tbhit's been so long17:52
*** carl_baldwin has quit IRC17:52
*** tpeoples has quit IRC17:53
bobhtbh: I've looked at it a couple of times but never had time to do a thorough review17:53
bobhtbh: I'll try to spend some time on it this week17:53
tbhbobh, sure thanks17:53
sridhar_ramtbh: we can take some of monitoring related enhancements after we make some progress in Mitaka priorities.17:54
tbhsridhar_ram, okay17:54
sridhar_ramI need another help from the team ..17:54
sridhar_ramanyone here know how to waddle through openstack-infra project-config ?17:54
sridhar_ramI could use some help to land tacker repos to pypi17:55
*** natarajk1 has joined #openstack-meeting-417:55
sridhar_ramreach out if someone has some expertise here..17:56
sridhar_rammoving on...17:56
sridhar_ram#topic Open Discussion17:56
*** openstack changes topic to "Open Discussion (Meeting topic: tacker)"17:56
sridhar_ramquick poll.. how many of here would like to install Tacker in a non-devstack environment ?17:57
*** pmesserl_ has joined #openstack-meeting-417:57
bobho/17:57
*** markvoelker_ has joined #openstack-meeting-417:57
tbho/17:57
*** natarajk has quit IRC17:57
natarajk1o/17:57
sridhar_ramokay.. there is multiple asks coming in the irc channel regardign this17:58
sridhar_ramwe should take it up as a work item then17:58
*** jmccrory has joined #openstack-meeting-417:58
sridhar_ramanything else ?17:58
bobhsridhar_ram: Also seems like we need a way t validate that heat/nova are working17:58
*** ivar-lazzaro has joined #openstack-meeting-417:59
*** banix_ has joined #openstack-meeting-417:59
*** SimonChung has quit IRC17:59
*** banix has quit IRC17:59
*** pkoniszewski_ has quit IRC17:59
*** banix_ is now known as banix17:59
bobhLots of questions come in because VNF 'failed to deploy'17:59
sridhar_rambobh: you mean a stack validate ?17:59
* sridhar_ram almost out of time17:59
bobhmore like an openstack-validate17:59
bobhis heat working?  is nova working?17:59
*** bnemec has quit IRC17:59
*** pmesserli has quit IRC17:59
bobhif the answer to either is no then tacker isn't going to work17:59
sridhar_rami think we should write a RFE and work through it ..17:59
*** klamath_ has joined #openstack-meeting-417:59
sridhar_rambobh: quite valid..18:00
*** santoshkumark has quit IRC18:00
*** markvoelker has quit IRC18:00
*** sbadia has quit IRC18:00
*** Kiall_ has quit IRC18:00
sridhar_ramtimes up folks..18:00
*** klamath has quit IRC18:00
sridhar_ramtalk to you next week18:00
vishwanathjbye all18:00
sridhar_rambye all18:00
bobhbye18:00
sridhar_ram#endmeeting18:00
tbhbye18:00
*** bnemec has joined #openstack-meeting-418:00
*** natarajk1 has left #openstack-meeting-418:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Tue Nov 17 18:00:35 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2015/tacker.2015-11-17-17.02.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2015/tacker.2015-11-17-17.02.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2015/tacker.2015-11-17-17.02.log.html18:00
*** Kiall has joined #openstack-meeting-418:01
*** tbh has quit IRC18:01
*** ivar-lazzaro has quit IRC18:03
*** armax has quit IRC18:06
*** pkoniszewski has joined #openstack-meeting-418:07
*** Sukhdev has quit IRC18:07
*** jwagner is now known as jwagner_away18:09
*** Sukhdev has joined #openstack-meeting-418:10
*** sbadia has joined #openstack-meeting-418:11
*** Sukhdev has quit IRC18:11
*** brucet has quit IRC18:14
*** s3wong has joined #openstack-meeting-418:14
*** MarkAtwood has quit IRC18:14
*** Sukhdev has joined #openstack-meeting-418:15
*** Sukhdev has quit IRC18:20
*** harshs has quit IRC18:22
*** sbalukoff1 has joined #openstack-meeting-418:22
*** fawadkhaliq has quit IRC18:26
*** qwebirc47081 has joined #openstack-meeting-418:26
*** armax has joined #openstack-meeting-418:26
*** qwebirc47081 has quit IRC18:26
*** carl_baldwin has joined #openstack-meeting-418:26
*** degorenko is now known as _degorenko18:27
*** baoli has quit IRC18:29
*** sridhar_ram has quit IRC18:29
*** bpokorny_ has quit IRC18:32
*** baoli has joined #openstack-meeting-418:32
*** samleon has joined #openstack-meeting-418:33
*** Sukhdev has joined #openstack-meeting-418:34
*** Sukhdev has quit IRC18:35
*** MarkAtwood has joined #openstack-meeting-418:35
*** Sukhdev has joined #openstack-meeting-418:36
*** Sukhdev has quit IRC18:36
*** dims has quit IRC18:37
*** gjayavel_ has quit IRC18:38
*** dims has joined #openstack-meeting-418:40
*** ashtokolov has joined #openstack-meeting-418:48
*** aglarendil has joined #openstack-meeting-418:48
*** alex_didenko has joined #openstack-meeting-418:50
*** bpokorny has joined #openstack-meeting-418:52
*** armax has quit IRC18:53
*** ivar-lazzaro has joined #openstack-meeting-418:53
*** armax has joined #openstack-meeting-418:55
*** GheRivero has joined #openstack-meeting-418:55
*** ivar-lazzaro has quit IRC18:57
*** banix has quit IRC18:57
*** SimonChung has joined #openstack-meeting-418:58
*** cloudtrainme has quit IRC18:59
*** bpokorny has quit IRC18:59
*** MarkAtwood has quit IRC18:59
*** sc68cal_ is now known as sc68cal19:00
*** irenab has quit IRC19:00
*** bpokorny has joined #openstack-meeting-419:01
*** banix has joined #openstack-meeting-419:01
*** harshs has joined #openstack-meeting-419:02
*** cloudtrainme has joined #openstack-meeting-419:03
*** samleon has quit IRC19:04
*** cloudtrainme has quit IRC19:19
*** bpokorny has quit IRC19:19
*** bpokorny has joined #openstack-meeting-419:19
*** bpokorny has quit IRC19:22
*** bpokorny has joined #openstack-meeting-419:22
*** cloudtrainme has joined #openstack-meeting-419:22
*** SimonChung has quit IRC19:22
*** SimonChung1 has joined #openstack-meeting-419:22
*** SimonChung1 has quit IRC19:23
*** SimonChung has joined #openstack-meeting-419:23
*** ekarlso has joined #openstack-meeting-419:24
*** SimonChung has quit IRC19:24
*** SimonChung1 has joined #openstack-meeting-419:24
*** jwagner_away is now known as jwagner19:24
*** Piet has joined #openstack-meeting-419:26
*** ivar-lazzaro has joined #openstack-meeting-419:26
*** bpokorny has quit IRC19:28
*** bpokorny has joined #openstack-meeting-419:29
*** tpeoples_ has joined #openstack-meeting-419:30
*** carl_baldwin has quit IRC19:35
*** igordcard has quit IRC19:36
*** carl_baldwin has joined #openstack-meeting-419:38
*** sridhar_ram has joined #openstack-meeting-419:43
*** angdraug has joined #openstack-meeting-419:48
*** salv-orlando has quit IRC19:48
*** baoli has quit IRC19:53
*** britthouser has quit IRC19:54
*** armax has quit IRC19:57
*** cloudtrainme has quit IRC19:58
*** banix has quit IRC19:59
*** Sukhdev has joined #openstack-meeting-420:03
*** sridhar_ram has quit IRC20:03
*** baoli has joined #openstack-meeting-420:03
*** cloudtrainme has joined #openstack-meeting-420:07
*** banix has joined #openstack-meeting-420:11
*** harshs has quit IRC20:13
*** cloudtrainme has quit IRC20:24
*** cloudtrainme has joined #openstack-meeting-420:26
*** banix has quit IRC20:26
*** cloudtrainme has quit IRC20:30
*** MarkAtwood has joined #openstack-meeting-420:32
*** cloudtrainme has joined #openstack-meeting-420:33
*** Swami has quit IRC20:35
*** baoli has quit IRC20:36
*** iyamahat has joined #openstack-meeting-420:41
*** Sukhdev has quit IRC20:51
*** salv-orlando has joined #openstack-meeting-420:51
*** salv-orlando has quit IRC20:51
*** salv-orlando has joined #openstack-meeting-420:52
*** Swami has joined #openstack-meeting-420:55
*** jwagner is now known as jwagner_away20:57
*** dims_ has joined #openstack-meeting-421:00
*** dims has quit IRC21:02
*** dzamboni has quit IRC21:03
*** AlanClark has joined #openstack-meeting-421:03
*** salv-orlando has quit IRC21:08
*** banix has joined #openstack-meeting-421:10
*** salv-orlando has joined #openstack-meeting-421:10
*** Rockyg has joined #openstack-meeting-421:28
*** banix has quit IRC21:29
*** banix has joined #openstack-meeting-421:32
*** krtaylor has quit IRC21:32
*** SimonChung1 has quit IRC21:37
*** jwagner_away is now known as jwagner21:39
*** krtaylor has joined #openstack-meeting-421:45
*** dims_ has quit IRC21:51
*** sdake has joined #openstack-meeting-421:56
*** dims has joined #openstack-meeting-421:57
*** bobh has quit IRC21:57
*** sdake_ has joined #openstack-meeting-421:59
*** SimonChung has joined #openstack-meeting-421:59
*** sdake has quit IRC22:00
*** sdake_ has quit IRC22:02
*** CheKoLyN has joined #openstack-meeting-422:02
*** angdraug has quit IRC22:04
*** baoli has joined #openstack-meeting-422:06
*** jwagner is now known as jwagner_away22:07
*** baoli has quit IRC22:11
*** woodard_ has joined #openstack-meeting-422:14
*** galstrom_zzz is now known as galstrom22:14
*** harshs has joined #openstack-meeting-422:15
*** woodard has quit IRC22:18
*** woodard_ has quit IRC22:19
*** Sukhdev has joined #openstack-meeting-422:19
*** julim_ has quit IRC22:20
*** banix has quit IRC22:29
*** SimonChung1 has joined #openstack-meeting-422:40
*** SimonChung has quit IRC22:40
*** AlanClark has quit IRC22:40
*** Sukhdev has quit IRC22:43
*** MarkAtwood has quit IRC22:54
*** galstrom is now known as galstrom_zzz22:55
*** dims has quit IRC23:00
*** dims has joined #openstack-meeting-423:01
*** Rockyg has quit IRC23:03
*** klamath_ has quit IRC23:04
*** dims_ has joined #openstack-meeting-423:04
*** dims has quit IRC23:07
*** SimonChung1 has quit IRC23:07
*** SimonChung has joined #openstack-meeting-423:07
*** SimonChung has quit IRC23:10
*** jckasper has quit IRC23:13
*** sigmavirus24 is now known as sigmavirus24_awa23:20
*** woodard has joined #openstack-meeting-423:23
*** cloudtrainme has quit IRC23:24
*** salv-orl_ has joined #openstack-meeting-423:28
*** salv-orlando has quit IRC23:30
*** SimonChung has joined #openstack-meeting-423:34
*** alex_didenko has quit IRC23:36
*** woodard has quit IRC23:42
*** blahRus has quit IRC23:43
*** jgjhgsonchn88523 has quit IRC23:46
*** salv-orl_ has quit IRC23:49
*** salv-orlando has joined #openstack-meeting-423:50
*** SimonChung1 has joined #openstack-meeting-423:51
*** SimonChung has quit IRC23:51
*** SimonChung has joined #openstack-meeting-423:52
*** SimonChung has quit IRC23:52
*** SimonChung1 has quit IRC23:52
*** SimonChung2 has joined #openstack-meeting-423:52
*** pmesserl_ has quit IRC23:56
*** Sukhdev has joined #openstack-meeting-423:58

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