Wednesday, 2016-07-27

*** rossella_s has joined #openstack-meeting-300:00
*** baoli has joined #openstack-meeting-300:00
*** pvaneck has quit IRC00:01
*** pvaneck has joined #openstack-meeting-300:04
*** sarob has joined #openstack-meeting-300:05
*** mickeys has joined #openstack-meeting-300:09
*** baoli has quit IRC00:11
*** baoli has joined #openstack-meeting-300:13
*** sdague has quit IRC00:16
*** dimtruck is now known as zz_dimtruck00:19
*** baoli has quit IRC00:23
*** zz_dimtruck is now known as dimtruck00:28
*** armax has quit IRC00:29
*** banix has quit IRC00:30
*** Swami has quit IRC00:31
*** armax has joined #openstack-meeting-300:34
*** bklei has quit IRC00:39
*** D9 has joined #openstack-meeting-300:39
*** bklei has joined #openstack-meeting-300:39
*** bklei has quit IRC00:44
*** sdake_ has quit IRC00:45
*** sdake has joined #openstack-meeting-300:47
*** tonytan4ever has joined #openstack-meeting-300:47
*** mtanin___ has quit IRC00:48
*** ddieterly has joined #openstack-meeting-300:49
*** hoangcx has joined #openstack-meeting-300:50
*** tonytan4ever has quit IRC00:53
*** jrist has quit IRC00:59
*** pvaneck has quit IRC01:01
*** sdake has quit IRC01:04
*** zhurong has joined #openstack-meeting-301:10
*** jrist has joined #openstack-meeting-301:11
*** neil_ has quit IRC01:14
*** toddjohn has joined #openstack-meeting-301:16
*** sarob has quit IRC01:16
*** mickeys has quit IRC01:17
*** sarob has joined #openstack-meeting-301:17
*** dimtruck is now known as zz_dimtruck01:19
*** calbers has quit IRC01:19
*** calbers has joined #openstack-meeting-301:19
*** ddieterly is now known as ddieterly[away]01:20
*** ddieterly[away] is now known as ddieterly01:20
*** sarob has quit IRC01:21
*** toddjohn has quit IRC01:28
*** toddjohn has joined #openstack-meeting-301:29
*** banix has joined #openstack-meeting-301:30
*** TaylorHuang has joined #openstack-meeting-301:31
*** toddjohn has quit IRC01:33
*** TaylorH has quit IRC01:34
*** calbers has quit IRC01:35
*** TaylorH has joined #openstack-meeting-301:35
*** TaylorHuang has quit IRC01:38
*** TaylorH has quit IRC01:39
*** woodster_ has quit IRC01:39
*** baoli has joined #openstack-meeting-301:41
*** zz_dimtruck is now known as dimtruck01:47
*** tonytan4ever has joined #openstack-meeting-301:49
*** calbers has joined #openstack-meeting-301:49
*** kenji-i has quit IRC01:52
*** uxdanielle has quit IRC01:52
*** tonytan4ever has quit IRC01:53
*** ddieterly has quit IRC01:57
*** mickeys has joined #openstack-meeting-302:00
*** revon has quit IRC02:00
*** mickeys has quit IRC02:03
*** mickeys has joined #openstack-meeting-302:04
*** coolsvap_ has joined #openstack-meeting-302:04
*** julim has joined #openstack-meeting-302:05
*** mickeys has quit IRC02:08
*** armax has quit IRC02:10
*** kenji-i has joined #openstack-meeting-302:11
*** sdake has joined #openstack-meeting-302:12
*** eliqiao has quit IRC02:12
*** eliqiao has joined #openstack-meeting-302:12
*** baoli has quit IRC02:17
*** salv-orl_ has quit IRC02:21
*** baoli has joined #openstack-meeting-302:32
*** yamahata has quit IRC02:34
*** iyamahat has quit IRC02:34
*** tonytan4ever has joined #openstack-meeting-302:35
*** baoli has quit IRC02:52
*** sdake has quit IRC02:53
*** ddieterly has joined #openstack-meeting-302:56
*** yamamoto_ has joined #openstack-meeting-303:05
*** ddieterly has quit IRC03:08
*** uxdanielle has joined #openstack-meeting-303:10
*** baoli has joined #openstack-meeting-303:10
*** abalutoiu_ has joined #openstack-meeting-303:12
*** sdake has joined #openstack-meeting-303:12
*** abalutoiu has quit IRC03:15
*** baoli has quit IRC03:17
*** salv-orlando has joined #openstack-meeting-303:22
*** RuiChen has joined #openstack-meeting-303:24
*** Liuqing has joined #openstack-meeting-303:25
*** salv-orlando has quit IRC03:28
*** eliqiao has quit IRC03:29
*** eliqiao has joined #openstack-meeting-303:31
*** banix has quit IRC03:40
*** calbers has quit IRC03:49
*** SridarK has joined #openstack-meeting-303:53
*** shwetaap has joined #openstack-meeting-303:55
*** calbers has joined #openstack-meeting-303:58
*** lpetrut has joined #openstack-meeting-303:59
*** dimtruck is now known as zz_dimtruck03:59
*** chandanc_ has joined #openstack-meeting-303:59
*** rossella_s has quit IRC03:59
SridarKHi FWaaS folks04:00
chandanc_hello04:00
*** padkrish has joined #openstack-meeting-304:00
*** yushiro has joined #openstack-meeting-304:00
*** rossella_s has joined #openstack-meeting-304:00
SridarKwe can get started - i see folks joining04:00
SridarK#startmeeting fwaas04:01
openstackMeeting started Wed Jul 27 04:01:13 2016 UTC and is due to finish in 60 minutes.  The chair is SridarK. Information about MeetBot at http://wiki.debian.org/MeetBot.04:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:01
*** openstack changes topic to " (Meeting topic: fwaas)"04:01
openstackThe meeting name has been set to 'fwaas'04:01
xgermano/04:01
yushiroHi all, o/04:01
SridarK#chair xgerman04:01
openstackCurrent chairs: SridarK xgerman04:01
padkrishhi all04:01
*** SarathMekala has joined #openstack-meeting-304:01
*** _SarathMekala_ has joined #openstack-meeting-304:01
SridarKok lets run thru the usual topics04:02
shwetaapHi04:02
SridarK#topic FWaaS v204:02
*** openstack changes topic to "FWaaS v2 (Meeting topic: fwaas)"04:02
_SarathMekala_hi all04:02
hoangcxhi04:02
SridarKon the patchsets, shwetaap: thx i saw that u uploaded a new patch on the extensions04:02
SridarKand yushiro: thanks for addressing some of the comments04:02
yushiroSridarK, you're welcome :)04:03
SridarKshwetaap: do u see more work on the patch in terms of UT ?04:03
shwetaapsure, thanks yushiro on fixing some of the comments.04:03
shwetaapi may add a few UTs for firewall_groups04:04
shwetaapthe rest seem ok04:04
SridarKshwetaap: ok04:04
SridarKI will look thru and post some comments too04:04
yushiroshwetaap, You're welcome.  I'll put some new comments on your patch.  would you check and fix it?04:04
SridarKmy sense is that we can target the first set of basic resources and attributes04:04
SridarKi will comment on gerrit and we can discuss there04:05
shwetaapyushiro: sure04:05
yushiroshwetaap, OK04:05
SridarKnext up is njohnston and myself on the db & plugin04:06
SridarKi have been working the db patch - i have some basic things working with the policy, tweaking out the policy - rule - position table04:06
SridarKi will push the patch up as soon as i finish my testing04:07
yushiroSridarK, I see. After that, I'll comment in your DB patch(I found some nit bugs)04:08
SridarKyushiro: ok great - much appreciated04:08
SridarKi will keep the plugin patch with the old rpc model04:09
SridarKas the first approach04:09
padkrishSridarK# Sounds good....once i see your patch, i will integrate with versioned object patch and test04:09
SridarKwe can refactor with versioned objects and the L3 Agent ext as the next step04:09
SridarKpadkrish: ok that is good - we can try to sync up to plan this a bit later in the week04:10
padkrishSridarK# Ok04:10
yushiropadkrish, I'll sync with you about the integration of our patches.04:10
SridarKOn the plugin, the old model had a PENDING state04:11
SridarKand after the Agent applied the rules and sent an ACK back - we would go to the final state04:11
padkrish#yushiro# absolutely...i am looking forward to your devstack plugin, which will help us all integrate04:11
SridarKi would like folks to think abt this and get some comments out04:11
SridarKperhaps with versioned objects - we dont need this04:12
SridarKi will reach out to u guys to clarify this bit04:12
yushiropadkrish, Ah, unfortunately, this is not devstack plugin but procedure how 2 integrate our patches..  Is it OK?04:12
padkrishyushiro# i see, that's still very good...04:13
SridarKyushiro: that is good too - all of us following a similar approch will be good04:13
xgerman+104:14
SridarKi think we will be in some craziness with the dependencies04:14
SridarKyushiro: padkrish: mfranc213_: pls go ahead with the agent side updates04:14
yushiroSridarK, Sure.  Last week, I attended virtual mid-cycle with SridarK , njohnston|PTO  and margaret04:15
yushiroSridarK, As you know :)04:15
SridarK:-)04:15
SridarKwe can get this as a separate topic04:15
yushiroSridarK, After that, I fosused on as follows:04:16
yushiro1. Review margaret patch first. I've already put some comments into her patch.04:16
yushiro2. Integrate our patches and try to pass  "GET".  Currently, I've just finished GET firewall_groups.04:17
yushiroI'll share this information into FWaaS members within today(Japan timezone).04:17
SridarKyushiro: great04:18
*** RuiChen has quit IRC04:18
SridarKcan u elaborate more on (2)04:18
SridarKhave u added some missing pieces ?04:18
yushiroSridarK, Yes. I've added some DB attributes.04:19
SridarKyushiro: ok cool04:19
yushiroSridarK, ex. "project_id", "public"...04:19
SridarKyushiro: ok04:19
SridarKi will have some of these missing pieces on the Rules, Policy and FW group resources also04:20
yushiroSridarK, So, let me confirm about DB.  we use 'public' instead of 'shared', don't you?04:20
SridarKyushiro: yes04:20
yushiroSridarK, Also, 'project_id' instead of 'tenant_id', don't you?04:20
SridarKyushiro: yes that is correct04:20
yushiroSridarK, OK, thank you.04:21
SridarKyushiro: just give me another day - and i will update the patch04:21
SridarKso u can use that04:21
xgermannice!04:21
padkrishSridarK# On my side, i have sent out couple of patches for versioned objects https://review.openstack.org/#/c/342476/2 and https://review.openstack.org/#/c/347092/04:22
SridarKpadkrish: yes thx04:23
yushiroSridarK, Sure.  I also changed a little with migration file , DB, plugin, versioned object,..  in order to pass golden route(GET).  I'll feedback it.04:23
SridarKyushiro: ok sounds good04:23
padkrishthey seem to have a circular dependency, so i am planning to split https://review.openstack.org/#/c/342476/2  into two...basically remove the notification driver portion from it04:23
SridarKyushiro: u can comment on the patch after i push it too04:23
yushiroSridarK, Sure. I'll do that :)04:24
SridarKpadkrish: yes saw ur email04:24
*** salv-orlando has joined #openstack-meeting-304:24
xgermanthe less circular dependencies we have the better. That’s the reason for neutron-lib (cut back on those dependencies)04:25
SridarKxgerman: +104:25
padkrishxgerman# agree, but the resources are embedded in Neutron as it stands today...04:25
SridarKpadkrish: will look thru this04:25
padkrishSo, any suggestions on that?04:25
SridarKand we can look for the easiest way fwd04:26
xgermanI think proceed as is and hope they merge it...04:26
*** asettle has joined #openstack-meeting-304:26
padkrishxgerman# ok :)04:26
xgermanthat’s the best we can do — and if we need to change we do so04:27
padkrishxgerman# sure04:27
SridarKpadkrish: yes this is can be quite tricky04:28
SridarKbut it is not very clear on how to get past this04:28
*** salv-orlando has quit IRC04:28
padkrishSridarK# unless, we make the resource registration generic instead of hard-coding, i also need to think through this....if we do, we also may need to modify existing consumer (QoS) to make use of it04:29
*** lpetrut has quit IRC04:30
SridarKpadkrish: yes, since QoS is part of neutron - things are good04:30
padkrishSridarK# yes04:30
*** yamamoto_ has quit IRC04:31
SridarKlets discuss this more along with xgerman & mfranc213_ since Nate is out this week04:31
*** asettle has quit IRC04:31
SridarKok lets move on to the next piece04:31
xgerman+104:31
SridarKchandanc_: & SarathMekala: how do things look on the driver side04:32
*** vishwanathj has quit IRC04:32
SarathMekalaWe are done with Security Group changes04:32
SarathMekalathings seem to be good04:32
SarathMekalabut there are certain issues that need discussion..04:32
SridarKSarathMekala: ok great - which change is this ?04:32
SridarKso both can coexist ?04:33
chandanc_the changes are needed on the iptables_manager, in the neutron code\04:33
SarathMekalacontention between SG and FwaaS drivers got solved... this solution needs some review from the team04:34
chandanc_we have introduced a common chain and then component level chains for fw and SG04:34
SridarKok nice04:34
xgermanneat!04:34
chandanc_with the changes the IPtables configuration is now not been overwritten by components04:34
SridarKif u can review with mickeys and then reach out ot a broader audience04:34
SridarK*to a04:34
*** Poornima has joined #openstack-meeting-304:35
SridarKbut this is great04:35
SarathMekalasure..04:35
chandanc_here is an example output   http://paste.openstack.org/show/542471/04:35
SridarKand an important piece to have in place04:35
SarathMekalaSridarK# there are a few general concerns04:35
SarathMekalafor ex:  we need to change neutron code.. is it ok?04:36
SridarKSarathMekala: yes u will need to get the review out04:36
SarathMekalaip_firewall and iptable_manger are from neutron04:36
xgermanSridarK +104:36
xgermanI think we are running up against their deadline soon04:37
SridarKu can reference the before and after from paste in the review comments04:37
SarathMekalasure will do that... there are a few more queries, will send across a mail after this meeting04:37
SridarKi echo xgerman: - u will need to get some review time with the neutron folks04:37
SridarKso sooner the better04:37
yushiroSarathMekala, BTW, it there any update about ordering b/w firewall_groups?04:38
SarathMekalasure.. we are in a shape to post a review04:38
SridarKexcellent04:38
xgerman+104:38
yushiro+104:38
SarathMekalaordering is still open for now at the same level04:38
SridarKthere will be some minor updates to iptables rules for L3 as well - i will run it by both of u04:39
chandanc_sure04:39
SarathMekalaxgerman suggested to throw an error.. so we can consider that04:39
SridarKbut this is quite simple compared to what u guys are doing for L204:39
SarathMekalasure..04:40
SarathMekalaSridar can we sync up after this meeting04:40
SridarKSarathMekala: sure04:40
yushiroSarathMekala, I see.  Is it discussing in google doc now?04:41
SarathMekalayushiro# the doc needs to be updated04:41
*** jtomasek has quit IRC04:41
SarathMekalawe got busy sorting out some issues04:42
SarathMekalawill do it this week04:42
yushiroSarathMekala, OK. great work.  I'll check in next week.  Thank you.04:42
SridarKSarathMekala: understand no worries04:42
SridarKanything else on driver pieces04:43
chandanc_nothing much , we need to have some discussion.04:43
chandanc_we will have the patch out04:44
SridarKok sounds good04:44
SarathMekalacode seems to be in a ok shape04:44
SridarKok04:44
SarathMekalaneed to see how the review goes04:44
SridarKlets move on04:45
SridarK#topic L3 Agent04:45
*** openstack changes topic to "L3 Agent (Meeting topic: fwaas)"04:45
SridarKmfranc213_: has a review out:04:45
SridarK#link https://review.openstack.org/#/c/337699/04:45
SridarKwe clarified that this can be step 104:46
SridarKand yushiro: has a patch out04:46
SridarK#link https://review.openstack.org/#/c/34137404:46
SridarKthis could be step204:46
yushiroSridarK, yes.04:46
SridarKmfranc213_: is not here - but we can continue the review04:47
SridarKyushiro: thx for getting started04:47
SridarK#topic virtual coding sprint04:47
*** openstack changes topic to "virtual coding sprint (Meeting topic: fwaas)"04:47
SridarKwe met on thu & fri of last week (njohnston, mfranc213_ , padkrish yushiro & SridarK )04:48
SridarKwe spent some time to discuss and clear things up on any questions so we can focus04:48
SridarKand get answers quickly04:48
SarathMekalaSorry guys.. I fell sick and could not join the discussion04:49
SridarKperhaps we can target allocating couple of hours on couple of days every week04:49
SridarKSarathMekala: no worries - we were mainly on the plugin - agent side of things04:49
SridarKif we can block some time to have a quick discussion and clarify issues, do reviews etc - could be useful to move quickly04:50
SridarKanyways - something folks can think abt and see if it is worth pursuing - we can also do this on demand04:50
SridarK#topic Open Discussion04:51
*** openstack changes topic to "Open Discussion (Meeting topic: fwaas)"04:51
SridarKother things folks want to bring up ?04:52
SridarKin general we are tight on time but i think the dependencies are coming together - a focussed push will get us thru the finish line04:52
xgerman#link http://graham.hayes.ie/posts/equal-opportunities-for-all-openstack-projects/04:52
xgerman^^ that’s interesting in case we spin out ;-)04:53
xgermanSridarK +104:53
SridarKxgerman: how relevant :-)04:53
SridarKWe also need to keep an eye on the Client patch sets needed04:55
SridarKThats all I had, if nothing else we can close out04:55
yushiroSridarK, I'll follow CLI's patch with njohnston.04:55
SridarKyushiro: ok great - he will be back next week04:56
SridarKok then thanks all for attending and all the updates, have a great and productive week04:56
yushiroTO All, if you'd like to reach out Japanese core-reviewer, please let me ask.  I can reach out them more easily.04:56
SridarKyushiro: that is very useful04:56
xgerman+104:57
yushiroBecause I'm on the same timezone :)04:57
SridarKthx04:57
SridarK#endmeeting04:57
*** openstack changes topic to " (Meeting topic: ops_guide)"04:57
_SarathMekala_bye all o/04:57
openstackMeeting ended Wed Jul 27 04:57:20 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/fwaas/2016/fwaas.2016-07-27-04.01.html04:57
xgermano/04:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/fwaas/2016/fwaas.2016-07-27-04.01.txt04:57
openstackLog:            http://eavesdrop.openstack.org/meetings/fwaas/2016/fwaas.2016-07-27-04.01.log.html04:57
yushirobye bye04:57
*** numans has joined #openstack-meeting-304:57
shwetaapbye, Thanks!04:57
chandanc_bye04:57
*** Poornima has quit IRC04:57
padkrishbye04:57
*** shwetaap has left #openstack-meeting-304:57
*** yushiro has left #openstack-meeting-304:58
*** yamahata has joined #openstack-meeting-305:00
*** flwang1 has quit IRC05:03
*** SarathMekala_ has joined #openstack-meeting-305:05
*** _SarathMekala_ has quit IRC05:07
*** padkrish has quit IRC05:09
*** anil_rao has joined #openstack-meeting-305:09
*** anilvenkata has joined #openstack-meeting-305:11
*** uxdanielle has quit IRC05:13
*** salv-orlando has joined #openstack-meeting-305:14
*** soichi has joined #openstack-meeting-305:20
*** yamamot__ has joined #openstack-meeting-305:22
*** anilvenkata has quit IRC05:25
*** beagles has quit IRC05:26
*** numans has quit IRC05:27
*** iyamahat has joined #openstack-meeting-305:29
*** kaz has joined #openstack-meeting-305:29
anil_rao#startmeeting taas05:30
openstackMeeting started Wed Jul 27 05:30:15 2016 UTC and is due to finish in 60 minutes.  The chair is anil_rao. Information about MeetBot at http://wiki.debian.org/MeetBot.05:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:30
*** openstack changes topic to " (Meeting topic: taas)"05:30
openstackThe meeting name has been set to 'taas'05:30
yamamot__hi05:30
anil_raoHello05:30
kazhi05:30
soichihi05:30
anil_rao#topic Performance measurement05:30
*** openstack changes topic to "Performance measurement (Meeting topic: taas)"05:30
kazlink: http://lists.openstack.org/pipermail/openstack-dev/attachments/20160727/04c7bcbc/attachment-0001.pdf05:31
anil_raoThanks Kaz for providing the new results.05:31
kazThere is a mistake in the graph I showed last week IRC meeting.05:31
*** muawiakhan has joined #openstack-meeting-305:31
kazThe attached file is a collected edition.05:31
anil_raoI was reading on a blog that OVS is able to do around 260K pps05:32
anil_raoApparently this is a a new version with lots of perf enhancements.05:33
soichicould you share URL of the blog?05:33
anil_raosure. give me a minute05:33
*** pgadiya has joined #openstack-meeting-305:34
anil_rao#link http://blog.ipspace.net/2014/11/open-vswitch-performance-revisited.html05:34
yamamot__the vhost-net thread was sharing the cpu with something cpu-consuming?05:34
soichianil_rao: thiank you05:35
*** anil_rao_ has joined #openstack-meeting-305:35
*** anil_rao_ has quit IRC05:36
kazCPU pin down was enabled05:36
*** anil_rao_ has joined #openstack-meeting-305:37
yamamot__kaz: so the cpu was dedicated to the vhost-net instance?05:37
*** anil_rao_ has quit IRC05:38
*** anil_rao has quit IRC05:38
*** numans has joined #openstack-meeting-305:39
*** anil_rao has joined #openstack-meeting-305:39
kazyamamot__: vhost-net is running on host OS, so it was not dedicated, I think.05:39
yamamot__you mean vcpu threads are pinned?05:41
kazyamamot__: yes05:42
yamamot__do you have a record of which cpu was running which thread?05:42
kazNo I do not.05:43
anil_raoIf my understanding of the graph is correct it appears that when mirroring is not enabled, iperf is able to drive 95K pps.05:44
anil_raoWhen mirroring is enabled you get 70K pps of production traffic + 70K pps of mirrored traffic.05:45
kazanil_rao: yes05:45
anil_raoso when mirroring if off the 95K limit is either from iperf of the VMs themselves and not OVS. is this correct?05:46
yamamot__the screenshot in p4 is for which case?05:46
kazyamamot__: this is for mirror is enabled case.05:47
kazanil_raw: yes, I guess05:48
anil_raoI am curious to know why the non mirrored case tops off at 95K pps. Was vhost-net consuming 100% cpu in that case too.05:49
anil_raoI was logged out of the IRC chat a few min back. Did the blog link i sent out reach you all?05:51
kazwe know that vhost-net cosume 100% cpu , but we do not know the reason.05:52
soichianil_rao: okay05:52
anil_raosoichi: Thanks05:52
anil_raoThis is an interesting result. I will need some time to fully understand the behavior.05:54
soichiwe will try to investigate05:54
anil_raoI mean, when mirroring is enabled we are essentially seeing 140k pps (70K prod + 70K mirrored).05:55
soichiyes05:55
anil_raoSo it seems to indicate that the 95K non mirrored limit is perhaps a limit with the dest VM not being able to receive faster than that rate.05:56
*** coolsvap_ is now known as coolsvap05:56
reedipHi sorry, I forgot that today we had a meeting05:56
anil_raoHi Reedip05:57
soichireedip: hi05:57
kazhi05:57
reedipgoing through the meeting logs...05:57
anil_raoOur lab is down because of an AC upgrade. So I will only have result for you all next week.05:58
anil_raoany more on this topic, otherwise we can move to the next one on the agenda.05:59
muawiakhanhi06:00
kazI guess the limit of 95K is a limit of source VM's CPU bound of vhost-net06:00
*** nkrinner_afk is now known as nkrinner06:02
*** calbers has quit IRC06:02
soichiwe will make additional experiments and report the result06:02
anil_raosoichi: Thanks06:02
soichilet's go no next topic06:03
anil_rao#topic Design of traffic isolation by using flow based tunneling (cont.)06:03
*** openstack changes topic to "Design of traffic isolation by using flow based tunneling (cont.) (Meeting topic: taas)"06:03
soichiKaz found that Netron code was updated06:04
anil_raosoichi: In what manner?06:04
kazI found that it is not able to use ":taas" in a neutron database because a new version of neutron has a strict type check of IP address.06:05
*** hoangcx has left #openstack-meeting-306:06
kazSo we need to consider a new method of discovering IP address.06:06
soichiyes, we need to revise our proposal06:07
soichiwe will submit revised one when we find a good idea.06:08
yamamot__what's wrong with adding a column?06:09
soichiyamamot__: it shoud be an idea, tahnk you06:09
soichimove to next topic?06:11
anil_raosoichi,kaz: I was wondering if we can return the right IP when the destination replies to the broadcast packet(s).06:11
*** Liuqing has quit IRC06:12
kazbroadcast packets need to send to appropriate tunnel.06:13
*** calbers has joined #openstack-meeting-306:13
*** Liuqing has joined #openstack-meeting-306:14
soichiit means send to tunnels for production trafiic06:15
anil_raofor taas we will always send via TAAS_SEND_FLOOD table, right?06:15
anil_raosoichi,kaz: I will study this some more and we can discuss options in a later meeting.06:16
*** sdake has quit IRC06:16
kazbefore mac learning, we send via TAAS_SEND_FLOOD table06:16
kazafter mac lerning we will send via TAAS_SEND_UCAST table06:17
anil_raokaz: In today's exercise we are not really performing mac learning. Instead, we just learn about the location of the destination of a tap service instance. I am assuming that the same will be true with your flow based tunneling.06:19
kazthank you for your comment. I would like to discuss next week.06:21
anil_raosure. Let's move to the next topic.06:21
anil_rao#topic Can not capture the packet, if the two VM on the same host06:21
*** openstack changes topic to "Can not capture the packet, if the two VM on the same host (Meeting topic: taas)"06:21
anil_rao#link Media:ingress_packet-20160720-r1.png06:22
*** anilvenkata has joined #openstack-meeting-306:22
anil_raoThanks for the detailed description of the problem. I am examining this issue...looks like the port vlan is not visible to the OVS flow table.06:24
anil_raoI have reproduced the issue on my setup. I'll report back when I have a better handle on this.06:25
kazanil_rao: thank you06:26
anil_raoWhat I did notice is that traffic coming from outside the host gets properly tagged by the flows in OVS.06:26
*** abalutoiu_ has quit IRC06:26
anil_raoso this only affects ingress monitoring when the source is on the same host.06:27
kazanil_rao: that's right06:28
anil_rao#topic  Open Discussion06:28
*** openstack changes topic to "Open Discussion (Meeting topic: taas)"06:28
soichiLet's vote to TaaS and related presentations.06:28
*** salv-orl_ has joined #openstack-meeting-306:28
soichiI found Vinay's presentation: "Tapping in NFV cloud : A real world showcase by Swisscom, Ericsson and IXIA." in the Telecom/NFV Operations track.06:28
anil_rao+106:29
anil_raowe have run out of time. Next week then?06:30
anil_rao#endmeeting06:30
*** openstack changes topic to " (Meeting topic: ops_guide)"06:30
openstackMeeting ended Wed Jul 27 06:30:57 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-07-27-05.30.html06:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-07-27-05.30.txt06:31
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-07-27-05.30.log.html06:31
soichibye06:31
anil_raoBye06:31
kazthanks, bye06:31
*** anil_rao has quit IRC06:31
*** salv-orlando has quit IRC06:31
*** soichi has left #openstack-meeting-306:31
*** kaz has quit IRC06:31
*** amitkqed has joined #openstack-meeting-306:35
*** amitkqed has quit IRC06:36
*** amitkqed has joined #openstack-meeting-306:36
*** amitkqed has quit IRC06:36
*** amitkqed has joined #openstack-meeting-306:37
*** asettle has joined #openstack-meeting-306:39
*** asettle has quit IRC06:43
*** abalutoiu has joined #openstack-meeting-306:45
*** sdake has joined #openstack-meeting-306:45
*** ameade has quit IRC06:49
*** etoews has quit IRC06:49
*** derekjhyang has quit IRC06:49
*** jraim has quit IRC06:49
*** zhiyan has quit IRC06:49
*** briancurtin has quit IRC06:49
*** amit213 has quit IRC06:50
*** davidmichaelkarr has quit IRC06:50
*** etoews has joined #openstack-meeting-306:50
*** derekjhyang has joined #openstack-meeting-306:52
*** amit213 has joined #openstack-meeting-306:52
*** zhiyan has joined #openstack-meeting-306:52
*** ameade has joined #openstack-meeting-306:52
*** jraim has joined #openstack-meeting-306:52
*** briancurtin has joined #openstack-meeting-306:52
*** davidmichaelkarr has joined #openstack-meeting-306:52
*** nkrinner has quit IRC06:54
*** nkrinner has joined #openstack-meeting-306:57
*** egallen has joined #openstack-meeting-307:00
*** sdake has quit IRC07:01
*** nkrinner has quit IRC07:05
*** calbers has quit IRC07:11
*** mickeys has joined #openstack-meeting-307:16
*** nkrinner has joined #openstack-meeting-307:18
*** amotoki has joined #openstack-meeting-307:19
*** asettle has joined #openstack-meeting-307:21
*** vdrok has quit IRC07:22
*** vdrok has joined #openstack-meeting-307:23
*** salv-orlando has joined #openstack-meeting-307:25
*** mickeys has quit IRC07:25
*** salv-orl_ has quit IRC07:25
*** asettle has quit IRC07:26
*** mickeys has joined #openstack-meeting-307:26
*** calbers has joined #openstack-meeting-307:26
*** kzaitsev_mb has joined #openstack-meeting-307:29
*** andreas_s has joined #openstack-meeting-307:29
*** mickeys has quit IRC07:31
*** sc68cal has quit IRC07:33
*** sc68cal has joined #openstack-meeting-307:33
*** jlanoux has joined #openstack-meeting-307:34
*** isq_ has quit IRC07:34
*** isq_ has joined #openstack-meeting-307:34
*** ajmiller_ has quit IRC07:35
*** ajmiller_ has joined #openstack-meeting-307:35
*** mtreinish has quit IRC07:36
*** mtreinish has joined #openstack-meeting-307:36
*** tovchinnikova has joined #openstack-meeting-307:38
*** iyamahat has quit IRC07:41
*** neiljerram has joined #openstack-meeting-307:42
*** jtomasek has joined #openstack-meeting-307:50
*** stendulker has joined #openstack-meeting-307:53
*** kzaitsev_mb has quit IRC07:55
*** tonytan4ever has quit IRC07:58
*** tonytan4ever has joined #openstack-meeting-307:59
*** rossella_s has quit IRC08:00
*** rossella_s has joined #openstack-meeting-308:00
*** ihrachys has joined #openstack-meeting-308:09
*** salv-orlando has quit IRC08:10
*** tonytan4ever has quit IRC08:11
*** salv-orlando has joined #openstack-meeting-308:12
*** kzaitsev_mb has joined #openstack-meeting-308:12
*** egallen has quit IRC08:16
*** jlanoux has quit IRC08:16
*** jlanoux has joined #openstack-meeting-308:16
*** RuiChen has joined #openstack-meeting-308:17
*** asettle has joined #openstack-meeting-308:17
*** salv-orlando has quit IRC08:17
*** toddjohn has joined #openstack-meeting-308:17
*** asettle has quit IRC08:21
*** toddjohn has quit IRC08:21
*** qwebirc17176 has joined #openstack-meeting-308:26
*** qwebirc17176 has left #openstack-meeting-308:26
*** kzaitsev_mb has quit IRC08:26
*** egallen has joined #openstack-meeting-308:37
*** kzaitsev_mb has joined #openstack-meeting-308:47
*** SarathMekala has quit IRC08:56
*** SarathMekala_ has quit IRC08:56
*** tonytan4ever has joined #openstack-meeting-309:01
*** tonytan4ever has quit IRC09:05
*** asettle has joined #openstack-meeting-309:13
*** neil_ has joined #openstack-meeting-309:15
*** neiljerram has quit IRC09:16
*** kzaitsev_mb has quit IRC09:16
*** asettle has quit IRC09:18
*** sambetts|afk is now known as sambetts09:22
*** calbers has quit IRC09:27
*** asettle has joined #openstack-meeting-309:31
*** dansmith has quit IRC09:33
*** dansmith has joined #openstack-meeting-309:35
*** dansmith is now known as Guest4106909:35
*** calbers has joined #openstack-meeting-309:36
*** asettle has quit IRC09:36
*** yushiro_afk has joined #openstack-meeting-309:40
*** muawiakhan has quit IRC09:41
*** muawiakhan has joined #openstack-meeting-309:41
*** ccamacho has joined #openstack-meeting-309:44
*** muawiakhan has quit IRC09:45
*** mbound has joined #openstack-meeting-309:46
*** iyamahat has joined #openstack-meeting-309:49
*** tangchen has quit IRC09:50
*** tangchen_ has quit IRC09:50
*** muawiakhan has joined #openstack-meeting-310:00
*** zhurong has quit IRC10:01
*** stanzgy has joined #openstack-meeting-310:02
*** Liuqing has quit IRC10:03
*** tangchen_ has joined #openstack-meeting-310:04
*** tangchen has joined #openstack-meeting-310:04
*** yushiro_afk has quit IRC10:06
*** muawiakhan has quit IRC10:08
*** tovchinnikova has quit IRC10:21
*** ociuhandu has joined #openstack-meeting-310:30
*** yamamot__ has quit IRC10:31
*** egallen has quit IRC10:44
*** iyamahat has quit IRC10:44
*** yamahata has quit IRC10:48
*** egallen has joined #openstack-meeting-310:51
*** yuikotakadamori has joined #openstack-meeting-311:00
*** rtheis has joined #openstack-meeting-311:03
*** neiljerram has joined #openstack-meeting-311:05
*** chandanc_ has quit IRC11:06
*** neil_ has quit IRC11:07
*** stendulker has quit IRC11:09
*** salv-orlando has joined #openstack-meeting-311:09
*** stanzgy has quit IRC11:13
*** yamamoto has joined #openstack-meeting-311:13
*** yamamoto_ has joined #openstack-meeting-311:14
*** yamamoto has quit IRC11:18
*** muawiakhan has joined #openstack-meeting-311:26
*** sdague has joined #openstack-meeting-311:30
*** ociuhandu has quit IRC11:33
*** ociuhandu has joined #openstack-meeting-311:35
*** sergio_nubeliu has joined #openstack-meeting-311:45
*** yamamoto_ has quit IRC11:46
*** bogdando has joined #openstack-meeting-311:46
*** egallen has quit IRC11:53
*** egallen has joined #openstack-meeting-311:54
*** rossella_s has quit IRC11:59
*** asettle has joined #openstack-meeting-311:59
*** mionkin has quit IRC12:00
*** rossella_s has joined #openstack-meeting-312:00
*** yamamoto has joined #openstack-meeting-312:07
*** andymaier has joined #openstack-meeting-312:12
*** tonytan4ever has joined #openstack-meeting-312:17
*** ddieterly has joined #openstack-meeting-312:19
*** tonytan4ever has quit IRC12:22
*** ddieterly has quit IRC12:22
*** claudiub has joined #openstack-meeting-312:22
*** sdake has joined #openstack-meeting-312:23
*** yamamoto has quit IRC12:23
*** yuikotakadamori has quit IRC12:27
*** yamamoto has joined #openstack-meeting-312:30
*** calbers has quit IRC12:32
*** egallen has quit IRC12:32
*** yamamoto has quit IRC12:33
*** egallen has joined #openstack-meeting-312:33
*** beagles has joined #openstack-meeting-312:35
*** tovchinnikova has joined #openstack-meeting-312:37
*** ddieterly has joined #openstack-meeting-312:39
*** claudiub|2 has joined #openstack-meeting-312:40
*** calbers has joined #openstack-meeting-312:40
*** vishwanathj has joined #openstack-meeting-312:42
*** claudiub has quit IRC12:43
*** egallen has quit IRC12:44
*** ddieterly has quit IRC12:44
*** ccamacho is now known as ccamacho|hungry12:45
*** c64cosmin has joined #openstack-meeting-312:46
*** egallen has joined #openstack-meeting-312:49
*** neiljerram has quit IRC12:49
*** baoli has joined #openstack-meeting-312:49
*** woodster_ has joined #openstack-meeting-312:49
*** baoli_ has joined #openstack-meeting-312:50
*** yamamoto has joined #openstack-meeting-312:52
*** baoli has quit IRC12:55
*** pt_15 has joined #openstack-meeting-312:56
*** sagar_nikam has joined #openstack-meeting-312:59
claudiub|2#startmeeting hyper-v13:00
openstackMeeting started Wed Jul 27 13:00:21 2016 UTC and is due to finish in 60 minutes.  The chair is claudiub|2. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: hyper-v)"13:00
openstackThe meeting name has been set to 'hyper_v'13:00
sagar_nikamHi13:00
claudiub|2damn, I have a bad nickname13:00
claudiub|2hello. :)13:00
sagar_nikamhow was the mid cycle meetup ?13:01
claudiub|2well, tirering. :)13:01
claudiub|2we'll get to the details shortly. :)13:01
*** kvinod has joined #openstack-meeting-313:02
sagar_nikamok13:02
claudiub|2anyone else joining us today?13:02
claudiub|2lpetrut won't be with us today, as he's on vacation13:02
claudiub|2anyways, let's get started13:02
claudiub|2#topic os-brick status13:02
*** openstack changes topic to "os-brick status (Meeting topic: hyper-v)"13:02
claudiub|2sooo, we have a voting CI on os-brick13:03
claudiub|2yeay. :)13:03
sagar_nikamgood ...13:03
claudiub|2buut, currently, it only tests iscsi and smb. fibre channel will be added soon, probably by next week.13:03
*** atuvenie_ has joined #openstack-meeting-313:03
atuvenie_hi guys!13:03
claudiub|2lpetrut has worked diligently on it. :)13:03
claudiub|2atuvenie_: hi. :)13:04
abalutoiuhello guys13:04
sagar_nikamthanks lpetrut:13:04
*** itoader has joined #openstack-meeting-313:04
itoaderhi13:04
claudiub|2for now, I'll bug hemna and smcginnis to review the smb patch on os-brick for now.13:04
sagar_nikamhi atuvenie_: abalutoiu:13:05
sagar_nikamok13:05
claudiub|2that's mergeable, and they shouldn't have any more complains regarding ci for it13:05
sagar_nikami will also try to get hemna's review13:05
claudiub|2sagar_nikam: cool, thanks. :)13:05
claudiub|2#topic designate status13:05
*** openstack changes topic to "designate status (Meeting topic: hyper-v)"13:05
claudiub|2abalutoiu: the patch didn't merge yet. abalutoiu has been addressing comments13:06
*** Liuqing has joined #openstack-meeting-313:06
*** sonu has joined #openstack-meeting-313:06
claudiub|2hopefully it'll get merged soon.13:06
*** coolsvap is now known as coolsvap_13:07
claudiub|2#topic shielded VMs13:07
*** openstack changes topic to "shielded VMs (Meeting topic: hyper-v)"13:07
claudiub|2sooo, we've said this in the past meetings: Hyper-V 2016 comes with a new feature called shielded vms13:08
claudiub|2it's a pretty neat feature, the instance is fully encrypted and safe13:08
claudiub|2it is merged at the moment in compute-hyperv13:08
sagar_nikamplanned for "o" ? upstream13:09
sagar_nikamBP approved ?13:09
claudiub|2if you guys are planning to use it, that would be great. :)13:09
sagar_nikamwe will try it ....13:09
sagar_nikamnice feature to have13:09
claudiub|2sagar_nikam: the blueprint was approved in the past, but it wasn't approved in newton, since there were some changes in how shielded vms were implemented, so we had to rewrite some parts of the spec.13:10
sagar_nikamok13:10
claudiub|2itoader: can you share some links on this topic?13:11
claudiub|2on how to use them / how to create the env for it?13:11
itoaderHere is explained the concept and how to do the setup https://cloudbase.it/hyperv-shielded-vms-part-1/13:11
itoaderAnd this is the link on shielded vms in openstack https://cloudbase.it/hyper-v-shielded-vms-part-2/13:12
claudiub|2cool, thanks. :)13:12
itoaderI consider that everything needed it's explained in the blog posts, but if you have any questions, I'll gladly answer them :)13:13
sagar_nikamwe will check13:13
sagar_nikamwas  reading the blog now... sounds very intresting13:13
*** bklei has joined #openstack-meeting-313:14
claudiub|2cool, moving on. :)13:14
claudiub|2#topic OpenStack Summit presentations13:14
*** openstack changes topic to "OpenStack Summit presentations (Meeting topic: hyper-v)"13:14
sonuclaudiub: Can you give reference to use cases of using shielded vms with openstack?13:14
claudiub|2soo, just a short topic, the voting for presentations in barcelona are open.13:15
claudiub|2#link https://www.openstack.org/summit/barcelona-2016/vote-for-speakers/presentation/1646613:15
claudiub|2sonu: just a sec.13:15
sonuIs it Telco use case.13:15
claudiub|2soo, there are a few presentations regarding windows and hyper-v that would be nice to have them there. for that, they need voting.13:16
claudiub|2unfortunately, the vote-for-presentations link is a bit... bad, and I cannot link the exact presentations directly13:17
sagar_nikamok13:17
*** yamamoto has quit IRC13:17
claudiub|2but, a quick seach for Alessandro, Samfira, Vladu, and Sonu will reveal those presentations. :)13:18
*** matrohon has joined #openstack-meeting-313:18
claudiub|2so, if you could, please vote on those presentations. :)13:19
sagar_nikamsure13:19
claudiub|2sonu: ok, so now answering your question: the usecase is whenever security is a huge concern13:20
claudiub|2sonu: and the VMs and their data needs to be protected13:20
sonuI got my answer Claudiu Thanks13:20
claudiub|2e.g.: vms related to banks, financial transactions, personal data / info, etc.13:20
sonuYes13:20
claudiub|2k13:21
claudiub|2#topic nova midcycle meeting status13:21
*** openstack changes topic to "nova midcycle meeting status (Meeting topic: hyper-v)"13:21
claudiub|2ok, so this is going to take a while13:21
claudiub|2it'll be hard to compress 3 days worth of discussions into 35 mins.13:22
sagar_nikamok13:22
claudiub|2for a comprehensive view on the topics discussed at the midcycle, there's an etherpad13:23
claudiub|2#link https://etherpad.openstack.org/p/nova-newton-midcycle13:23
sagar_nikamhow was the discussion on clusterdriver13:23
*** pgadiya has quit IRC13:23
claudiub|2soo, on the cluster driver, the nova folks reaaaallly don't like the fact that failover migration can occur without nova's consent13:24
claudiub|2they say that ideally, the hyper-v cluster driver should call nova's api to actually do the failover13:24
sagar_nikamoh ....13:25
sagar_nikamdriverf calling api ?13:25
claudiub|2so that the claims, affinity, and other scheduling rules will be applied to the failover13:25
sagar_nikamdriver calling api ?13:25
claudiub|2yeah, don't like it either. :)13:25
*** cleong has joined #openstack-meeting-313:26
claudiub|2but the thing is, the whole scheduler / claiming / placement logic is being heavely refactored.13:26
claudiub|2right now, the claims are being made locally, on each compute-node13:26
claudiub|2and for now, the claims are correct with the cluster driver13:26
claudiub|2but all the claims and all its logic are going to be moved to the scheduler13:27
*** egallen has left #openstack-meeting-313:27
claudiub|2so, unless we do the failover "via the api" as they say, the resource claims won't be correct when a failover occurs.13:28
*** ccamacho|hungry is now known as ccamacho13:28
claudiub|2right now, I'm thinking how we can manually do the failover...13:28
sagar_nikambut ... driver calling api ... may not be good13:28
claudiub|2so, there's a field on the MSCluster_Resource object, that says how many times can it failover. wondering if we can set it to 0, detect whenever a failover needs to happen, and then call the api for it13:29
claudiub|2that's going to require some experiments.13:30
sagar_nikamyou mean nova driver detects when the failover has to happen ?13:30
claudiub|2yep13:31
atuvenie_claudiub|2 but: but that kind of defeats the purpose of failover13:31
claudiub|2so, unless we can do something like this, they won't say yes to the spec.13:31
claudiub|2atuvenie_: i know13:31
*** david-lyle_ has joined #openstack-meeting-313:31
*** david-lyle_ has quit IRC13:31
claudiub|2atuvenie_: it is going to slow the failover a lot. :)13:31
sagar_nikamhow will hardware failures on another node be detected ?13:31
*** mionkin has joined #openstack-meeting-313:31
atuvenie_claudiub|2: also, if we set that field to 0, it will not failover to another node ever. That means, how many times the vm can be moved around13:32
atuvenie_claudiub|2: that field I mean13:32
sagar_nikami think setting the field to 0 defeats the purpose of HA13:32
claudiub|2sagar_nikam: so, cluster resources are available at the cluster level. the cluster service detects whenever a failover needs to occur and does it. at the moment, in the compute-hyperv we have a wmi listener, which detects whenever a cluster resource changes its host.13:33
claudiub|2atuvenie_: i know, that's the point. basically to disable the automatic hyper-v failover, so we can attempt to do it manually.13:34
sagar_nikamand where is the wmi listener running ?13:34
*** david-lyle has quit IRC13:34
*** eliqiao has quit IRC13:34
claudiub|2sagar_nikam: on all nodes. they all listen to the event "when a cluster resource changes the its host to me"13:34
sagar_nikamdoing it manually can mean the VM can get powered off... which may not be a good solution13:34
*** ralonsoh has joined #openstack-meeting-313:34
sagar_nikamoh...13:34
atuvenie_atuvenie_: yeah, wait, if that value is 0 and the system needs triggers a failover, then the vm will be in error state13:35
atuvenie_claudiub|2: so you mean we should detect this and move it manually then?13:35
sagar_nikamyou mean nova-compute running on all the nodes in the cluster will listen to this wmi listener ?13:35
claudiub|2atuvenie_: pretty much, yeah.13:36
atuvenie_claudiub|2: error state in hyperv, not in nova I mean13:36
claudiub|2atuvenie_: not sure it is going to be explicitly in error state13:36
atuvenie_claudiub|2: then how is this different than a cold migration? I don't even know if we can recover it from that state13:36
claudiub|2we'll have to see what exactly happens if failover count is 013:37
atuvenie_claudiub|2: I think we can actually, but what about hardware failure?13:37
claudiub|2atuvenie_: if there's a hw failure, the vm will be in off state anyways13:37
*** yamamoto has joined #openstack-meeting-313:37
atuvenie_claudiub|2: no it will not13:37
sagar_nikamagree with atuvenie_: we need to handle hardware failures13:38
atuvenie_claudiub|2: it will be restarted on another node pretty fast13:38
claudiub|2the hyper-v cluster documentation says that it will not guarantee that the failover vms will have the same state as before failover13:38
atuvenie_claudiub|2: from a saved state13:38
sagar_nikamcurrently ... the mscluster handles it13:38
atuvenie_claudiub|2: it's not the exact same state, but pretty close, and certainly not from off state13:38
atuvenie_claudiub|2: it's the closest saved state the hyper-v cluster has13:39
claudiub|2if there is such a saved state, we can restore that state on another host then.13:39
atuvenie_claudiub|2: also, if we do this, this is not taking advantage of any of the clustering features in hyper-v, we can just make our own cluster manually and be done with it, cause this way, we use the hyper-v cluster for nothing if we don't use any of it's features13:40
atuvenie_claudiub|2: I don't think we can access that state13:40
claudiub|2why not? why don't we have access to it, but the cluster service magically has access to it?13:41
*** egallen has joined #openstack-meeting-313:42
atuvenie_claudiub|2: it's how the hyper-v cluster works. I assume we don't have access there, but we can check13:42
*** eliqiao has joined #openstack-meeting-313:43
atuvenie_claudiub|2: still, this sounds like a pretty nasty hack to be honest.13:43
claudiub|2well, nova core didn't offer any other solution13:44
claudiub|2anyways.13:45
claudiub|2remains to be seen how we can address this13:45
claudiub|2as for other news, there are a couple of them13:46
claudiub|2live-resize is going to be a thing, finally13:46
claudiub|2yeay13:46
claudiub|2but I'll have to do a blueprint beforehand, for a new api13:46
sagar_nikamok13:46
claudiub|2which can basically tell you "what you can do", given your permissions as a user and the capabilities of your cloud.13:46
claudiub|2the live-resize will be implemented for all drivers, there are volunteers for each of the drivers.13:47
claudiub|2as for host capabilities, there's going to be a new project called os-capabilities13:47
*** Guest41069 is now known as dansmith13:48
claudiub|2and there will be all sorts of capabilities, for cinder and neutron, not only for nova.13:48
claudiub|2so, we'll have to handle the hyper-v related capabilities in the near future on that project.13:49
sagar_nikamok13:49
claudiub|2multiple ephemerals, nova does them, but they have no idea why they were introduced in the first place13:49
claudiub|2and they might be deprecated in the future.13:49
claudiub|2then there's the new placement api13:50
claudiub|2which will be the next step for the scheduler13:50
claudiub|2and which will be outside of nova, as it will also be used by nova, neutron, cinder.13:50
sagar_nikamso where is this new API coming ?13:51
sagar_nikamif not nova13:51
claudiub|2although there's still plenty of work to be done on that, plus, they want to make sure the host capabilities fits very well in it.13:51
*** marst has quit IRC13:51
claudiub|2sagar_nikam: it is going to be a separate project13:51
sagar_nikamok13:52
sagar_nikamos-capabilities ?13:52
claudiub|2no, another13:52
claudiub|2no name yet13:52
*** VW has joined #openstack-meeting-313:53
sagar_nikamok13:53
claudiub|2and yeah, there were a lot of talks about how to evolve the nova api in the future13:53
claudiub|2as they want to get rid of most of the api extensions13:53
claudiub|2as you know, they already removed the legacy v2.0 api13:54
*** calbers has quit IRC13:54
claudiub|2and how to finally get rid of nova-network13:54
claudiub|2by constantly breaking bits of it, until people finally move to neutron.13:54
claudiub|2anyways.13:55
claudiub|2there were other topics as well, you can read them in the etherpad13:56
*** calbers has joined #openstack-meeting-313:56
claudiub|2but those were the major things, and things that we had an interest in.13:56
claudiub|2#topic open discussion13:57
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:57
*** Fdaisuke has joined #openstack-meeting-313:57
claudiub|2anything here?13:57
*** chandanc_ has joined #openstack-meeting-313:57
sagar_nikamback to cluster driver in compute-hyperv... any further discussion on iscsi support ?13:57
claudiub|2atuvenie_: ^13:58
*** calbers has quit IRC13:58
claudiub|2hm, she got disconnected14:00
atuvenie_sagar_nikam: if you want to go ahead with the idea of having each node login all targets you can propose a patch14:00
*** tovchinnikova has quit IRC14:00
*** calbers has joined #openstack-meeting-314:00
claudiub|2hm, i was wrong. :)14:01
sagar_nikamok14:01
claudiub|2anyways... need to end the meeting14:01
sagar_nikamthanks14:01
claudiub|2thanks folks for joining, see you next week!14:01
claudiub|2#endmeeting14:01
*** openstack changes topic to " (Meeting topic: ops_guide)"14:01
openstackMeeting ended Wed Jul 27 14:01:30 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-07-27-13.00.html14:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-07-27-13.00.txt14:01
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-07-27-13.00.log.html14:01
ajohi, qos? anyone?14:02
ajoping ralonsoh ? :)14:02
* ihrachys is here14:03
ihrachysthough just lurking14:03
ajohi ihrachys  :)14:03
ihrachysping me when you have something for me14:03
*** sagar_nikam has quit IRC14:03
ralonsohhi14:03
*** yamamoto has quit IRC14:03
ajoihrachys, nothing specifically, I just saw ralonsoh emails about qos min bw14:03
ajoralonsoh, and I just discovered that you're around here but not on #openstack-neutron :)14:03
ralonsohajo: i'll connect to openstack-neutron14:04
*** yamamoto has joined #openstack-meeting-314:04
*** yamamoto has quit IRC14:04
ajoralonsoh, may be we can just use the timeslot to discuss about that spec :)14:04
ralonsohperfect14:04
ajoand the issues you're having, to see where I can help14:04
ralonsohwell, the spec is fine14:05
ralonsohi think14:05
ajosorry, the code :D14:05
ihrachysajo: should you start a meeting?14:05
ralonsohok14:05
ihrachysajo: for logging purposes14:05
ralonsohhehehe yes14:05
ajolet's go then, lonely meeting (I was considering bluejeans or phone call which is more fluid)14:05
*** eliqiao has quit IRC14:06
ajoralonsoh, where are you located?14:06
*** marst has joined #openstack-meeting-314:06
ralonsohireland14:06
ajoireland, do you have a phone to be called? :)14:06
ajoihrachys, do you mind?14:06
ralonsohone sec14:06
ralonsoh+3536177781414:06
*** rhochmuth has joined #openstack-meeting-314:06
ihrachysajo: whatever you like. I just won't join.14:07
*** Swami has joined #openstack-meeting-314:07
ihrachysbut I guess it doesn't matter much14:07
*** zhurong has joined #openstack-meeting-314:07
ajoihrachys, ack, I will talk about the technical details with ralonsoh and we ping you on the chanel14:07
ajowith any update14:07
*** mars_toktonaliev has joined #openstack-meeting-314:07
*** marst has quit IRC14:07
ihrachysok, make sure you update everyone about resolution14:07
*** atuvenie_ has quit IRC14:07
ajoihrachys, yes, probably we can startmeeting/endmeeting to have it logged14:08
ajoafterwards14:08
ihrachysajo: nah just email or smth14:08
ihrachysok I won't take more of your time :)14:08
ajoor email, yup14:08
ajoralonsoh, trying to call14:08
ralonsohok!14:09
*** eliqiao has joined #openstack-meeting-314:09
*** Swami has quit IRC14:09
*** galstrom_zzz is now known as galstrom14:09
*** Swami has joined #openstack-meeting-314:10
*** kvinod has quit IRC14:11
*** itoader has quit IRC14:11
*** toddjohn has joined #openstack-meeting-314:12
*** abalutoiu has quit IRC14:14
*** uxdanielle has joined #openstack-meeting-314:15
*** zz_dimtruck is now known as dimtruck14:16
*** tonytan4ever has joined #openstack-meeting-314:17
*** azemlyanov has joined #openstack-meeting-314:18
*** davidsha has joined #openstack-meeting-314:22
*** claudiub|2 has quit IRC14:24
*** chandanc_ has quit IRC14:25
*** andymaier has quit IRC14:25
*** mars_toktonaliev has quit IRC14:27
*** marst has joined #openstack-meeting-314:27
*** rbak has joined #openstack-meeting-314:29
*** marst has quit IRC14:31
*** marst has joined #openstack-meeting-314:32
*** davidsha has left #openstack-meeting-314:32
*** iyamahat has joined #openstack-meeting-314:35
*** gabriel-bezerra has joined #openstack-meeting-314:39
*** sonu has quit IRC14:42
*** claudiub|2 has joined #openstack-meeting-314:43
*** Liuqing has quit IRC14:43
*** abalutoiu has joined #openstack-meeting-314:44
*** Liuqing has joined #openstack-meeting-314:44
*** egallen has quit IRC14:44
*** yamahata has joined #openstack-meeting-314:48
*** dasanind has joined #openstack-meeting-314:51
*** tomasztrebski has joined #openstack-meeting-314:52
*** egallen has joined #openstack-meeting-314:53
*** ddieterly has joined #openstack-meeting-314:54
*** egallen has quit IRC14:55
*** hosanai has joined #openstack-meeting-314:57
*** Fdaisuke_ has joined #openstack-meeting-314:57
*** nkrinner has quit IRC14:58
*** zhurong has quit IRC14:58
*** coolsvap_ is now known as coolsvap14:59
*** atuvenie_ has joined #openstack-meeting-314:59
*** zhurong has joined #openstack-meeting-314:59
*** azemlyanov has quit IRC14:59
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Jul 27 15:00:27 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. 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: monasca)"15:00
rhochmutho/15:00
openstackThe meeting name has been set to 'monasca'15:00
*** galstrom is now known as galstrom_zzz15:00
rhochmuthAgenda is at, https://etherpad.openstack.org/p/monasca-team-meeting-agenda15:00
rbako/15:00
*** nkrinner has joined #openstack-meeting-315:00
rhochmuthAgenda for Wednesday July 27, 2016 (15:00 UTC)15:01
rhochmuth1.OpenStack Barcelona Summit Voting15:01
rhochmuth2.Number of reviews or various organizations/contributors.15:01
rhochmuth3.Java deprecation plan15:01
rhochmuth4.Reviews15:01
rhochmuth1.https://review.openstack.org/#/c/343905/15:01
rhochmuth2.https://review.openstack.org/#/c/347481/15:01
shinya_kwbto/15:01
rhochmuth3.https://review.openstack.org/#/c/347532/15:01
rhochmuth4.https://review.openstack.org/#/c/332731/15:01
rhochmuth5.https://review.openstack.org/#/c/334856/15:01
rhochmuth3. Colorado Openstack Meetup 6th Birthday party:15:01
bkleio/15:01
Fdaisuke_o/15:01
tomasztrebskio/15:01
ddieterlyo/15:01
hosanaio/15:01
rhochmuthhi everyone15:01
*** nkrinner has left #openstack-meeting-315:01
*** revon has joined #openstack-meeting-315:01
rhochmuth#topic OpenStack Barcelona Summit Voting15:01
*** openstack changes topic to "OpenStack Barcelona Summit Voting (Meeting topic: monasca)"15:01
iurygregoryo/15:02
rhochmuthThe voting opened yesterday for the OpenStack Summit in Barcelona15:02
*** witek has joined #openstack-meeting-315:02
rhochmuthAs usual, you can search for topics as well as use the categories15:02
rhochmuthFor example, https://www.openstack.org/summit/barcelona-2016/vote-for-speakers/presentation/15929/?q=monasca15:02
rhochmuthgive all the Monasca sessions15:02
*** tsv has joined #openstack-meeting-315:03
rhochmuthIt would be good to see folks vote on these based on interest15:03
*** zhurong has quit IRC15:03
*** ericksonsantos has joined #openstack-meeting-315:03
rhochmuthDoes anyone know about the Masakari 2.0 project15:03
*** vhoward has joined #openstack-meeting-315:03
rhochmuththat is listed as a session, and they mention Monasca and their interest/TODO collaboration15:04
rhochmuthI guess not.15:04
bkleii don't15:04
*** yamamoto has joined #openstack-meeting-315:05
*** Liuqing has quit IRC15:05
rhochmuthSo, please take a look and vote for topics you are interested in. There are a number of session on monitoring, Vitrage, Watcher and Kubernetes that look interesting15:05
bkleiwill do15:05
rhochmuth#topic Number of reviews or various organizations/contributors.15:05
*** openstack changes topic to "Number of reviews or various organizations/contributors. (Meeting topic: monasca)"15:05
*** zhurong has joined #openstack-meeting-315:06
rhochmuthSo, I've been looking at the overall numbers of reviews occurring by various organizations and individuals15:06
*** galstrom_zzz is now known as galstrom15:06
rhochmuthMy concern is that there is a huge dissaproportinate number of reviews from my team mostly at HPE15:06
bkleibut your team is so good at it15:07
rhochmuthGoing forward I'm trying to figure out what to do, but new code submissions is going to have to take a back seat15:07
rhochmuthto reviews15:07
*** egallen has joined #openstack-meeting-315:08
rhochmuthSo, here is a good review to take a look at15:08
rhochmuthhttps://review.openstack.org/#/c/334688/15:08
witekhpe 65% new lines of code, 73% reviews15:08
rhochmuthIt was posted on June 27th, and other than Tomasz, I don't see any other reviewers15:08
bkleiapologies, will look15:09
rhochmuthHowever, I see code showing up from other companies15:09
rhochmuthand I constantly get pressure to priortize those reviews higher than others that are doing reviews15:09
rhochmuththat probably needs to change and become a more equitable mix15:10
rhochmuthAdditionally, I'm reviewing the list of core members15:10
rhochmuthReviews is one of the primary reasons for being core15:10
rhochmuthBeing core is not lifelong position15:10
*** yamamoto has quit IRC15:11
rhochmuthSo, I think folks just need to be aware of the amount of code that is going through the system and the need for taking part in more reviews to balance the load a little more15:12
bkleisounds like a good idea15:12
witekagree15:13
*** mtanino has joined #openstack-meeting-315:14
rhochmuth#topic Java deprecation plan15:14
*** openstack changes topic to "Java deprecation plan (Meeting topic: monasca)"15:14
bkleiwe briefly talked about ^^ at the midcycle15:14
bkleishould we set a goal for deprecation at least?15:15
*** rbrndt has joined #openstack-meeting-315:15
bkleithoughts?15:15
witekyes, we should plan the steps to deprecate java15:15
rhochmuthi would like to see a goal too15:15
tomasztrebskiby deprecate you mean: 'hey java is deprecated' or 'rm -rf */java' ?15:16
iurygregorythere is a plan to have packages to install monasca? just wondering =)15:16
rhochmuthcassandra seems to be key to this plan15:16
rhochmuthor a replacment for influxdb15:16
bkleiif we at least get it to be 'deprecated', then we could stop maintaining java with new features -- i could see even only doing cassandra in python15:17
rhochmuthiurygregory: There are packages for monasca15:17
*** pcaruana has quit IRC15:17
iurygregoryrhochmuth, like apt-get install monasca?15:17
witekI think we agreed on doing cassandra only in python15:17
iurygregoryO.o15:17
tomasztrebskimaybe not apt...but they are on python pypi15:17
rhochmuthiurygregory: i see. No we don't have a plan for that15:18
iurygregoryoh my idea is to impro puppet-monasca and this would be good  =)15:18
iurygregoryimprove*15:18
shinya_kwbtOh. So should I stop writing java cassandra?15:18
bkleimaybe even that is part of the java deprecation plan iurygregory15:18
bkleiyou could add install of the python api/persister to puppet-monasca15:19
iurygregorybklei, yeah15:19
bkleishinya_kwbt it's a suggestion15:19
witekshinya_kwbt: I agree with bklei, cassandra in Java is only additional effort15:20
rhochmuthIf support for Vertica and Cassandra was added to the persister, then we could deprecate the Java persister today.15:21
*** numans has quit IRC15:21
rhochmuthThe reason I mention that is that the persister is relatively simple15:21
ericksonsantossounds good15:21
bkleigood first step, would save shinya_kwbt java dev15:22
*** armax has joined #openstack-meeting-315:22
rhochmuthSimilar for the API15:22
rhochmuthbut i was thinking about staging development15:22
rhochmuthalthoguh if only the persister supports cassandra, then the api has to too15:22
*** emagana has joined #openstack-meeting-315:23
witekis anyone from DT here?15:23
bkleii can't think of a reason to add cassandra support for java for api or persister15:23
*** mickeys has joined #openstack-meeting-315:24
tomasztrebskiif we are at the topic of open changes - there's also notification-story to think of, at the moment already having impl in java and python from what I saw15:24
witekI agree with Roland, we have to make sure that Cassandra is the right way for Monasca first15:25
witekand make progress with that15:25
bkleieven more reason to do the 'pilot' only in python15:26
*** raj_singh_ has joined #openstack-meeting-315:26
shinya_kwbtI agree too.15:27
rhochmuthIf we had support for Vertica in the Python implementation, then HPE and TWC could switch to the Python implementation completely15:27
rhochmuthWe would essentially have parity at that point15:28
bklei* boom *15:28
rhochmuthThen we could add support for Cassandra and hopefully deprecate InfluxDB15:28
rhochmuthIf Cassandra was a suitable replacemnt for Vertica, then we don't need to add support for Vertica to Python15:28
*** vhoward has quit IRC15:29
bkleihmm -- not sure on that -- existing deployments have the issue of data migration15:29
tomasztrebskiso, shall we say: 'brace yourself - python is hissing' ? Personally still having both languages makes things harder, maybe not from POV of new features, but still any bugfixing and so on15:29
bkleii'd like to see vertica in python15:29
*** andreas_s has quit IRC15:29
rhochmuthSo, if we added Vertica to Python, we have parity with what we have today, and we can stop development on Java15:30
*** bklei_ has joined #openstack-meeting-315:30
rhochmuthat least the Java API and Persister15:30
rhochmuthThat work woudl fall on HPE and TWC since we are the only one's using it today15:31
rhochmuthusing Vertica that is15:31
bklei_yes -- we could split that work15:31
rhochmuthok, i'll have to look into that, but seems like a reasonable proposal/start15:32
*** galstrom is now known as galstrom_zzz15:32
bklei_we should be GA for MaaS by 9/1, then i'll have some time15:32
rhochmuthThe Threshold Engine would remain in Java15:32
tomasztrebskithreshold could be in python, but that would require writing that with spark I guess, like monasca-transform ? and that's also a lot of work15:33
rhochmuthThen in parallel we could add support for Cassandra15:33
witekwouldn't it be better to join the power and concentrate on Cassandra instead of Vertica?15:33
tomasztrebski+ not realty sure if that is possible15:33
rhochmuthwitek: i would love to say yes, i just dno't know how well cassandra will compare to Vertica15:34
*** bklei has quit IRC15:34
*** raj_singh_ has left #openstack-meeting-315:34
rhochmuthalso i don't know how long cassandra will really take15:35
witekrhochmuth: we answer that question only if we check15:35
witeki mean comparison with vertica15:35
shinya_kwbtI don't know how speed and use space too. > i just dno't know how well cassandra will compare to Vertica15:36
rhochmuthso, i think the vertica discussion is primarily a hpe/twc discussion15:37
bklei_yup15:37
rhochmuthi think we shoudl focus on a plan for cassandra with the greater community15:37
rhochmuthi'll look into resources that are available to work on this over the next few months15:38
*** atuvenie_ has quit IRC15:38
rhochmuthand get back to you next week15:38
witekgreat15:38
rhochmuthfrom an hpe stand-point15:38
bklei_i'll get approval for some of my time in sept rhochmuth15:38
rhochmuththx15:38
rhochmuthi'll also follow-up with DT15:39
rhochmuthwitek: do you know from your end what would be available15:39
witekrhochmuth: i could write them15:39
rhochmuththx15:39
rhochmuthsounds good15:39
witekrhochmuth: we should have some resources for cassandra, don't know exact numbers15:40
*** uxdanielle has quit IRC15:41
rhochmuthso, if we could get resources and focus on this from everyone starting up in sept or sooner and lasting a few months we might be able to get over this hurdle15:41
rhochmuth1 from HPE, TWC, DT, Fujitsu and NEC is a pretty serious effort15:41
rhochmuthhope i didn't leave anyone out15:41
rhochmuthi usually do15:42
witek:)15:42
*** zhurong has quit IRC15:42
rhochmuthso, how about we reconvene on this next week after everyone checks back with headquarters15:42
witekgood idea15:42
bklei_sounds good -- and we have to train rhochmuth to say CHARTER, not TWC :)15:43
witekhehe15:43
rhochmuthyou'll always be TWC to me15:43
bklei_:)15:43
*** david-lyle has joined #openstack-meeting-315:43
rhochmuth#topic Colorado Openstack Meetup 6th Birthday party15:43
*** openstack changes topic to "Colorado Openstack Meetup 6th Birthday party (Meeting topic: monasca)"15:43
rhochmuth    http://www.meetup.com/OpenStack-Colorado/events/231949941/?gj=co2&rv=co215:44
rhochmuth    Thursday 7/28 6:30 pm15:44
rhochmuth    CableLabs, 858 Coal Creek Circle, Louisville, CO, US, 8002715:44
rhochmuththought i woudl drop that in before the reviews15:44
rhochmuthsounds like bklei_ is going15:44
bklei_yes -- just want CO folks to know they are invited15:44
bklei_beer, food, giveaways15:45
rhochmuththanks, i don't hink I'm going to make this15:45
rhochmuthwhat, free beer15:45
rhochmuthmaybe15:45
bklei_:)15:45
rhochmuth#topic reviews15:45
*** openstack changes topic to "reviews (Meeting topic: monasca)"15:45
*** cbouch has joined #openstack-meeting-315:45
rhochmuthhttps://review.openstack.org/#/c/343905/15:45
rbakThat's mine.15:45
rhochmuthyup15:45
rbakI was hoping to get this merged since it's been sitting around for a while, but there's been a flurry of comments I need to address now.15:46
witek:)15:46
tomasztrebskiroland said nobody is doing any reviews, so I thought I will post some buster there ]:->15:46
rhochmuthtomasztrebski: thanks for all your reviews15:47
rhochmuth:-)15:47
rhochmuthrbak: so it sounds like this is getting some attention15:48
*** Sukhdev has joined #openstack-meeting-315:48
rbakright.  I'll address those comments today.15:48
rhochmuthi gave a +1, but didnt review closely, as JS isn't my area15:48
rhochmuthi'll try and take another look though15:48
rhochmuthhttps://review.openstack.org/#/c/347481/15:49
tomasztrebskiI think I will also try to spend some time on JS there, maybe I will find something else to comment about15:49
bklei_that review is just me, just want to advertise the change15:50
*** jlanoux has quit IRC15:50
rhochmuthIt looks like this one is getting attention15:50
rbakI'd rather not fix every issue in that repo right now.  We've been using this code for a while, this is just the repo move.15:50
bklei_i have a bit more tempest testing to do15:50
rhochmuthrbak: sounds like you want to get merged, and then start making improvements15:50
rhochmuthas well as getting others involved15:50
rhochmuthbklei_: yup15:51
rhochmuthhttps://review.openstack.org/#/c/347532/15:51
rhochmuthshouldn't the other review go first?15:52
*** egallen has quit IRC15:53
rhochmuthMoving onto: https://review.openstack.org/#/c/332731/15:53
*** tovchinnikova has joined #openstack-meeting-315:53
rhochmuthtomasztrebski: that is yours15:54
witeklooks like I have to look at this15:54
rhochmuthit looks like you are free to merge that one15:55
tomasztrebskisorry, was writing a comment for previous one15:55
tomasztrebskiyes, it sits there for some time and basically I'd like to know if anyone is fine with that or is there something that should be fixed15:55
rhochmuthi'm fine with it merging15:55
*** matrohon has quit IRC15:56
rhochmuthlast one15:56
rhochmuthhttps://review.openstack.org/#/c/334856/15:56
rhochmuthlooks good to me15:57
tomasztrebskiI don't see any room for improvement by my eye15:59
tomasztrebskibut if someone would like to test a bit or review a code, it is always welcomed15:59
*** dasanind has quit IRC15:59
rhochmuththx tomasztrebski15:59
*** rossella_s has quit IRC15:59
rhochmuthi meant to have tsv look at this16:00
rhochmuthand we might want to integrate into our helion distribution16:00
*** rossella_s has joined #openstack-meeting-316:00
*** banix has joined #openstack-meeting-316:00
tsvrhochmuth, sure, will review16:00
rhochmuthso, i need to end the meeting16:00
witekthank you16:01
rhochmuth#endmeeting monasca16:01
*** openstack changes topic to " (Meeting topic: ops_guide)"16:01
openstackMeeting ended Wed Jul 27 16:01:21 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-07-27-15.00.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-07-27-15.00.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-07-27-15.00.log.html16:01
*** hosanai has left #openstack-meeting-316:01
shinya_kwbtthanks bye16:01
tomasztrebskibye16:01
ericksonsantosbye16:01
*** tomasztrebski has quit IRC16:01
*** claudiub|2 has quit IRC16:04
*** tsv has quit IRC16:04
*** armax has quit IRC16:04
*** rbrndt has left #openstack-meeting-316:05
*** marst has quit IRC16:06
*** galstrom_zzz is now known as galstrom16:07
*** mjturek1 has joined #openstack-meeting-316:11
*** armax has joined #openstack-meeting-316:13
*** marst has joined #openstack-meeting-316:18
*** dasanind has joined #openstack-meeting-316:19
*** emagana has quit IRC16:19
*** cbouch has quit IRC16:19
*** emagana has joined #openstack-meeting-316:20
*** jtomasek has quit IRC16:22
*** asettle has quit IRC16:23
*** toddjohn has quit IRC16:23
*** toddjohn has joined #openstack-meeting-316:25
*** asettle has joined #openstack-meeting-316:27
*** david-lyle has quit IRC16:28
*** ddieterly is now known as ddieterly[away]16:30
*** toddjohn has quit IRC16:30
*** toddjohn has joined #openstack-meeting-316:31
*** iyamahat has quit IRC16:35
*** toddjohn has quit IRC16:36
*** yamahata has quit IRC16:37
*** abalutoiu_ has joined #openstack-meeting-316:37
*** toddjohn has joined #openstack-meeting-316:40
*** abalutoiu has quit IRC16:40
*** VW has quit IRC16:43
*** Sukhdev has quit IRC16:44
*** piet_ has joined #openstack-meeting-316:47
*** ddieterly[away] is now known as ddieterly16:48
*** s3wong has joined #openstack-meeting-316:48
*** Fdaisuke_ has quit IRC16:50
*** VW has joined #openstack-meeting-316:51
*** rbak has quit IRC16:52
*** bklei_ has quit IRC16:53
*** rbak has joined #openstack-meeting-316:53
*** bklei has joined #openstack-meeting-316:55
*** VW has quit IRC16:56
*** iyamahat has joined #openstack-meeting-316:59
*** muawiakhan has quit IRC17:05
*** Swami has quit IRC17:05
*** ralonsoh has quit IRC17:06
*** mbound has quit IRC17:08
*** ddieterly is now known as ddieterly[away]17:13
*** sdake has quit IRC17:15
*** asettle has quit IRC17:15
*** david-lyle has joined #openstack-meeting-317:20
*** david-lyle has quit IRC17:23
*** david-lyle_ has joined #openstack-meeting-317:23
*** david-lyle_ is now known as david-lyle17:24
*** david-lyle_ has joined #openstack-meeting-317:25
*** abalutoiu__ has joined #openstack-meeting-317:26
*** david-lyle has quit IRC17:29
*** emagana has quit IRC17:29
*** emagana has joined #openstack-meeting-317:30
*** abalutoiu_ has quit IRC17:30
*** david-lyle_ has quit IRC17:34
*** emagana has quit IRC17:34
*** david-lyle_ has joined #openstack-meeting-317:34
*** abalutoiu__ has quit IRC17:35
*** tonytan_brb has joined #openstack-meeting-317:36
*** abalutoiu__ has joined #openstack-meeting-317:36
*** tonytan4ever has quit IRC17:38
*** piet_ has quit IRC17:38
*** yamahata has joined #openstack-meeting-317:39
*** david-lyle_ has quit IRC17:42
*** ihrachys has quit IRC17:44
*** abalutoiu_ has joined #openstack-meeting-317:45
*** sambetts is now known as sambetts|afk17:45
*** sdague has quit IRC17:46
*** abalutoiu__ has quit IRC17:48
*** sdague has joined #openstack-meeting-317:54
*** dasanind has quit IRC17:56
*** VW has joined #openstack-meeting-318:01
*** VW_ has joined #openstack-meeting-318:04
*** VW has quit IRC18:07
*** VW_ has quit IRC18:08
*** VW has joined #openstack-meeting-318:13
*** ddieterly[away] has quit IRC18:13
*** numans has joined #openstack-meeting-318:13
*** baoli_ has quit IRC18:18
*** VW has quit IRC18:19
*** VW has joined #openstack-meeting-318:20
*** ociuhandu has quit IRC18:21
*** ddieterly has joined #openstack-meeting-318:22
*** Swami has joined #openstack-meeting-318:22
*** dasanind has joined #openstack-meeting-318:33
*** sarob has joined #openstack-meeting-318:34
*** baoli has joined #openstack-meeting-318:34
*** dasanind has quit IRC18:37
*** ericksonsantos has quit IRC18:44
*** toddjohn has quit IRC18:44
*** tonytan_brb has quit IRC18:44
*** toddjohn has joined #openstack-meeting-318:45
*** toddjoh__ has joined #openstack-meeting-318:49
*** toddjohn has quit IRC18:49
*** beagles is now known as beagles-brb18:51
*** toddjoh__ has quit IRC18:51
*** toddjohn has joined #openstack-meeting-318:52
*** dasanind has joined #openstack-meeting-318:52
*** dimtruck is now known as zz_dimtruck18:53
*** david-lyle_ has joined #openstack-meeting-318:57
*** zz_dimtruck is now known as dimtruck18:57
*** abalutoiu__ has joined #openstack-meeting-318:59
*** abalutoiu_ has quit IRC19:02
*** VW_ has joined #openstack-meeting-319:02
*** VW has quit IRC19:03
*** beagles-brb is now known as beagles19:06
*** david-lyle_ is now known as david-lyle19:07
*** fifieldt has quit IRC19:08
*** tovchinnikova has quit IRC19:09
*** emagana has joined #openstack-meeting-319:12
*** marst has quit IRC19:16
*** numans has quit IRC19:16
*** emagana has quit IRC19:16
*** tonytan4ever has joined #openstack-meeting-319:17
*** fifieldt has joined #openstack-meeting-319:18
*** coolsvap has quit IRC19:21
*** ddieterly is now known as ddieterly[away]19:22
*** marst has joined #openstack-meeting-319:24
*** sdake has joined #openstack-meeting-319:25
*** marst has quit IRC19:27
*** marst has joined #openstack-meeting-319:28
*** kzaitsev_mb has joined #openstack-meeting-319:28
*** anilvenkata has quit IRC19:28
*** toddjohn has quit IRC19:31
*** kzaitsev_mb has quit IRC19:36
*** asettle has joined #openstack-meeting-319:41
*** toddjohn has joined #openstack-meeting-319:41
*** sdake has quit IRC19:43
*** ddieterly[away] is now known as ddieterly19:47
*** kzaitsev_mb has joined #openstack-meeting-319:47
*** sdake has joined #openstack-meeting-319:53
*** robcresswell has joined #openstack-meeting-319:58
*** dasanind has quit IRC19:58
*** kzaitsev_mb has quit IRC19:59
robcresswell#startmeeting horizon20:00
openstackMeeting started Wed Jul 27 20:00:12 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: horizon)"20:00
robcresswello/20:00
openstackThe meeting name has been set to 'horizon'20:00
*** mickeys has quit IRC20:00
lcastello/20:00
*** rhochmuth has left #openstack-meeting-320:00
*** matt-borland has joined #openstack-meeting-320:00
*** mickeys has joined #openstack-meeting-320:01
*** mickeys has quit IRC20:01
*** mickeys has joined #openstack-meeting-320:01
matt-borlando/20:01
*** tsufiev has joined #openstack-meeting-320:01
tsufievo/20:01
robcresswellHey folks20:02
lcastellhey20:02
robcresswellWe are without agenda items again20:02
robcresswellSo we can just move to open discussion if anyone has anything to raise20:02
matt-borlandPhantomJS?20:03
robcresswell#topic Open Discussion20:03
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"20:03
matt-borlandthe gate npm-run-test20:03
robcresswellAh, yeah20:03
robcresswellDo e have a cause yet?20:03
robcresswellwe*20:03
matt-borlandI will happily help figure out what is going on, if I can get some help with how to debug20:03
matt-borlandI think I need to talk to krotscheck about how to do that.20:04
robcresswellI would imagine digging up krotscheck blog on building a local node would be sensible20:04
robcresswellSee if it can be reproduced locally20:04
krotscheckI hear that krotscheck has a blog whose URL is suprisingly similar to his IRC handle20:04
matt-borlandheh20:05
tsufievlol )20:05
david-lylehttps://krotscheck.net/2016/06/01/how-to-simulate-an-openstack-infra-slave.html20:05
matt-borlandthanks :)20:05
david-lyleI seem to have that bookmarked :)20:05
matt-borlandIn other news, not quite related, do devs prefer to have tests run in PhantomJS or in Chrome/FF?20:05
matt-borlandI had a complaint about having to use Chrome.20:05
matt-borland*heard a complaint20:06
robcresswellI don't have any strong preference20:06
matt-borlandok.20:06
robcresswellIt seems to bug some people that a window opens temporarily20:06
robcresswellin chrome20:06
*** yamamoto has joined #openstack-meeting-320:06
matt-borlandyeah.  Maybe we can make it configurable (without changing the code itself)20:06
matt-borlandright now you have to edit karma.conf to modify that20:06
robcresswellthe gate is the bigger issue :)20:07
tsufievI recall PhantomJS had some issues with file inputs20:07
matt-borlandyep20:07
robcresswelltsufiev: Yep20:07
tsufievthough I do not know if it still does20:07
matt-borlandPhantom doesn't respect things like Promise/File objects right off the bat20:07
matt-borlandsome of those presumed globals20:07
matt-borlandanyway, ok, so fixing the npm-run-test (and -lint!) is a priority, cool20:08
matt-borlandI'll budget quiet time for that tomorrow20:08
david-lylewhat's the upside to testing in a non-realworld browser?20:08
robcresswell*silence*20:09
matt-borlandnot much, mostly that it doesn't pop up a window, or require Chrome (which is not open source, yadda yadda)20:09
robcresswellit can be a good deal faster too.20:09
tsufievalso we can use xvfb to hide browser window20:09
robcresswellWhich is the important part :p20:10
tsufievif that's the real problem20:10
matt-borlandthat's true, there's slightly less runup for PhantomJS20:10
matt-borlanddoesn't sound like a big priority.20:10
matt-borlandthat's fine with me, just asking the question.20:10
robcresswellI don't consider a window popping up an issue, ha. Lets just debug the gate timeouts.20:10
matt-borlandyep20:10
*** ediardo has joined #openstack-meeting-320:10
robcresswellN-3 is 4 weeks tomorrow20:11
david-lyle:o20:11
robcresswellSo make sure to be wrapping up features etc20:11
matt-borlandI think with tsufiev's addition of basic integration tests, we have only one more known hurdle to make Angular Images default.20:12
tsufievlooking at the patch in browser right now20:12
tsufievI mean how it works20:12
matt-borlandThe other hurdle is displaying 'in transition' statuses for the row/field in a list.20:12
matt-borlandMatt Wood has a patch for that.20:12
robcresswellDoes that solve the issue of running both sets of tests/20:13
tsufievI have a slight concern that although we have an integration 'smoke' test for angular content, we don't run it20:13
robcresswell?*20:13
matt-borlandso I'd like that all to land within about 5 days20:13
tsufievso even if something will break NG Images panel, we won't notice that until run the test explicitly20:13
robcresswellI didnt think we had a solution for running both at once yet20:13
robcresswellprobably just needs a separate job, but need to figure out the best way of toggling that20:14
tsufievI had an idea of some tricky setup to pass an alternate Django setting using cookies in integration tests20:14
robcresswell:/ cookies?20:14
tsufievdidn't investigate yet20:14
matt-borlandcan we not alter settings as part of the test run?20:14
matt-borland(an independent test run?)20:15
tsufievnot, because integration test is a separate process from horizon webserver20:15
tsufievwe would have to develop our own way of IPC20:15
matt-borlandbut I mean, we can modify that config file too...right?20:15
tsufievor... I have an idea20:15
matt-borlandisn't that why there's a horizon.config for the unit tests?20:15
matt-borlander, integration tests?20:16
tsufievwe could create a new dsvm job for angular content :)20:16
tsufievless troubles with cookies20:16
robcresswellI'd have thought the easiest way was just to append a boolean to the conf file in the pre test hook20:16
robcresswellor something like that20:16
robcresswelltsufiev: Yes, this was my thinking. Separate job seems cleanest20:16
tsufievrobcresswell, but it still will be either of these 2 values in a single test run20:16
robcresswelleither is fine, as we can just run two jobs20:16
robcresswellHaving it swap halfway is hacky20:17
matt-borlandI'm assuming most of the time for the integration is the dsvm setup?20:17
tsufievmatt-borland, horizon.conf is a way to tell integration tests about horizon enabled features20:17
*** tangchen has quit IRC20:17
matt-borlandyep, exactly tsufiev20:17
tsufievhorizon.conf and openstack_dashboard.settings may be theoretically disjoint20:17
tsufiever, inconsistent20:17
matt-borlandof course20:17
*** ihrachys has joined #openstack-meeting-320:17
tsufievokay, so a separate job for angular content, that sounds pretty reasonable to me20:18
tsufievI hope infra folks won't blame us :D20:18
matt-borlandIf they do, we cross that bridge.  I'm glad we at least have tests that respond to current settings.20:18
matt-borlandand operate in both panel enabled situations (even if separately)20:18
matt-borlandthanks again for your help with that tsufiev20:19
tsufievif we hit the topic of different Horizon modes & integration tests, I have a related question20:19
*** tangchen has joined #openstack-meeting-320:19
matt-borlandso, to be clear, we can approve the switch patch before that's worked out, we just don't want to throw the switch itself to Angular, right?20:19
robcresswellYes, thats a step in the right direction20:19
tsufievI have a patch for [Django] Create Image which uses CORS20:19
robcresswellYes, matt-borland20:19
matt-borlandthanks20:20
tsufievbut a CORS support is a separate feature20:20
robcresswellWe need both being tested in the gate before we can swap the default.20:20
tsufievdon't have the luxury of creating another job just to test it alone :)20:20
robcresswellbut nothing to stop allowing deployers to swap20:20
matt-borlandyep, sounds great robcresswell20:20
tsufievit's the same issue as with testing both angular and legacy content20:20
robcresswelltsufiev: Even with a separate job, how would the ocnfiguration be job-specific?20:21
*** hurgleburgler has joined #openstack-meeting-320:21
tsufievanother setting switch in a pre-test hook20:21
robcresswellRight. Sorry if I'm being slow, but how is the pre-test hook job specific? I thought it lived within horizon20:22
tsufievwell, we'll need to provide at least two pre-test hooks, one for legacy (existing), another for legacy20:22
robcresswellOr is the implication that the job called "angular pre-test hook" or similar20:22
*** tyr_ has joined #openstack-meeting-320:22
robcresswellah, yep20:22
tyr_ o/20:23
tsufiev*another for angular20:23
robcresswelltsufiev: If its just a a shell script, could we not pass in a parameter?20:23
tsufievmatt-borland, I'm in for approving that patch even before we have a job separation20:23
robcresswellWould be nice to avoid config script duplication20:23
tsufievrobcresswell, I think we could20:24
tsufiev80% sure20:24
robcresswellI think that would be cleaner.20:24
robcresswellI'll have a look tomorrow. Something like ./pre_test_hook.sh ng would be convenient.20:24
matt-borlandrobcresswell, keep me in the loop on those developments, I'd like to know how it all works :)20:24
matt-borlandand obviously if there's anything I can do to help get those jobs testing the way we want20:25
tsufievmatt-borland, have your read docs on integration testing ;)?20:26
robcresswellI'll discuss in infra tomorrow, see if they have any suggestions20:26
matt-borlandabout how to set up pre-test-hooks, etc.? no20:26
matt-borlandtsufiev ^^ that is20:26
tsufievnope, about page object pattern and the importance of it :)20:27
matt-borlandI'm fine with it20:27
robcresswellre: schema form, I've updated the whole thing to use the service patterns that are common now. The only bit thats got me stuck is returning data from the create service back to the LI modal. It creates the network fine, but it doesnt seem to pass the data how I expect it to.20:27
matt-borlandI will only complain if it doesn't work or is a problem, tsufiev20:27
tyr_robcresswell: if you post an updated patch version I'm happy to help troubleshoot20:27
tsufievmatt-borland, it may seem that it makes things slightly more complicated than they are, but in a long run it helps to keep the tests maintainable20:28
robcresswelltyr_: Yeah, I will do that I think. Faster that way.20:28
robcresswelltyr_: I'll ping about it tomorrow. Kinda spent today.20:28
matt-borlandtsufiev, I have not expressed complaints about pageobject20:28
matt-borlandit's similar to other testing infrastructures I've used, it's fine20:29
tsufievmatt-borland, sorry then, I have misinterpreted your message20:29
* matt-borland means 'fine' when he says 'fine,' not 'FINE!' :)20:29
tsufiev:)20:29
matt-borlandtsufiev, I had just taken a very simple and admittedly sloppy approach to get started20:30
tsufievnp, I prefer to get things done fast myself20:31
robcresswellI've been starring patches that I'd like to see make the release in the next month20:32
robcresswell#link https://review.openstack.org/#/q/starredby:rob-cresswell+status:open20:32
tsufievI expected to see at least 50 patches there20:32
robcresswellha, I've just started doing it recently. The idea is to use that to advertise patches-to-review20:33
robcresswellFor the most part, file upload, angular images, filtering improvements and django 1.10 compatibility20:33
matt-borlandI like the idea robcresswell, thanks20:34
ediardogot it20:34
robcresswellIf you want patches to focus reviews on, this list aims to be the critical ones.20:34
*** cleong has quit IRC20:35
tsufievyep, it's much more maintainable than a wiki page, robcresswell20:35
robcresswelltsufiev: Yes, much lower input!20:35
robcresswellIn case anyone else didnt realise, you can customise your gerrit at Settings > Preferences and add custom links20:36
robcresswellReally useful to put davids review dashboard in there as well as that starred link. Helps focus reviews on important items better.20:36
robcresswellThats all from me; any other issues? Otherwise we shall end early20:37
tsufievI'd like to ask only about context['THEME'] fix20:37
tsufievfolks from murano team asked about it several times and every time I had to point them to a zhurong's patch which does it wrong :/20:38
hurgleburglerisn't it a configuration problem?20:38
robcresswellAre there any plugins still blocked on that? I had thought the config updates resolved that issue?20:38
*** yamamoto has quit IRC20:39
tsufievI don't understand either how they managed to get this error20:39
tyr_I see it anytime I'm running COMPRESS_ENABLED=True.20:39
tyr_What is the current idea for the fix?20:39
tsufievhttps://review.openstack.org/#/c/344871/ tyr_20:40
hurgleburglerI run compress enabled true all the time20:40
hurgleburglerthe thing is … the fix is just a bandaid20:40
tsufievI guess it depends on some missing config value20:40
hurgleburglerthe context sets the default using the default value its supposed to20:40
hurgleburglerusing the settings20:40
tyr_I do not have COMPRESS_OFFLINE=True fwiw20:41
tsufievwhich... tells me that a few unit tests for themes wouldn't hurt, hurgleburgler ;)20:41
hurgleburglerif the settings aren't set properly, then it can't know what to default to20:41
tyr_which settings in particular hurgleburgler?20:41
robcresswellTo be clear, this fails *only* in a unit test environment20:42
hurgleburglertsufiev: there was talk last year of a need for unit tests for the static settings in general20:42
robcresswelland *only* when you do not import from Horizon20:42
hurgleburglerDEFAULT_THEME and AVAILABLE_THEMES20:42
hurgleburgleryou really only need AVAILABLE_THEMES, DEFAULT_THEME will fall back to AVAILABLE_THEMES[0]20:42
tyr_both are set in my settings.py, yet I see the THEME compress error20:43
hurgleburglerand if you don't have AVAILABLE_THEMES set, it falls back to the previous setting, custom_theme_path20:43
robcresswellhttps://review.openstack.org/#/c/344871 updated. Still a bandaid.20:43
hurgleburglerugh, that fix duplicates logic that already exists else where20:43
hurgleburglerso now we would be doing the exact same default check 2-3 times20:44
robcresswellWait, where else does it do that check?20:44
robcresswellthe issue just arises because that function defaults to []20:44
robcresswellif it defaults to the default theme, it should work fine, I believe.20:44
hurgleburgleryou are assuming that 'default' exists20:44
hurgleburglerit migh tnot20:44
hurgleburglersomeone might not be configured for 'default' at all20:45
tsufievcommented on that inline20:45
tsufievhm20:45
tsufievhurgleburgler, is there a way to enforce at least one theme to be available?20:45
hurgleburglerthat's why there is a DEFAULT_THEME setting20:45
hurgleburglerit should already be enforcing that … but I can take a look again20:45
*** sdake has quit IRC20:46
robcresswellif you try and run horizon without that key it will enforce it and fall over immediately20:46
robcresswellfrom my tests the other day20:46
robcresswellEither way, at some point in the chain its not throwing an error or defaulting as desired20:47
robcresswellAlso, rather unfortunately, the release nots at the time mention the deprecated settings but not the new required ones I believe.20:47
* tsufiev sees 'enforcing' as failing and telling how to prevent a failure20:48
hurgleburglerI'll take a look at it20:48
robcresswellthanks hurgleburgler20:48
robcresswellmuch appreciated :)20:48
tsufievhurgleburgler, thank you!20:48
hurgleburglernp20:49
robcresswellThanks for your time everyone!20:51
robcresswell#endmeeting20:52
*** openstack changes topic to " (Meeting topic: ops_guide)"20:52
openstackMeeting ended Wed Jul 27 20:52:02 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-07-27-20.00.html20:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-07-27-20.00.txt20:52
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-07-27-20.00.log.html20:52
*** tyr_ has left #openstack-meeting-320:52
*** tsufiev has left #openstack-meeting-320:52
*** hurgleburgler has left #openstack-meeting-320:53
*** abalutoiu_ has joined #openstack-meeting-320:55
*** asettle has quit IRC20:55
*** robcresswell has left #openstack-meeting-320:56
*** abalutoiu__ has quit IRC20:59
*** neiljerram has joined #openstack-meeting-321:05
*** sergio_nubeliu has quit IRC21:08
*** matt-borland has quit IRC21:18
*** rtheis has quit IRC21:22
*** flwang1 has joined #openstack-meeting-321:25
*** david-lyle has quit IRC21:25
*** pvaneck has joined #openstack-meeting-321:27
*** neil_ has joined #openstack-meeting-321:33
*** neil_ has quit IRC21:34
*** neiljerram has quit IRC21:35
*** yamamoto has joined #openstack-meeting-321:39
*** marst has quit IRC21:44
*** yamamoto has quit IRC21:45
*** tonytan4ever has quit IRC21:51
*** marst has joined #openstack-meeting-321:57
*** ddieterly is now known as ddieterly[away]22:01
*** iyamahat_ has joined #openstack-meeting-322:02
*** mbound has joined #openstack-meeting-322:03
*** c64cosmin has quit IRC22:03
*** iyamahat has quit IRC22:04
*** abalutoiu_ has quit IRC22:04
*** galstrom is now known as galstrom_zzz22:07
*** mbound has quit IRC22:07
*** bklei has quit IRC22:08
*** bklei has joined #openstack-meeting-322:08
*** VW_ has quit IRC22:11
*** bklei has quit IRC22:13
*** salv-orlando has quit IRC22:13
*** salv-orlando has joined #openstack-meeting-322:17
*** kzaitsev_mb has joined #openstack-meeting-322:22
*** david-lyle has joined #openstack-meeting-322:22
*** salv-orlando has quit IRC22:23
*** david-lyle has quit IRC22:25
*** david-lyle has joined #openstack-meeting-322:25
*** ddieterly[away] is now known as ddieterly22:25
*** ddieterly has quit IRC22:34
*** banix has quit IRC22:38
*** rbak has quit IRC22:40
*** toddjohn has quit IRC22:45
*** toddjohn has joined #openstack-meeting-322:46
*** asettle has joined #openstack-meeting-322:46
*** emagana has joined #openstack-meeting-322:48
*** david-lyle has quit IRC22:50
*** toddjohn has quit IRC22:50
*** david-lyle_ has joined #openstack-meeting-322:50
*** asettle has quit IRC22:51
*** emagana has quit IRC22:53
*** dimtruck is now known as zz_dimtruck22:58
*** david-lyle_ has quit IRC23:01
*** kzaitsev_mb has quit IRC23:02
*** vishwanathj has quit IRC23:02
*** abalutoiu has joined #openstack-meeting-323:05
*** abalutoiu has quit IRC23:08
*** kbyrne has quit IRC23:10
*** kbyrne has joined #openstack-meeting-323:16
*** sdake has joined #openstack-meeting-323:17
*** sdake has quit IRC23:25
*** abalutoiu has joined #openstack-meeting-323:26
*** mbound has joined #openstack-meeting-323:28
*** abalutoiu_ has joined #openstack-meeting-323:29
*** abalutoiu has quit IRC23:32
*** Sukhdev has joined #openstack-meeting-323:36
*** mtanino has quit IRC23:37
*** ddieterly has joined #openstack-meeting-323:42
*** ddieterly has quit IRC23:42
*** salv-orlando has joined #openstack-meeting-323:42
*** abalutoiu_ has quit IRC23:45
*** abalutoiu has joined #openstack-meeting-323:45
*** ddieterly has joined #openstack-meeting-323:45
*** bklei has joined #openstack-meeting-323:46
*** salv-orlando has quit IRC23:47
*** bklei has quit IRC23:51
*** bpokorny has joined #openstack-meeting-323:54
*** ajmiller_ has quit IRC23:56
*** asettle has joined #openstack-meeting-323:58
*** rossella_s has quit IRC23:59

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