Wednesday, 2016-02-17

*** ivar-laz_ has quit IRC00:02
*** ivar-lazzaro has joined #openstack-meeting-300:03
*** dims_ has quit IRC00:03
*** ivar-lazzaro has quit IRC00:05
*** ivar-lazzaro has joined #openstack-meeting-300:06
*** galstrom_zzz is now known as galstrom00:15
*** Anand has joined #openstack-meeting-300:15
*** Anand has quit IRC00:16
*** rbak has quit IRC00:17
*** dconde has quit IRC00:18
*** salv-orlando has quit IRC00:20
*** jeblair has quit IRC00:22
*** galstrom is now known as galstrom_zzz00:24
*** dims has joined #openstack-meeting-300:33
*** loquacities has joined #openstack-meeting-300:34
*** banix has quit IRC00:34
*** tej has joined #openstack-meeting-300:37
*** ajmiller_ has joined #openstack-meeting-300:38
*** tej has quit IRC00:41
*** ajmiller has quit IRC00:41
*** dobson has quit IRC00:43
*** tej has joined #openstack-meeting-300:46
*** hoangcx has joined #openstack-meeting-300:49
*** tej has quit IRC00:49
*** kzaitsev_mb has quit IRC00:49
*** dconde has joined #openstack-meeting-300:50
*** SumitNaiksatam has quit IRC00:50
*** dconde has quit IRC00:50
*** kzaitsev_mb has joined #openstack-meeting-300:51
*** dobson has joined #openstack-meeting-300:54
*** tej has joined #openstack-meeting-300:55
*** tej has quit IRC00:57
*** tej has joined #openstack-meeting-300:58
*** doug-fish has quit IRC01:01
*** doug-fish has joined #openstack-meeting-301:02
*** tej has quit IRC01:03
*** bswartz has joined #openstack-meeting-301:03
*** mtanino has quit IRC01:04
*** galstrom_zzz is now known as galstrom01:30
*** ekarlso has quit IRC01:30
*** Swami has quit IRC01:31
*** stanzgy has joined #openstack-meeting-301:33
*** sdake has quit IRC01:36
*** tfukushima has joined #openstack-meeting-301:40
*** doug-fish has quit IRC01:44
*** doug-fish has joined #openstack-meeting-301:44
*** zhurong has joined #openstack-meeting-301:45
*** ekarlso has joined #openstack-meeting-301:46
*** doug-fis_ has joined #openstack-meeting-301:48
*** kzaitsev_mb has quit IRC01:48
*** doug-fish has quit IRC01:49
*** doug-fis_ has quit IRC01:52
*** baojg has joined #openstack-meeting-301:53
*** zhurong has quit IRC01:55
*** zhurong has joined #openstack-meeting-301:56
*** galstrom is now known as galstrom_zzz01:57
*** Aish has quit IRC01:59
*** cartik has joined #openstack-meeting-302:02
*** cartik has quit IRC02:06
*** yamamoto_ has joined #openstack-meeting-302:06
*** zz_dimtruck is now known as dimtruck02:08
*** yamamoto_ has quit IRC02:09
*** FallenPegasus has joined #openstack-meeting-302:11
*** FallenPegasus has quit IRC02:11
*** ivar-lazzaro has quit IRC02:12
*** tfukushima has quit IRC02:15
*** yushiro has joined #openstack-meeting-302:17
*** yushiro has left #openstack-meeting-302:17
*** zhurong has quit IRC02:19
*** zhurong has joined #openstack-meeting-302:20
*** bpokorny_ has joined #openstack-meeting-302:24
*** banix has joined #openstack-meeting-302:26
*** banix has quit IRC02:26
*** banix has joined #openstack-meeting-302:26
*** tfukushima has joined #openstack-meeting-302:27
*** markvoelker has quit IRC02:27
*** bpokorny has quit IRC02:28
*** bpokorny_ has quit IRC02:29
*** cartik has joined #openstack-meeting-302:31
*** _sarob has quit IRC02:31
*** doug-fish has joined #openstack-meeting-302:38
*** cartik has quit IRC02:38
*** doug-fish has quit IRC02:39
*** doug-fish has joined #openstack-meeting-302:40
*** ajmiller_ has quit IRC02:44
*** kzaitsev_mb has joined #openstack-meeting-302:44
*** baojg has quit IRC02:49
*** Aish has joined #openstack-meeting-302:51
*** Aish has left #openstack-meeting-302:51
*** doug-fish has quit IRC02:51
*** coolsvap|away is now known as coolsvap02:52
*** rossella_s has quit IRC02:57
*** rossella_s has joined #openstack-meeting-302:58
*** s3wong has quit IRC02:58
*** salv-orlando has joined #openstack-meeting-302:59
*** zhurong has quit IRC03:03
*** salv-orlando has quit IRC03:04
*** zhurong has joined #openstack-meeting-303:04
*** Aish has joined #openstack-meeting-303:06
*** Aish has quit IRC03:06
*** yamamoto has joined #openstack-meeting-303:10
*** tej has joined #openstack-meeting-303:13
*** tej has quit IRC03:17
*** baojg has joined #openstack-meeting-303:18
*** zhurong_ has joined #openstack-meeting-303:20
*** dimtruck is now known as zz_dimtruck03:20
*** SumitNaiksatam has joined #openstack-meeting-303:20
*** zhurong has quit IRC03:21
*** zz_dimtruck is now known as dimtruck03:22
*** dims has quit IRC03:23
*** markvoelker has joined #openstack-meeting-303:27
*** kzaitsev_mb has quit IRC03:31
*** markvoelker has quit IRC03:33
*** rbak has joined #openstack-meeting-303:48
*** dimtruck is now known as zz_dimtruck03:50
*** baoli_ has quit IRC03:50
*** kzaitsev_mb has joined #openstack-meeting-303:51
*** baoli has joined #openstack-meeting-303:52
*** baoli has quit IRC03:53
*** baoli has joined #openstack-meeting-303:54
*** kzaitsev_mb has quit IRC03:55
*** zhurong_ has quit IRC03:55
*** banix has quit IRC03:59
*** zhurong has joined #openstack-meeting-304:00
*** fawadkhaliq has joined #openstack-meeting-304:02
*** fawadkhaliq has quit IRC04:03
*** shwetaap has joined #openstack-meeting-304:03
*** shwetaap1 has joined #openstack-meeting-304:03
*** cartik has joined #openstack-meeting-304:05
*** kebray has quit IRC04:05
*** shwetaap has quit IRC04:08
*** bpokorny has joined #openstack-meeting-304:10
*** zz_dimtruck is now known as dimtruck04:10
*** kebray has joined #openstack-meeting-304:11
*** zhurong has quit IRC04:13
*** zhurong has joined #openstack-meeting-304:14
*** soichi has joined #openstack-meeting-304:17
*** galstrom_zzz is now known as galstrom04:20
*** baojg has quit IRC04:24
*** zhurong has quit IRC04:27
*** fawadkhaliq has joined #openstack-meeting-304:28
*** baojg has joined #openstack-meeting-304:29
*** fawadk has joined #openstack-meeting-304:34
*** zhurong has joined #openstack-meeting-304:34
*** galstrom is now known as galstrom_zzz04:35
*** fawadkhaliq has quit IRC04:35
*** dimtruck is now known as zz_dimtruck04:37
*** fawadk has quit IRC04:39
*** baoli has quit IRC04:44
*** zhurong has quit IRC04:55
*** neelashah has joined #openstack-meeting-304:58
*** bpokorny has quit IRC05:00
*** zhurong has joined #openstack-meeting-305:04
*** fawadkhaliq has joined #openstack-meeting-305:15
*** pt_15_ has quit IRC05:15
*** zhurong has quit IRC05:16
*** zhurong has joined #openstack-meeting-305:19
*** neelashah has quit IRC05:20
*** rbak has quit IRC05:23
*** armax has quit IRC05:23
*** _sarob has joined #openstack-meeting-305:27
*** sdake has joined #openstack-meeting-305:27
*** kzaitsev_mb has joined #openstack-meeting-305:29
*** markvoelker has joined #openstack-meeting-305:29
*** _sarob has quit IRC05:32
*** markvoelker has quit IRC05:33
*** kzaitsev_mb has quit IRC05:34
*** anil_rao has joined #openstack-meeting-305:42
*** zhurong has quit IRC05:42
*** zhurong has joined #openstack-meeting-305:45
*** Poornima has joined #openstack-meeting-305:46
*** zhurong has quit IRC05:47
*** _sarob has joined #openstack-meeting-305:48
*** zhurong has joined #openstack-meeting-305:48
*** hoangcx has quit IRC05:48
*** sarob_ has joined #openstack-meeting-305:48
*** sdake has quit IRC05:49
*** _sarob has quit IRC05:53
*** vasubabu has joined #openstack-meeting-305:54
*** hoangcx has joined #openstack-meeting-305:56
*** nkrinner has joined #openstack-meeting-305:56
*** baoli has joined #openstack-meeting-306:04
*** hoangcx has quit IRC06:04
*** lazy_prince has joined #openstack-meeting-306:07
*** killer_prince has joined #openstack-meeting-306:07
*** lazy_prince has quit IRC06:07
*** sarob_ has quit IRC06:07
*** baoli has quit IRC06:09
anil_raowe will start the TaaS meeting in 5 min'06:25
*** kaz has joined #openstack-meeting-306:25
*** fawadkhaliq has quit IRC06:27
*** fawadk has joined #openstack-meeting-306:27
*** fawadk has quit IRC06:30
yamamotohi06:30
anil_rao#startmeeting taas06:30
openstackMeeting started Wed Feb 17 06:30:08 2016 UTC and is due to finish in 60 minutes.  The chair is anil_rao. Information about MeetBot at http://wiki.debian.org/MeetBot.06:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.06:30
*** openstack changes topic to " (Meeting topic: taas)"06:30
openstackThe meeting name has been set to 'taas'06:30
kazhi06:30
*** salv-orlando has joined #openstack-meeting-306:30
*** fawadkhaliq has joined #openstack-meeting-306:30
anil_raoHi06:30
vasubabuhi06:30
*** kzaitsev_mb has joined #openstack-meeting-306:31
fawadkhaliqhello folks06:31
anil_raoLooks like there is only one topic today06:31
anil_raoShall we get started06:31
anil_rao#topic tap-service-create specify dest port or create destination port06:32
*** openstack changes topic to "tap-service-create specify dest port or create destination port (Meeting topic: taas)"06:32
*** salv-orlando has quit IRC06:32
reedipanil_rao: whats your take on this?06:33
anil_raoI notice that the latest version of the spec is suggesting that tap-service-create create the destination port06:33
reedipanil_rao : yup , thats right06:33
fawadkhaliqI think both should be supported.06:33
*** e0ne has joined #openstack-meeting-306:33
fawadkhaliqThere is no harm, is there?06:34
anil_raoActually, this is not how it is currently supported (as the spec seems to suggest).06:34
anil_raoOne problem I see is this (let me explain)06:34
anil_raoIf tap-service-create were to instantiate the destination port, there would be no monitoring VM at that time.06:34
*** kzaitsev_mb has quit IRC06:35
anil_raoSo the port doesn't really get bound to a compute node. Later then the monitoring VM is instantiated and consumes that port we will need a callback in order to place the flows for receiving traffic on the host where the destination port is bound06:35
anil_raoNot saying that this can't be done but the current implementaion has taken the easy route of working with an existing port that is already being used by the monitoring VM.06:36
anil_raoI am curious to know what workflow folks expect to see when tap-service-create instantiates the destination port.06:37
fawadkhaliqanil_rao: makes sense. We will probably have to support this anyway later because an operator may attach detach VM ports any time.06:37
*** hdaniel has joined #openstack-meeting-306:38
fawadkhaliqsince the functionality is there, no worries. From design perspective, we keep it in and track the lack of support via a bug report maybe and release note?06:38
fawadkhaliqs/is there/is not there/06:38
yamamotoanil_rao: do you mean the current impl is relying on the VM being launched beforehand?06:39
anil_raoyamamoto: Yes06:39
yamamotoit sounds like a bug06:39
anil_raoI do not fully understand what it means to create a tap-service instance before the monitoring VM is instantiated.06:39
anil_raoIdeally I'd like to see multiple tap-service instances sending traffic to the same destination port (and thereby to the same monitoring VM)06:40
anil_raoHow can we achieve this if every tap-service instance creates its own destination port?06:41
fawadkhaliqSince TaaS interfaces with the Neutron port resource, dependency on VM presence is really outside the scope and it will be hard to enforce such a workflow.06:42
fawadkhaliqFrom user perspective, I don't see how TaaS can enforce it at the code level06:42
anil_raoWell, we cannot deliver traffic to a port that is not consumed by some entity. What am I missing here?06:42
yamamotoanyway let's concentrate to finish "the easy route" right now06:42
fawadkhaliqSo lets say..06:43
fawadkhaliqUser creates a port (not attached to any VM) and then create TaaS service, we will still have the same problem06:43
anil_raoWe can fail tap-service-create if the port is not bound to some host. Just a thought06:43
yamamotofawadkhaliq: right06:44
fawadkhaliqanil_rao: agree and understand the limitation. Do you think from API design perspective we should block it?06:44
anil_raoMy question is this: Someone creates a tap-service instance, there is no consumer of the destination port and tap-flows are attached to it. Where and how to we move packets to the destination port.06:45
fawadkhaliqanil_rao: in the reference implementation, we can return an error from the TaaS backend (agent etc).06:45
fawadkhaliqanil_rao: as you mentioned, requirement would be to make sure port is bound is to something. So an error can raised until it is supported to have update_port implemented as well.06:46
anil_raoWe can return an error but I want to know what folks feel about this situation. Do folks agree that we need a consumer of the destination port for the tap-service to be functional06:46
reedipanil_rao : if we want to limit the use-cases for Mitaka Release, I think we should have a consumer of the port for Tap-service to be operational06:47
anil_raoWhat about the long term solution. I wanted to understand what it means for a (floating) destination port to be associated with a tap-service instance.06:47
reedipfawadkhaliq, yamamoto: what you are saying is correct, but we can update it in the next iteration of TaaS, keeping the following behavior, sort of a limited release.06:48
fawadkhaliqreedip: anil_rao sure, no issues on what we have right now :-)06:48
yamamotofile a bug, document the limitation for now.  i guess it can be fixed by using the existing handle_port callback06:49
fawadkhaliqyamamoto: +106:49
-openstackstatus- NOTICE: A problem with the mirror used for CI jobs in the rax-iad region has been corrected. Please recheck changes that recently failed jobs on nodes in rax-iad.06:49
fawadkhaliqthank you openstackstatus ;-)06:49
anil_raoyamamoto: Can you please describe the workflow for the case where the destination port is not claimed.06:50
yamamotomy expectation for that situation is that packets are just dropped.06:51
fawadkhaliqanil_rao: here is a use-case I can of06:51
fawadkhaliquser create TaaS service with a particular port and it stays static. Operator chooses to move the port around because let's say there is upgrade in the VM (destination) or replacement has to be done. In this case, a simple detach and attach will work without changing anything in TaaS and in the time period when port is not connected, packet will be dropped.06:53
anil_raoyamamoto: We will then also need logic to ensure that we don't mirror (duplicate) packets. Dropping after duplicating can be very wasteful, especially if there are a lot of tap-flows assocaited with a tap-service06:53
fawadkhaliqanil_rao: agree on that and optimization will need to added.06:54
fawadkhaliqto be added*06:54
yamamotoanil_rao: agreed06:55
reedipanil_rao : that is true when considering long term implications06:55
anil_raoI am therefore not seeing the real need for supporting such a scenario. I would sincerely appreciate some reasoning behind going this route. I mean what do we gain from supporting a floating destination port06:55
anil_raoPerhaps we can discuss this later, if necessary. :-)06:56
reedipanil_rao: +1 ( for later discussion as this may be a major use-case )06:56
fawadkhaliqfloating port is an internal concept anyway and no relationship with the API at this point, right?06:56
fawadkhaliqblock can be implemented at the agent layer06:57
reedipfawadkhaliq: I guess yes06:57
anil_raoIf we just look at the API definition that is correct. However, I would like to think that our API represents something more tangible, hence my question. Please pardon me if I am off base here06:57
*** rossella_s has quit IRC06:57
*** rossella_s has joined #openstack-meeting-306:58
anil_raoThere is another thing that I wanted to discuss.06:59
anil_raoI created a DevStack setup, multi-node but I am having problems getting it up. My controller node complains that ovs-ofctl is not found although I don't intend to have the controller node be a part of the dataplane. Does anyone have any ideas of what may be going on?07:00
anil_raoMy local.conf used to work with earlier DevStack versions but not anymore. :-(07:00
vasubabuwhich build07:01
vasubabu?07:01
anil_raoLatest07:01
fawadkhaliqanil_rao: I can share my local.conf, that works for me.07:01
vasubabui am using liberty07:02
anil_raofawadkhaliq: Thanks that would be great.07:02
fawadkhaliqanil_rao: npp, will share shortly07:02
*** hoangcx has joined #openstack-meeting-307:02
anil_raoPlease note that I typically use separate nodes for controller, network and compute since I like to keep the dataplane separate from the controller node.07:03
anil_raoyamamoto: I have a question regarding the local.conf setup for enabling TaaS07:03
yamamoto?07:05
anil_raodoes the instruction in README.rst under "devstack" work for multi-node setups?07:06
*** numans has joined #openstack-meeting-307:07
yamamototaas_openvswitch_agent is only for the compute/network nodes07:07
*** numans has quit IRC07:07
vasubabuREADME.rst should be updated07:08
*** numans has joined #openstack-meeting-307:08
yamamotoand "taas" is for controller07:08
anil_raoyamamoto: OK. Thanks. :-)07:08
yamamotootherwise i expect it works.  but i haven't tried by myself. :-)07:08
*** hdaniel has quit IRC07:09
anil_raoI should get around the DevStack setup issues tomorrow and then I'll have data to report back to the group.07:09
vasubabuanil_rao: i have one question on taas standard tap flows07:10
anil_raovasubabu: Yes?07:10
vasubabuIn Multinode setup, if we bringup instance on compute node all standard tap flows created by taas_agent are getting deleted07:11
vasubabuhave u observe this issue07:11
vasubabu?07:11
anil_raovasubabu:Can you kindly elaborate on "bringup instance on compute node"?07:12
vasubabujust spawn instance07:13
anil_raovasubabu: I have not observed this but I can surely verify this particular case as soon as my new setup is available.07:14
vasubabuit is happening with 1st instance07:14
kazI found this.07:14
kazI have posted on gerrit.07:15
yamamotovasubabu: it sounds like a known "agent uuid cookie" bug07:15
kazyamamoto: yes07:16
yamamotohttps://bugs.launchpad.net/neutron/+bug/152577507:17
openstackLaunchpad bug 1525775 in neutron "When ovs-agent is restarted flows creatd by other than ovs-agent are deleted." [Undecided,In progress] - Assigned to SUZUKI, Kazuhiro (kaz-k)07:17
vasubabuok, is there any work around for this07:18
vasubabu?07:18
vasubabucurrently i am creating all flows using ovs-ofctl07:18
vasubabuagain07:18
*** fawadk has joined #openstack-meeting-307:19
kazI posted workaround for it, but I cannot find the link.07:20
*** fawadkhaliq has quit IRC07:20
anil_raoAny other topics for discussion?07:21
anil_rao#topic open07:22
*** openstack changes topic to "open (Meeting topic: taas)"07:22
fawadksorry I missed a few minutes, whats the plan of action with the spec given its updated to original state07:22
yamamotoanil_rao: can you consider to triage bugs or give a permission to someone?07:23
vasubabuanil_rao: what if user trigger instance migration attached to tap-serivce/tap-flow port07:23
anil_raofawadk: I think one item that needs correction there is the issue of destionation port that we discussed today.07:23
fawadkanil_rao: okay, let's take the discussion on the spec for that.07:24
anil_raoyamamoto: Vinay and I will send eamil to the mailing list with recommendations for some more cores. I think that will help speed things up.07:24
anil_raoWe should get this started in the next day or so.07:24
fawadkanil_rao: great, thanks07:25
yamamotoanil_rao: LP bugs permission doesn't need to be tied to core reviewers.07:25
anil_raoyamamoto: Sure. I agree. Feel free to triage the bugs. I'll do my part too.07:26
yamamotoi don't have a permission to change priority etc07:26
anil_raoWe'll try to get that sorted out as soon as possible.07:27
yamamotoanil_rao: thank you07:27
anil_raodoes anyone have anything new to share regarding the big-tent discussion?07:27
reedipanil_rao: I think as the project is owned by vnyad, therefore, it might be difficult for triaging the bug07:28
anil_raoreedip: We'll get that sorted out.07:28
*** julim has quit IRC07:28
yamamotoanil_rao: studium discussion is still in progress.   https://review.openstack.org/#/c/275888/07:29
anil_raoyamamoto: Thanks. We should all keep an eye out for that discussion07:29
reedipyamamoto: however, this has been merged : https://review.openstack.org/#/c/278025/307:30
anil_raoWe have run out of time. Thanks all.07:30
*** markvoelker has joined #openstack-meeting-307:30
yamamotoreedip: sure07:30
anil_raoLets continue next week.07:30
yamamotobye07:30
*** fawadkhaliq has joined #openstack-meeting-307:30
reediptc07:30
anil_rao#endmeeting07:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"07:30
openstackMeeting ended Wed Feb 17 07:30:38 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-02-17-06.30.html07:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-02-17-06.30.txt07:30
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-02-17-06.30.log.html07:30
*** julim has joined #openstack-meeting-307:30
anil_raoBye!07:30
kazbye07:30
vasubabuby07:30
vasubabue07:30
*** fawadk has quit IRC07:30
fawadkhaliqbye07:31
*** anil_rao has quit IRC07:31
*** vasubabu has quit IRC07:31
*** kzaitsev_mb has joined #openstack-meeting-307:31
*** Poornima has left #openstack-meeting-307:34
*** markvoelker has quit IRC07:34
*** kaz has quit IRC07:35
*** jtomasek has joined #openstack-meeting-307:36
*** kzaitsev_mb has quit IRC07:36
*** JeanBriceCombebi has joined #openstack-meeting-307:44
*** jlanoux has joined #openstack-meeting-307:56
*** e0ne has quit IRC07:56
*** vtech has joined #openstack-meeting-308:10
*** itxaka has joined #openstack-meeting-308:13
*** salv-orlando has joined #openstack-meeting-308:18
*** shwetaap1 has quit IRC08:19
*** fawadkhaliq has quit IRC08:19
*** fawadkhaliq has joined #openstack-meeting-308:20
*** salv-orlando has quit IRC08:20
*** stendulker has joined #openstack-meeting-308:24
*** hdaniel has joined #openstack-meeting-308:26
*** andymaier has joined #openstack-meeting-308:29
*** kzaitsev_mb has joined #openstack-meeting-308:32
*** JeanBriceCombebi has quit IRC08:32
*** mkovacik has quit IRC08:34
*** kzaitsev_mb has quit IRC08:37
*** alexey_weyl has joined #openstack-meeting-308:38
*** eyalb has joined #openstack-meeting-308:39
*** idan_hefetz has joined #openstack-meeting-308:41
*** Nofarsch has joined #openstack-meeting-308:41
*** danoffek has joined #openstack-meeting-308:41
*** ifat_afek has joined #openstack-meeting-308:41
danoffekhi08:41
*** pcaruana has joined #openstack-meeting-308:42
*** matrohon has joined #openstack-meeting-308:43
*** dtardivel has joined #openstack-meeting-308:44
*** eyalb has quit IRC08:46
*** e0ne has joined #openstack-meeting-308:47
*** JeanBriceCombebi has joined #openstack-meeting-308:48
*** alexey_weyl has quit IRC08:50
*** alexey_weyl has joined #openstack-meeting-308:51
*** baohua has joined #openstack-meeting-308:53
*** safchain has joined #openstack-meeting-308:55
*** lhartal has joined #openstack-meeting-308:55
*** eyalb has joined #openstack-meeting-308:58
ifat_afek#startmeeting vitrage09:00
openstackMeeting started Wed Feb 17 09:00:51 2016 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: vitrage)"09:00
openstackThe meeting name has been set to 'vitrage'09:00
eyalbhi09:01
Nofarschhi09:01
idan_hefetzHi09:02
*** mbound has joined #openstack-meeting-309:03
*** mbound has quit IRC09:03
alexey_weylHello all :)09:03
*** mbound has joined #openstack-meeting-309:03
danoffekhi again09:03
*** ayah has joined #openstack-meeting-309:04
*** amir_gur has joined #openstack-meeting-309:04
amir_gurHi09:04
*** lhartal_ has joined #openstack-meeting-309:05
*** lhartal has quit IRC09:05
*** emalin has joined #openstack-meeting-309:05
emalinhi09:05
*** tfukushi_ has joined #openstack-meeting-309:05
ifat_afekHi everyone :-)09:06
ifat_afek#topic Current status09:06
*** openstack changes topic to "Current status (Meeting topic: vitrage)"09:06
*** dedery has joined #openstack-meeting-309:06
ifat_afekHave a look at our wiki page, we added a presentation about vitrage, and we plan to add a demo of nagios alarms later today.09:07
*** tfukushima has quit IRC09:07
ifat_afek#link https://wiki.openstack.org/wiki/Vitrage09:07
ifat_afekWe reviewed our remaining work for mitaka, and split the blueprints between us09:07
ifat_afekBy mitaka-3 we hope  to have rca working, and maybe also deduced alarms09:08
alexey_weylThumbs up :)09:08
ifat_afekWe also want to support update notifications from nova; write the integration with aodh; and implement the entity graph UI09:08
*** Alon has joined #openstack-meeting-309:09
alexey_weylwe plan also to add aodh notification and adding alarms to aodh09:09
*** nelsnels_ has quit IRC09:09
*** lhartal has joined #openstack-meeting-309:09
lhartalhi all09:09
alexey_weylin addition we plan to improve our api handler09:09
Alonhi :)09:09
*** lhartal_ has quit IRC09:09
*** alexey_weyl has quit IRC09:11
*** dedery has quit IRC09:11
*** mkovacik has joined #openstack-meeting-309:11
ifat_afekmy updates: I continued working on nagios synchronizer plugin and its transformer, specifically on unit tests and on the nagios configuration file09:12
*** tshtilma has joined #openstack-meeting-309:12
*** alexey_weyl has joined #openstack-meeting-309:12
ifat_afekI plan to update nagios blueprint with the latest design09:12
ifat_afekRegarding aodh integration: In general, this integration has three parts: 1. get all alarms, 2. register to aodh notifications of alarm changes, 3. notify aodh of vitrage alarms09:13
ifat_afekWe plan to implement 1 and 309:13
ifat_afekNumber 2 is more complex, and vitrage can manage it in mitaka. I plan to finally finish writing aodh blueprints, and ask aodh guys to review them.09:13
ifat_afek#action ifat update aodh blueprints09:13
ifat_afekwho wants to update?09:14
Alonme :)09:14
*** lhartal has quit IRC09:14
idan_hefetzI will09:14
Nofarschme too :)09:14
emalinifat_afek did you mean 2 would be part of mitaka or not ?09:14
*** lhartal has joined #openstack-meeting-309:15
idan_hefetzGo ahead Alon09:15
ifat_afekemalin: 2 probably won't be part of mitaka, since it will take too much time09:15
Alon"Who wants to update ? " -> me09:15
ifat_afekemalin: and we can have vitrage working without it, just with a delay in receiving aodh alarms09:15
AlonWe implemented a "smart table" for the alarms09:16
emalinOk. got it09:16
ifat_afekAlon: go ahead :-)09:16
Alonhttp://lorenzofox3.github.io/smart-table-website/09:16
AlonNow we can Sort + Filter alarms09:16
ifat_afekAlon: please write #link and then the url, so it will appear in the meeting summary09:16
ifat_afeksaw it, it looks great!09:16
Alon#link http://lorenzofox3.github.io/smart-table-website/09:16
AlonAbout the RCA...09:17
*** Adi___ has joined #openstack-meeting-309:17
*** davidsha_ has joined #openstack-meeting-309:17
*** nadav_yakar has joined #openstack-meeting-309:17
AlonWe can already see a dummy mock on a modal window, and yesterday we succeeded to connect and see data from the API (mock data)09:17
AlonThat's all for now. any questions ?09:18
ifat_afekAlon: thanks, sounds great09:18
emalinThat angular library looks very nice09:18
*** alexey_weyl has quit IRC09:18
ifat_afekBTW, we should still define the exact information that should appear in the alarms list.09:18
*** alexey_weyl has joined #openstack-meeting-309:18
ifat_afek#action define what information that should appear in the alarms list09:18
ifat_afekidan_hefetz: you wanted to update?09:19
AlonI prefer the ui-grid, but the Horizon use the Smart-Table09:19
Alon#http://ui-grid.info/09:19
ifat_afekAlon: you forgot #link09:20
Alon#link http://ui-grid.info/09:20
idan_hefetzRegarding the sub-graph matching algorithm, I'll just add a few more tests before pushing the code today09:20
idan_hefetzMy next blueprint is the Aodh-Notifier, a part of the integration with Aodh, to notify aodh of Vitrage alarms.09:20
ifat_afekidan_hefetz: so sub graph matching is finished, all is left are the tests?09:20
*** zhurong has quit IRC09:21
*** alexey_weyl has quit IRC09:21
idan_hefetzyes, so we can close the graph blueprint soon09:21
ifat_afekidan_hefetz: cool!09:21
eyalbI have an update09:21
eyalbI finished the RCA api09:22
eyalbwrote a mock for that09:22
eyalbso the ui team can work on it09:22
*** nkrinner has quit IRC09:22
eyalbI also updated the blueprint for the RCA09:22
*** nkrinner has joined #openstack-meeting-309:22
eyalbwaiting for feedback on the blueprint09:23
*** alexey_weyl has joined #openstack-meeting-309:23
eyalbthats all09:23
ifat_afekeyalb: great. I looked at it and it looks good. also sent it to PinPoint09:23
ayahplease add a  link for the blupring09:23
ifat_afek#link https://review.openstack.org/#/c/243671/609:24
NofarschI'm working on the synchronizer nova plugins for machines, hosts and zones09:24
Nofarsch(for updating)09:25
*** soichi has left #openstack-meeting-309:25
*** davidsha_ has quit IRC09:26
danoffekRPC server is now executed as eventlet instead of threaded. Had to monkey patch it first for t09:26
danoffeki09:26
ifat_afekNofarsch: you mean in addition to the snapshot mode that is already working, right?09:26
Nofarschyes09:26
ifat_afekNofarsch: great09:26
danoffekmonkey patched it for it to be non blocking and "green threaded"09:27
ifat_afekdanoffek: great, thanks09:27
ifat_afekwho else wants to update?09:27
lhartalI have updates09:27
lhartalLast week we had design review meeting for the Evaluator09:28
lhartalThe design included a full flow:09:28
lhartal1. Entity graph updates the evaluator processor09:28
lhartal2. The processor search for the relevant scenarios in the Scenarios Repository and execute sub-graph matching algorithm09:28
lhartal3. the evaluator processes  the sub-graph matching results and executes actions as needed09:29
lhartalAlso we talked about the template loading, its parsing and the scenarios repository09:29
lhartalany questions?09:29
*** baohua has quit IRC09:29
ifat_afeklhartal: sounds good, what's the status of the implementation?09:30
lhartalLast week I implemented the template loader and this week I’m going to work on the scenarios repository09:30
*** markvoelker has joined #openstack-meeting-309:31
lhartalalso we already defined all the intefaces between the different components09:31
ifat_afeklhartal: good. is the design documented? we should have a .rst file with the design09:31
lhartalwe wrote the design. we just need to publish it09:31
ifat_afeklhartal: great, thanks09:32
ifat_afek#action document the evaluator design and add a link to vitrage wiki page09:32
ifat_afekany other updates anyone?09:32
*** amir_gur has quit IRC09:33
ifat_afekalexey_weyl: can you update about the status of the physical plugin static synchronizer?09:33
*** kzaitsev_mb has joined #openstack-meeting-309:33
alexey_weylThe Physical plugin is finished.09:34
alexey_weylIt has tests and it looks good :)09:34
ifat_afekalexey_weyl: great! is it documented?09:34
alexey_weylNot yet09:35
*** markvoelker has quit IRC09:35
ifat_afekalexey_weyl: so please write a .rst file for the configuration files with examples, and then we can put it in our wiki09:35
alexey_weylNo problem :)09:35
ifat_afek#action alexey_weyl document the physical configuration static plugin09:36
ifat_afekany other updates anyone?09:36
ifat_afek#topic Review action items09:37
*** openstack changes topic to "Review action items (Meeting topic: vitrage)"09:37
ifat_afekthere were no action items last week09:37
ifat_afekmoving on...09:37
ifat_afek#topic Next Steps09:37
*** openstack changes topic to "Next Steps (Meeting topic: vitrage)"09:37
ifat_afekwe already talked about our plans for mitaka-309:38
ifat_afek#topic Open Discussion09:38
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"09:38
ifat_afekanyone wants to discuss anything?09:38
*** kzaitsev_mb has quit IRC09:38
ifat_afekso I guess we are done for today09:40
ifat_afekgoodbye everybody09:40
eyalbbye09:40
danoffekbye09:40
*** danoffek has left #openstack-meeting-309:40
Alonbye, Thanks09:40
Nofarschbye :)09:40
*** eyalb has quit IRC09:40
alexey_weylsee ya :)09:41
*** Nofarsch has quit IRC09:41
*** alexey_weyl has quit IRC09:41
ifat_afek#endmeeting09:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:41
openstackMeeting ended Wed Feb 17 09:41:25 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-02-17-09.00.html09:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-02-17-09.00.txt09:41
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-02-17-09.00.log.html09:41
*** emalin has quit IRC09:43
*** davidsha has joined #openstack-meeting-309:44
*** ifat_afek_ has joined #openstack-meeting-309:45
*** Adi___ has quit IRC09:48
*** ifat_afek has quit IRC09:48
*** calbers has quit IRC09:52
*** huats has quit IRC09:52
*** zhenguo_ has quit IRC09:52
*** skath_ has quit IRC09:52
*** miguelgrinberg has quit IRC09:52
*** bryan_att has quit IRC09:52
*** sgordon has quit IRC09:52
*** markmcclain has quit IRC09:52
*** briancurtin has quit IRC09:52
*** pasquier-s has quit IRC09:52
*** bauzas has quit IRC09:52
*** lifeless has quit IRC09:52
*** _fortis has quit IRC09:52
*** GheRivero has quit IRC09:52
*** SotK has quit IRC09:52
*** jraim has quit IRC09:52
*** dougwig has quit IRC09:52
*** sballe has quit IRC09:52
*** kzaitsev_ws has quit IRC09:52
*** ionutbalutoiu has quit IRC09:52
*** JayF has quit IRC09:52
*** zhiyan has quit IRC09:52
*** purp has quit IRC09:52
*** redrobot has quit IRC09:52
*** etoews has quit IRC09:52
*** alanmeadows has quit IRC09:52
*** DinaBelova has quit IRC09:52
*** davidmichaelkarr has quit IRC09:52
*** xgerman has quit IRC09:52
*** scottda has quit IRC09:52
*** j^2 has quit IRC09:52
*** reed has quit IRC09:52
*** Adri2000 has quit IRC09:52
*** amandap has quit IRC09:52
*** blogan has quit IRC09:52
*** mestery has quit IRC09:52
*** melwitt has quit IRC09:52
*** kzaitsev_ws has joined #openstack-meeting-309:52
*** purp has joined #openstack-meeting-309:52
*** redrobot has joined #openstack-meeting-309:52
*** sgordon has joined #openstack-meeting-309:52
*** reed has joined #openstack-meeting-309:52
*** Adri2000 has joined #openstack-meeting-309:52
*** Adri2000 has quit IRC09:52
*** Adri2000 has joined #openstack-meeting-309:52
*** markmcclain has joined #openstack-meeting-309:52
*** lifeless has joined #openstack-meeting-309:53
*** SotK has joined #openstack-meeting-309:53
*** huats has joined #openstack-meeting-309:53
*** blogan has joined #openstack-meeting-309:53
*** redrobot is now known as Guest5316209:53
*** miguelgrinberg has joined #openstack-meeting-309:53
*** pasquier-s has joined #openstack-meeting-309:53
*** melwitt has joined #openstack-meeting-309:53
*** calbers has joined #openstack-meeting-309:53
*** bauzas has joined #openstack-meeting-309:53
*** idan_hefetz has quit IRC09:53
*** mestery has joined #openstack-meeting-309:53
*** DinaBelova has joined #openstack-meeting-309:53
*** mkovacik_ has joined #openstack-meeting-309:53
*** JayF has joined #openstack-meeting-309:53
*** amandap has joined #openstack-meeting-309:54
*** ionutbalutoiu has joined #openstack-meeting-309:55
*** mkovacik has quit IRC09:56
*** kragniz has quit IRC09:56
*** kragniz has joined #openstack-meeting-309:58
*** zhiyan has joined #openstack-meeting-309:58
*** scottda has joined #openstack-meeting-309:58
*** nadav_yakar has quit IRC09:59
*** j^2 has joined #openstack-meeting-309:59
*** zhenguo_ has joined #openstack-meeting-309:59
*** davidmichaelkarr has joined #openstack-meeting-310:00
*** sballe has joined #openstack-meeting-310:00
*** GheRivero has joined #openstack-meeting-310:00
*** xgerman has joined #openstack-meeting-310:01
*** _fortis has joined #openstack-meeting-310:02
*** etoews has joined #openstack-meeting-310:02
*** jraim has joined #openstack-meeting-310:02
*** alanmeadows has joined #openstack-meeting-310:02
*** jraim has quit IRC10:03
*** zhiyan has quit IRC10:03
*** bauzas has quit IRC10:03
*** lhartal has quit IRC10:03
*** vtech has quit IRC10:03
*** rossella_s has quit IRC10:03
*** bswartz has quit IRC10:03
*** vdrok has quit IRC10:03
*** johnthetubaguy has quit IRC10:03
*** vtech has joined #openstack-meeting-310:04
*** briancurtin has joined #openstack-meeting-310:05
*** bauzas_ has joined #openstack-meeting-310:05
*** johnthetubaguy has joined #openstack-meeting-310:05
*** rossella_s has joined #openstack-meeting-310:05
*** salv-orlando has joined #openstack-meeting-310:06
*** egallen has joined #openstack-meeting-310:06
*** dougwig has joined #openstack-meeting-310:07
*** dedery has joined #openstack-meeting-310:07
*** neiljerram has joined #openstack-meeting-310:07
*** skath_ has joined #openstack-meeting-310:07
*** mestery has quit IRC10:08
*** markmcclain has quit IRC10:08
*** stendulker has quit IRC10:08
*** SumitNaiksatam has quit IRC10:08
*** yamamoto has quit IRC10:08
*** jrist has quit IRC10:08
*** iyamahat has quit IRC10:08
*** marios has quit IRC10:08
*** yamahata has quit IRC10:08
*** liangy has quit IRC10:08
*** aignatov has quit IRC10:08
*** mordred has quit IRC10:08
*** ajo has quit IRC10:08
*** maurosr has quit IRC10:08
*** jlvillal has quit IRC10:08
*** marios has joined #openstack-meeting-310:08
*** jrist has joined #openstack-meeting-310:08
*** liangy has joined #openstack-meeting-310:08
*** markmcclain has joined #openstack-meeting-310:08
*** iyamahat has joined #openstack-meeting-310:08
*** stendulker has joined #openstack-meeting-310:08
*** ajo has joined #openstack-meeting-310:08
*** maurosr has joined #openstack-meeting-310:08
*** mestery has joined #openstack-meeting-310:08
*** yamamoto has joined #openstack-meeting-310:08
*** yamahata has joined #openstack-meeting-310:08
*** mordred has joined #openstack-meeting-310:08
*** aignatov has joined #openstack-meeting-310:09
*** bauzas_ is now known as bauzas10:09
*** Guest70049 is now known as tdurakov10:10
*** dedery has quit IRC10:11
*** zhiyan has joined #openstack-meeting-310:12
*** jraim has joined #openstack-meeting-310:13
*** jlvillal has joined #openstack-meeting-310:13
*** salv-orlando has quit IRC10:13
*** kzaitsev_mb has joined #openstack-meeting-310:14
*** vdrok has joined #openstack-meeting-310:14
*** bryan_att has joined #openstack-meeting-310:15
*** vdrok has quit IRC10:17
*** bauzas has quit IRC10:17
*** bauzas has joined #openstack-meeting-310:18
*** andymaier has quit IRC10:18
*** kzaitsev_mb has quit IRC10:18
*** yamahata has quit IRC10:23
*** abalutoiu has joined #openstack-meeting-310:27
*** kaz has joined #openstack-meeting-310:30
*** kaz has quit IRC10:31
*** salv-orlando has joined #openstack-meeting-310:32
*** hoangcx has quit IRC10:32
*** andymaier has joined #openstack-meeting-310:36
*** stanzgy has quit IRC10:45
*** iyamahat has quit IRC10:46
*** dims has joined #openstack-meeting-310:49
*** salv-orlando has quit IRC10:49
*** GheRivero has quit IRC10:49
*** davidmichaelkarr has quit IRC10:49
*** zhenguo_ has quit IRC10:49
*** j^2 has quit IRC10:49
*** sgordon has quit IRC10:49
*** kzaitsev_ws has quit IRC10:49
*** tshtilma has quit IRC10:49
*** dobson has quit IRC10:49
*** flwang has quit IRC10:49
*** DuncanT has quit IRC10:49
*** cgayan has quit IRC10:49
*** lbragstad_ has quit IRC10:49
*** crinkle has quit IRC10:49
*** cfarquhar has quit IRC10:49
*** tmazur has quit IRC10:49
*** alex_xu has quit IRC10:49
*** pkoniszewski has quit IRC10:49
*** ttrifonov has quit IRC10:49
*** sarob has quit IRC10:49
*** vkmc has quit IRC10:49
*** darrenc has quit IRC10:49
*** mikal has quit IRC10:49
*** kfox1111 has quit IRC10:49
*** pshige_____ has quit IRC10:49
*** reedip has quit IRC10:49
*** lbragstad_ has joined #openstack-meeting-310:49
*** mikal has joined #openstack-meeting-310:49
*** cgayan has joined #openstack-meeting-310:49
*** dobson has joined #openstack-meeting-310:49
*** sarob has joined #openstack-meeting-310:49
*** pshige_____ has joined #openstack-meeting-310:49
*** kzaitsev_ws has joined #openstack-meeting-310:50
*** reedip has joined #openstack-meeting-310:50
*** tshtilma has joined #openstack-meeting-310:50
*** sgordon has joined #openstack-meeting-310:50
*** alex_xu has joined #openstack-meeting-310:50
*** vkmc has joined #openstack-meeting-310:51
*** pkoniszewski has joined #openstack-meeting-310:51
*** ttrifonov has joined #openstack-meeting-310:51
*** darrenc has joined #openstack-meeting-310:51
*** tmazur has joined #openstack-meeting-310:52
*** cfarquhar has joined #openstack-meeting-310:52
*** cfarquhar has quit IRC10:52
*** cfarquhar has joined #openstack-meeting-310:52
*** crinkle has joined #openstack-meeting-310:52
*** megm has quit IRC10:53
*** kfox1111 has joined #openstack-meeting-310:54
*** megm has joined #openstack-meeting-310:54
*** GheRivero has joined #openstack-meeting-310:57
*** davidmichaelkarr has joined #openstack-meeting-310:57
*** rossella_s has quit IRC10:57
*** j^2 has joined #openstack-meeting-310:57
*** rossella_s has joined #openstack-meeting-310:58
*** andymaier has quit IRC10:58
*** JeanBriceCombebi has quit IRC11:02
*** DuncanT has joined #openstack-meeting-311:02
*** jlanoux has quit IRC11:02
*** baohua has joined #openstack-meeting-311:02
*** zhenguo_ has joined #openstack-meeting-311:03
*** darrenc has quit IRC11:04
*** vkmc has quit IRC11:04
*** dobson has quit IRC11:04
*** sarob has quit IRC11:04
*** mikal has quit IRC11:04
*** dims has quit IRC11:04
*** zhiyan has quit IRC11:04
*** skath_ has quit IRC11:04
*** briancurtin has quit IRC11:04
*** xgerman has quit IRC11:04
*** sballe has quit IRC11:04
*** scottda has quit IRC11:04
*** JayF has quit IRC11:04
*** blogan has quit IRC11:04
*** reed has quit IRC11:04
*** Adri2000 has quit IRC11:04
*** Guest53162 has quit IRC11:04
*** hdaniel has quit IRC11:04
*** numans has quit IRC11:04
*** ameade has quit IRC11:04
*** clif_h has quit IRC11:04
*** sweston has quit IRC11:04
*** carl_baldwin has quit IRC11:04
*** jed56 has quit IRC11:04
*** kbyrne has quit IRC11:04
*** HenryG has quit IRC11:04
*** eliqiao_ has quit IRC11:04
*** med_ has quit IRC11:04
*** zz_dimtruck has quit IRC11:04
*** leifz has quit IRC11:04
*** toan has quit IRC11:04
*** wendar has quit IRC11:04
*** ozamiatin has quit IRC11:04
*** mugsie has quit IRC11:04
*** elmiko has quit IRC11:04
*** sigmavirus24_awa has quit IRC11:04
*** NikitaKonovalov has quit IRC11:04
*** lbragstad has quit IRC11:04
*** Guest40848 has quit IRC11:04
*** lbragstad_ is now known as lbragstad11:04
*** wendar has joined #openstack-meeting-311:04
*** darrenc has joined #openstack-meeting-311:04
*** redrobot has joined #openstack-meeting-311:04
*** zz_dimtruck has joined #openstack-meeting-311:04
*** hdaniel has joined #openstack-meeting-311:04
*** NikitaKonovalov has joined #openstack-meeting-311:04
*** blogan has joined #openstack-meeting-311:04
*** med_ has joined #openstack-meeting-311:04
*** dims has joined #openstack-meeting-311:04
*** redrobot is now known as Guest185611:04
*** sarob has joined #openstack-meeting-311:04
*** ozamiatin has joined #openstack-meeting-311:04
*** med_ is now known as Guest550611:04
*** GheRivero has quit IRC11:04
*** leifz has joined #openstack-meeting-311:05
*** zz_dimtruck is now known as dimtruck11:05
*** mugsie has joined #openstack-meeting-311:05
*** Guest40848 has joined #openstack-meeting-311:05
*** toan has joined #openstack-meeting-311:05
*** dobson has joined #openstack-meeting-311:05
*** vkmc has joined #openstack-meeting-311:05
*** JayF has joined #openstack-meeting-311:05
*** numans has joined #openstack-meeting-311:05
*** HenryG has joined #openstack-meeting-311:05
*** clif_h has joined #openstack-meeting-311:05
*** vkmc has quit IRC11:05
*** vkmc has joined #openstack-meeting-311:05
*** stendulker_ has joined #openstack-meeting-311:06
*** lbragstad_ has joined #openstack-meeting-311:06
*** sdague has joined #openstack-meeting-311:06
*** _fortis has quit IRC11:06
*** eliqiao_ has joined #openstack-meeting-311:06
*** stendulker has quit IRC11:07
*** reed has joined #openstack-meeting-311:07
*** kbyrne has joined #openstack-meeting-311:07
*** sigmavirus24_awa has joined #openstack-meeting-311:08
*** dedery has joined #openstack-meeting-311:08
*** mikal has joined #openstack-meeting-311:09
*** elmiko has joined #openstack-meeting-311:09
*** Adri2000 has joined #openstack-meeting-311:09
*** ameade has joined #openstack-meeting-311:11
*** tfukushi_ has quit IRC11:12
*** dedery has quit IRC11:13
*** cartik has quit IRC11:13
*** stendulker_ has quit IRC11:14
*** scottda has joined #openstack-meeting-311:15
*** carl_baldwin has joined #openstack-meeting-311:15
*** GheRivero has joined #openstack-meeting-311:15
*** sballe has joined #openstack-meeting-311:15
*** skath_ has joined #openstack-meeting-311:15
*** zhiyan has joined #openstack-meeting-311:16
*** xgerman has joined #openstack-meeting-311:17
*** briancurtin has joined #openstack-meeting-311:18
*** sweston has joined #openstack-meeting-311:18
*** jed56 has joined #openstack-meeting-311:18
*** kzaitsev_mb has joined #openstack-meeting-311:18
*** _fortis has joined #openstack-meeting-311:19
*** ifat_afek has joined #openstack-meeting-311:23
*** ifat_afek has left #openstack-meeting-311:24
*** baojg has quit IRC11:24
*** ayah has quit IRC11:24
*** ifat_afek_ has quit IRC11:25
*** jlanoux has joined #openstack-meeting-311:28
*** markvoelker has joined #openstack-meeting-311:31
*** yamamoto has quit IRC11:32
*** reedip_ has joined #openstack-meeting-311:36
*** markvoelker has quit IRC11:36
*** robcresswell has joined #openstack-meeting-311:39
*** reedip_ has quit IRC11:39
*** kbyrne has quit IRC11:39
*** reed has quit IRC11:39
*** lbragstad_ has quit IRC11:39
*** ozamiatin has quit IRC11:39
*** crinkle has quit IRC11:39
*** tmazur has quit IRC11:39
*** aignatov has quit IRC11:39
*** melwitt has quit IRC11:39
*** SotK has quit IRC11:39
*** mbound has quit IRC11:39
*** killer_prince has quit IRC11:39
*** ALUvial has quit IRC11:39
*** pavel_bondar has quit IRC11:39
*** krotscheck has quit IRC11:39
*** alazarev has quit IRC11:39
*** dmowrer has quit IRC11:39
*** devananda has quit IRC11:39
*** mrunge has quit IRC11:39
*** yasui has quit IRC11:39
*** john5223 has quit IRC11:39
*** pl0pix has quit IRC11:39
*** mdbooth has quit IRC11:39
*** toddjohn has quit IRC11:39
*** peterstac has quit IRC11:39
*** lbragstad_ has joined #openstack-meeting-311:40
*** reed has joined #openstack-meeting-311:40
*** plopix has joined #openstack-meeting-311:40
*** mrunge has joined #openstack-meeting-311:40
*** kbyrne has joined #openstack-meeting-311:40
*** tmazur has joined #openstack-meeting-311:40
*** killer_prince has joined #openstack-meeting-311:40
*** alazarev has joined #openstack-meeting-311:40
*** peterstac has joined #openstack-meeting-311:40
*** toddjohn has joined #openstack-meeting-311:40
*** dmowrer has joined #openstack-meeting-311:40
*** ozamiatin has joined #openstack-meeting-311:40
*** yasui has joined #openstack-meeting-311:40
*** melwitt has joined #openstack-meeting-311:40
*** devananda has joined #openstack-meeting-311:40
*** pavel_bondar has joined #openstack-meeting-311:40
*** aignatov has joined #openstack-meeting-311:40
*** ALUvial has joined #openstack-meeting-311:40
*** mbound has joined #openstack-meeting-311:41
*** reedip_ has joined #openstack-meeting-311:41
*** mdbooth has joined #openstack-meeting-311:41
*** crinkle has joined #openstack-meeting-311:41
*** krotscheck has joined #openstack-meeting-311:42
*** killer_prince has quit IRC11:44
*** SotK has joined #openstack-meeting-311:46
*** dixiaoli has joined #openstack-meeting-311:47
*** mbound has quit IRC11:50
*** aignatov has quit IRC11:50
*** HenryG has quit IRC11:50
*** hdaniel has quit IRC11:50
*** baohua has quit IRC11:50
*** neiljerram has quit IRC11:50
*** ionutbalutoiu has quit IRC11:50
*** mkovacik_ has quit IRC11:50
*** itxaka has quit IRC11:50
*** jtomasek has quit IRC11:50
*** julim has quit IRC11:50
*** tdurakov has quit IRC11:50
*** bapalm has quit IRC11:50
*** toabctl has quit IRC11:50
*** sheeprine has quit IRC11:50
*** todin has quit IRC11:50
*** jcook has quit IRC11:50
*** obondarev has quit IRC11:50
*** dloi has quit IRC11:50
*** abramley has quit IRC11:50
*** anteaya has quit IRC11:50
*** doffm has quit IRC11:50
*** SotK_ has quit IRC11:50
*** rhagarty_ has quit IRC11:50
*** ^Gal^ has quit IRC11:50
*** galstrom_zzz has quit IRC11:50
*** notmyname has quit IRC11:50
*** todin has joined #openstack-meeting-311:50
*** doffm has joined #openstack-meeting-311:50
*** galstrom_zzz has joined #openstack-meeting-311:50
*** ionutbalutoiu has joined #openstack-meeting-311:50
*** baohua has joined #openstack-meeting-311:50
*** sheeprine has joined #openstack-meeting-311:50
*** SotK_ has joined #openstack-meeting-311:50
*** itxaka has joined #openstack-meeting-311:50
*** neiljerram has joined #openstack-meeting-311:50
*** anteaya has joined #openstack-meeting-311:50
*** abramley has joined #openstack-meeting-311:50
*** bapalm has joined #openstack-meeting-311:50
*** mkovacik_ has joined #openstack-meeting-311:50
*** aignatov has joined #openstack-meeting-311:50
*** tdurakov has joined #openstack-meeting-311:51
*** hdaniel has joined #openstack-meeting-311:51
*** mbound has joined #openstack-meeting-311:51
*** julim has joined #openstack-meeting-311:51
*** jtomasek has joined #openstack-meeting-311:51
*** toabctl has joined #openstack-meeting-311:51
*** notmyname has joined #openstack-meeting-311:51
*** dloi has joined #openstack-meeting-311:51
*** HenryG has joined #openstack-meeting-311:51
*** jcook has joined #openstack-meeting-311:51
*** obondarev has joined #openstack-meeting-311:52
*** ^Gal^ has joined #openstack-meeting-311:52
*** SotK_ has quit IRC11:54
*** rhagarty has joined #openstack-meeting-311:55
*** tsufiev has joined #openstack-meeting-311:58
*** tsufiev has quit IRC11:58
*** doug-fish has joined #openstack-meeting-311:58
*** openstack has joined #openstack-meeting-312:04
*** breton has joined #openstack-meeting-312:04
*** pleia2 has joined #openstack-meeting-312:04
robcresswellRight, lets continue anyway.12:04
robcresswellOnly notice is a reminder about deadlines12:05
*** igordcard_ has joined #openstack-meeting-312:05
*** tonyb has joined #openstack-meeting-312:05
robcresswell2 weeks today12:05
robcresswellUntil M-3 releases. We need to make sure bps are complete and ready for review. Start pestering cores if you need to.12:06
itxakayay, pestering cores \o/12:06
*** sdake has joined #openstack-meeting-312:06
robcresswellAny other notices before we move on to the agenda?12:06
betherlyyay IRC has let me into the meeting!12:06
*** hogepodge has quit IRC12:07
robcresswell#link https://wiki.openstack.org/wiki/Meetings/Horizon#Agenda_for_2016-02-17_12_UTC12:07
robcresswell#topic d_o_a stable releases for kilo/liberty12:08
robcresswellUrgh none of this is going to work is it.12:08
doug-fish:-)12:08
robcresswellmrunge: You're up :)12:08
mrungeuhm, on a call currently12:08
mrungeitxaka12:08
mrunge?12:09
itxakayeah12:09
*** dedery has joined #openstack-meeting-312:09
robcresswellitxaka, can you speak about the agenda items?12:09
itxakabasically regarding the patches linked in the agenda, tsufiev showed concern on the release timing for them12:09
*** _fortis has joined #openstack-meeting-312:09
itxakaand its a concern that we should all share12:09
tsufievitxaka, me?12:10
itxakadoa should make a stable release for kilo and liberty12:10
tsufievitxaka, ah, got it12:10
tsufievyes, I did :)12:10
itxakaand then a horizon liberty/kilo release should also follow with a new constraint on doa version to avoid any issues12:10
*** coolsvap is now known as coolsvap|away12:11
*** piet has quit IRC12:12
*** AJaeger has joined #openstack-meeting-312:12
*** AJaeger has left #openstack-meeting-312:12
itxakabasically a horizon patch needs a specific new doa version with some backports already merged or it will introduce a known bug12:12
robcresswellSounds reasonable12:13
*** dedery has quit IRC12:13
*** piet has joined #openstack-meeting-312:13
mrungethis reads to me like: release a now doa version for kilo, then increase global requirements and then finally patch horizon12:13
itxakaso Im guessing release new doa version for kilo/liberty -> bump the requirements for doa in horizon kilo/liberty -> release new horizon version for kilo/liberty12:13
*** GheRivero has joined #openstack-meeting-312:13
*** JoshNang has joined #openstack-meeting-312:13
itxakaI dont have it very clear how the release process works and so on, so thats the main concern for me12:14
mrungedoes anyone of you have other patches in the queue for doa in kilo/liberty?12:14
mrungeitxaka, either david-lyle or I should take care of that12:15
robcresswellBest people to speak to are david-lyle and lhcheng12:15
*** piet has quit IRC12:15
itxakareleasing the doa version should be no problem thanks to a david-lyle patch that fixes backwards compatibility https://review.openstack.org/#/q/topic:bug/152657212:15
mrungeworst thing with releases is, process changes from release to release12:15
robcresswellAs as we're careful, I don't imagine there should be any huge issues. It's just a stable bugfix release.12:16
mrungehttps://wiki.openstack.org/wiki/ReleaseTeam/How_To_Release12:16
robcresswellfamous last words...12:16
*** Guest45178 has quit IRC12:17
mrungeI'd be tagging doa release tomorrow then, if nothing else comes up12:17
itxakaI think the workflow of doa -> bump reqs in horizon -> horizon should alliviate any concers tsufiev ?12:18
tsufievitxaka, no, just a little note: bump reqs in openstack/requirements, not in horizon12:18
tsufievthen proposal bot will propose a requirements patch into horizon12:19
*** sankarshan_away is now known as sankarshan12:19
itxakasounds good to me12:19
itxakamrunge, this affects the liberty branch as well, patches are all merged in liberty (doa and horizon)12:20
mrungeack12:20
*** piet has joined #openstack-meeting-312:20
*** dansmith has joined #openstack-meeting-312:20
*** dansmith is now known as Guest1430412:20
*** k-ishii_ has joined #openstack-meeting-312:20
*** jaypipes has joined #openstack-meeting-312:21
*** vgridnev has joined #openstack-meeting-312:21
robcresswellThat's the only agenda items12:21
robcresswellSo: open discussion12:22
*** piet has quit IRC12:22
*** piet has joined #openstack-meeting-312:22
robcresswellAnyone have any topics? Or we can have some time back :)12:24
mrungemasco?12:24
mrungesigh12:24
*** rhagarty has quit IRC12:24
*** devananda has quit IRC12:24
*** kzaitsev_mb has quit IRC12:24
*** clif_h has quit IRC12:24
*** numans has quit IRC12:24
*** DuncanT has quit IRC12:24
*** ttrifonov has quit IRC12:24
*** sgordon has quit IRC12:24
*** ajo has quit IRC12:24
*** vtech has quit IRC12:24
*** alanmeadows has quit IRC12:24
*** kragniz has quit IRC12:24
*** calbers has quit IRC12:24
*** DinaBelova has quit IRC12:24
*** nkrinner has quit IRC12:24
*** markvan_ has quit IRC12:24
*** sergek has quit IRC12:24
*** d0ugal has quit IRC12:24
*** andreaf has quit IRC12:24
*** stevemar has quit IRC12:24
*** eliqiao has quit IRC12:24
*** cgoncalves has quit IRC12:24
*** sreshetn1ak has quit IRC12:24
*** sc` has quit IRC12:24
*** njohnston has quit IRC12:24
*** russellb has quit IRC12:24
*** jroll has quit IRC12:24
*** fungi has quit IRC12:24
*** jhesketh has quit IRC12:24
*** zigo has quit IRC12:24
*** sankarshan has quit IRC12:24
*** kzaitsev_mb has joined #openstack-meeting-312:25
*** sc` has joined #openstack-meeting-312:25
*** sreshetnyak has joined #openstack-meeting-312:25
*** sankarshan has joined #openstack-meeting-312:25
*** clif_h has joined #openstack-meeting-312:25
*** markvan has joined #openstack-meeting-312:25
*** sgordon has joined #openstack-meeting-312:25
*** jroll has joined #openstack-meeting-312:25
*** andreaf has joined #openstack-meeting-312:25
*** numans has joined #openstack-meeting-312:25
*** rhagarty has joined #openstack-meeting-312:25
*** njohnston has joined #openstack-meeting-312:25
*** kragniz has joined #openstack-meeting-312:25
*** DinaBelova has joined #openstack-meeting-312:25
*** markvan has quit IRC12:25
*** markvan has joined #openstack-meeting-312:25
r1chardj0n3shum, I disappeared for a bit there12:25
*** devananda has joined #openstack-meeting-312:25
*** stevemar has joined #openstack-meeting-312:25
r1chardj0n3shope I didn't miss anything12:25
*** vtech has joined #openstack-meeting-312:25
*** cgoncalves has joined #openstack-meeting-312:25
*** nkrinner has joined #openstack-meeting-312:25
*** fungi has joined #openstack-meeting-312:25
*** nkrinner has quit IRC12:25
*** nkrinner has joined #openstack-meeting-312:25
*** ajo has joined #openstack-meeting-312:25
*** numans has quit IRC12:25
*** numans has joined #openstack-meeting-312:25
*** rhagarty has quit IRC12:25
*** rhagarty has joined #openstack-meeting-312:25
*** russellb has joined #openstack-meeting-312:25
*** d0ugal has joined #openstack-meeting-312:25
*** ajo has quit IRC12:25
*** ajo has joined #openstack-meeting-312:25
mrungenot really, r1chardj0n3s12:25
*** zigo has joined #openstack-meeting-312:26
robcresswellNothing much12:26
*** jhesketh has joined #openstack-meeting-312:26
robcresswellAnything you wanted to discuss? Otherwise I'm gonna call it12:26
r1chardj0n3smight be worthwhile reminding folks of https://etherpad.openstack.org/p/horizon-mitaka-midcycle12:26
mrungecall it then...12:26
*** piet has quit IRC12:26
*** ttrifonov has joined #openstack-meeting-312:26
r1chardj0n3sreckon we might have a busy enough few days just trying to move code thru that's in play12:26
r1chardj0n3sbut just in case there's something you'd like to talk about12:26
r1chardj0n3s(like angular patch size ;-)12:27
*** yamamoto has joined #openstack-meeting-312:27
robcresswellYeah, I think we'll be focusing on paired coding and reviews it seems12:27
*** masco has joined #openstack-meeting-312:27
mrungeoh, would it be possible to loop external folks in to midcycle?12:27
r1chardj0n3salso, there's a global bugbash coming up12:27
*** calbers has joined #openstack-meeting-312:27
mrungeangular patch size is indeed a concern of mine12:27
robcresswellhttps://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka12:27
r1chardj0n3sthanks robcresswell12:28
robcresswellGood point. So this is very similar to our Horizon bug days12:28
r1chardj0n3sfeel free to pop over to Sydney and smash some bugs with us ... or go somewhere more local ;-)12:28
robcresswellIt would be good to get involved in the bug day. I'll be at the London location for at least a couple of the days12:28
r1chardj0n3srobcresswell: say hi to Alex, who just joined the London office from Brisbane. She says it's cold over there. Who'd have thought.12:29
*** yamamoto_ has joined #openstack-meeting-312:29
*** plopix has quit IRC12:29
robcresswellHa, bad decision :p12:29
r1chardj0n3sanyway, I don't have anything further, thanks12:30
r1chardj0n3sgoing to bed before midnight sounds nice12:30
mrungemasco, you had something to discuss?12:30
mrungehttps://review.openstack.org/#/c/255854/#12:30
mascomrunge, https://review.openstack.org/#/c/255854/ i need ppl opinion on this12:31
mascooh you are faster then me12:31
mrungehr hr hr12:31
*** yamamoto has quit IRC12:31
mrungewith that being said, I have to leave, unfortunately :P12:31
*** natorious_ has joined #openstack-meeting-312:32
*** sarob_ has joined #openstack-meeting-312:32
*** leifz- has joined #openstack-meeting-312:32
*** elmiko has quit IRC12:32
*** sdague has quit IRC12:32
*** leifz has quit IRC12:32
*** dimtruck has quit IRC12:32
*** NikitaKonovalov has quit IRC12:32
*** sarob has quit IRC12:32
*** Guest5506 has quit IRC12:32
*** pkoniszewski has quit IRC12:32
*** pshige_____ has quit IRC12:32
*** bryan_att has quit IRC12:32
*** jlvillal has quit IRC12:32
*** jraim has quit IRC12:32
*** jrist has quit IRC12:32
*** marios has quit IRC12:32
*** etoews has quit IRC12:32
*** amandap has quit IRC12:32
*** miguelgrinberg has quit IRC12:32
*** safchain has quit IRC12:32
*** e0ne has quit IRC12:32
*** dtardivel has quit IRC12:32
*** lekha has quit IRC12:32
*** tpeoples has quit IRC12:32
*** jwang__ has quit IRC12:32
*** krtaylor has quit IRC12:32
*** SergeyLukjanov has quit IRC12:32
*** otherwiseguy has quit IRC12:32
*** pkarikh has quit IRC12:32
*** davidlenwell has quit IRC12:32
*** eglute has quit IRC12:32
*** natorious has quit IRC12:32
*** eglute_s has joined #openstack-meeting-312:32
*** zz_dimtruck has joined #openstack-meeting-312:32
mrungeit was about to collect feedback, thoughts etc.12:32
*** pkarikh_ has joined #openstack-meeting-312:32
*** natorious_ is now known as natorious12:32
*** leifz- is now known as leifz12:32
*** sarob_ is now known as sarob12:32
mrungeit seems to be a good addition, but some disagreement on implementation12:32
*** zz_dimtruck is now known as dimtruck12:32
*** safchain has joined #openstack-meeting-312:32
*** elmiko has joined #openstack-meeting-312:32
*** jwang__ has joined #openstack-meeting-312:32
*** krtaylor_ has joined #openstack-meeting-312:32
*** elmiko has quit IRC12:32
*** elmiko has joined #openstack-meeting-312:32
*** NikitaKonovalov has joined #openstack-meeting-312:32
robcresswellmasco: Just reading12:32
*** marios has joined #openstack-meeting-312:32
*** e0ne has joined #openstack-meeting-312:32
*** jrist has joined #openstack-meeting-312:32
*** jrist has joined #openstack-meeting-312:32
*** davidlenwell has joined #openstack-meeting-312:33
*** pshige_____ has joined #openstack-meeting-312:33
*** med_ has joined #openstack-meeting-312:33
*** yamamoto_ has quit IRC12:33
*** sdague has joined #openstack-meeting-312:33
*** med_ is now known as Guest3757012:33
*** pkoniszewski has joined #openstack-meeting-312:33
robcresswellYep reading comments12:34
doug-fishDavid's suggestion seems good to me - does somebody not like that?12:34
tsufievmasco, btw, what are your further plans on https://review.openstack.org/#/c/261930/ ?12:34
*** jlvillal has joined #openstack-meeting-312:34
mascoi hope performance wise there will not be much problem12:34
mascotsufiev, i think instead of deleting the field just hiding will help. am i right?12:35
tsufievmasco, yes, should be a good approach12:35
*** davidsha has quit IRC12:35
mascosince integration needs the shared field12:35
* tsufiev wonders why he didn't think about it12:35
mascook will submit a patch for that12:36
tsufievmasco, awesome :)12:36
*** otherwiseguy has joined #openstack-meeting-312:36
mascotsufiev, :) even i too got this today12:36
robcresswellEr, why is an individual user get memoized?12:36
*** miguelgrinberg has joined #openstack-meeting-312:36
robcresswellJust scanning.12:36
*** vgridnev_ has joined #openstack-meeting-312:36
*** SergeyLukjanov has joined #openstack-meeting-312:37
*** amandap has joined #openstack-meeting-312:37
robcresswellI mean this seems like the memoized part is irrelevant if you're making multiple individual calls12:37
robcresswellthe id would change, no?12:37
mascorobcresswell, can change12:38
mascoi mean for different users12:38
robcresswellIt seems like it would be poor peformance would it not? just making api calls for each user12:38
*** vgridnev has quit IRC12:38
robcresswellAs David noted.12:39
mascoyes, if each user is different12:39
*** Alon has quit IRC12:39
robcresswellI guess it depends on no. of users per instance. Hmm..12:39
mascobut practically it won't12:39
robcresswellYeah, it shouldnt be huge.12:40
*** atuvenie has joined #openstack-meeting-312:40
mascoyes12:40
mascoso no worry for performance ;)12:40
*** baojg has joined #openstack-meeting-312:40
*** r1chardj0n3s is now known as r1chardj0n3s_afk12:41
robcresswellBetter speak with david then :)12:41
*** DuncanT has joined #openstack-meeting-312:41
mascorobcresswell, sure. thanks. please add your points on it.12:41
mascoit will help for future reference :)12:42
*** rtheis has joined #openstack-meeting-312:43
robcresswellAnyone else with discussion points?12:44
robcresswellmasco: Sure12:44
*** sergek has joined #openstack-meeting-312:44
robcresswellWe'll end the meeting there, have 15 mins back :)12:45
mascoi don't have anything specific. but i just want request the core to review my QoS patches :)12:45
*** etoews has joined #openstack-meeting-312:46
*** yamamoto has joined #openstack-meeting-312:50
*** baoli has joined #openstack-meeting-312:50
*** alanmeadows has joined #openstack-meeting-312:51
*** baoli has quit IRC12:51
*** tpeoples has joined #openstack-meeting-312:51
*** jraim has joined #openstack-meeting-312:51
*** sweston has quit IRC12:53
*** dougwig has quit IRC12:53
*** lblanchard has joined #openstack-meeting-312:55
*** dtardivel has joined #openstack-meeting-312:56
*** sagar_nikam has joined #openstack-meeting-312:58
*** ^Gal^ has quit IRC12:59
*** itoader has joined #openstack-meeting-312:59
*** piet has joined #openstack-meeting-312:59
*** robcresswell has left #openstack-meeting-312:59
*** claudiub has joined #openstack-meeting-313:01
atuvenieo/13:01
sagar_nikamHi All13:01
*** lpetrut has joined #openstack-meeting-313:01
*** betherly has left #openstack-meeting-313:01
abalutoiuo/13:02
alexpilotti#startmeeting hyper-v13:02
openstackMeeting started Wed Feb 17 13:02:17 2016 UTC and is due to finish in 60 minutes.  The chair is alexpilotti. Information about MeetBot at http://wiki.debian.org/MeetBot.13:02
lpetruthi13:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
openstackThe meeting name has been set to 'hyper_v'13:02
claudiubo/13:02
abalutoiuhello13:02
sagar_nikamHi13:02
itoaderhi13:02
itoadero/13:03
alexpilottihey folks13:03
alexpilotti#topic networing-hyperv patches13:03
alexpilottiso most patches got approved13:03
*** masco has left #openstack-meeting-313:04
sagar_nikamnice13:04
alexpilottiwe have only Sonu's patch pending13:04
claudiub^ merged.13:04
alexpilottiSOnu's one too? perfect13:04
*** lekha has joined #openstack-meeting-313:05
alexpilottiI saw your comments yesterday, but I didnt see the merge yet, great13:05
*** piet has quit IRC13:05
*** piet has joined #openstack-meeting-313:06
alexpilottiwe have this one open: #link https://review.openstack.org/#/c/264235/13:06
*** kzaitsev_mb has quit IRC13:07
*** eliqiao has joined #openstack-meeting-313:07
*** kvinod_ has joined #openstack-meeting-313:07
claudiubit was approved yesterday, but jenkins said no. ammended, reapproved.13:07
kvinod_Hi all13:08
alexpilottiit's at top of the zuul queue now13:08
*** piet has quit IRC13:08
alexpilottiso should merge during the meeting, hopefully :)13:08
alexpilottiok that clears the networking-hyperv topic13:08
*** eliqiao has quit IRC13:08
alexpilottianything to add?13:08
kvinod_sorry to ask, but are we talking about neutron patches13:09
sagar_nikamyes kvinod_:13:09
*** kvinod_ has quit IRC13:10
*** itoader has quit IRC13:10
*** sagar_nikam has quit IRC13:10
*** k-ishii_ has quit IRC13:10
*** abalutoiu has quit IRC13:10
alexpilottinetworking-hyperv patches13:10
alexpilottiwe said that everything got approved13:11
*** kvinod has joined #openstack-meeting-313:13
*** sagar_nikam has joined #openstack-meeting-313:14
alexpilottisagar_nikam, kvinod: ping13:14
sagar_nikamalexpilotti: got disconnected13:14
sagar_nikamback again13:14
kvinodi m back13:14
kvinodsorry internet issue13:14
kvinodso are we still on bug discussion topic13:15
*** itoader has joined #openstack-meeting-313:15
*** andymaier has joined #openstack-meeting-313:15
kvinodif so wanted to know when we are planning to get Enhanced RPC and Native thread patch merged13:15
alexpilottiok13:15
alexpilottikvinod: they all merged13:16
*** baoli has joined #openstack-meeting-313:16
*** banix has joined #openstack-meeting-313:16
kvinodok cool13:16
alexpilottikvinod: that was the initial discussion topic13:16
alexpilottikvinod: anything to add?13:16
*** abalutoiu_ has joined #openstack-meeting-313:16
kvinodnothing thanks13:17
*** fawadkhaliq has quit IRC13:17
alexpilottinext13:17
alexpilotti#topic SG / VLAN random false outcome issue13:18
alexpilottiabalutoiu_ is working on isolating the issue in a script to send to the MSFT product team13:18
alexpilottiI'm stressing out the fact that this is a major issue13:19
*** yamamoto has quit IRC13:19
alexpilottias at the current stage we have a race condition not knowing if VLAN settings and or / SG are applied or not13:20
alexpilottihappens very rarely, but during rally tests is the main reason for failures13:20
alexpilottianything to add?13:20
*** dims_ has joined #openstack-meeting-313:20
alexpilottiif not we can move on13:20
*** dims has quit IRC13:21
alexpilotti#topic Hyper-V cluster13:21
*** banix has quit IRC13:22
alexpilottiatuvenie: would you like to give a status update?13:22
atuvenieyeah13:22
atuvenieso the patches are up, we support smb volumes13:22
*** dedery has joined #openstack-meeting-313:22
atuvenieand ovs (though I'm still not where I want with testing that )13:22
*** abalutoiu has joined #openstack-meeting-313:23
*** flwang has joined #openstack-meeting-313:23
atuvenieI have some tempest tests in my env, planning on writing some more so we don't have to do things manually13:23
sagar_nikamatuvenie: can you share the patches13:24
atuvenie2 sec13:24
atuvenie#link https://review.openstack.org/#/c/281115/13:24
atuvenieand the one related13:24
*** yamamoto has joined #openstack-meeting-313:25
atuveniethe unit tests fail because of the related os-win patches are not in yet13:25
atuvenieos-win one #https://review.openstack.org/#/c/276190/13:25
sagar_nikamok13:25
atuvenieneeds to be updated with some fixes13:25
sagar_nikamsoem questions on cluster driver, if i can ask now13:26
atuvenieyeah13:26
sagar_nikamthe last time when we saw the patch submitted by claudiub: that patch did not handle the nova DB update when MSCluster moves the VM to another host13:26
sagar_nikamhope this patch has a fix for that13:27
atuvenieyes of course13:27
sagar_nikamok13:27
atuvenieevery time the instance is moved to a new host, the instance object is updated and saved in the DB13:27
sagar_nikamand since the nova DB gets updated ... we can trigger other nova operations like start/stop etc on the moved VM13:27
sagar_nikamit should work13:28
sagar_nikamcould you try that ?13:28
atuveniestart / stop on a moved vm?13:28
atuvenieof course13:28
sagar_nikamyes moved vm13:28
sagar_nikamok, thanks13:29
*** markvoelker has joined #openstack-meeting-313:29
*** bswartz has joined #openstack-meeting-313:29
*** kzaitsev_mb has joined #openstack-meeting-313:29
*** dims_ has quit IRC13:29
sagar_nikamwe can test it, only issue ... we are on liberty. alexpilotti: any chance of a patch which backports the mitaka patch to liberty ?13:30
alexpilottisagar_nikam: about cluster? It's not on our plans as part of our community engagement at the moment13:30
alexpilottiwe are planning to do if any of our customers ask for it13:31
sagar_nikamok13:31
sagar_nikamwe may move to mitaka after couple on months, we will test it as soon as we move13:32
*** vgridnev_ has quit IRC13:32
alexpilottimakes sense13:32
alexpilottianything else on this topic?13:32
*** vgridnev has joined #openstack-meeting-313:32
sagar_nikamis it very difficult to backport ? are there too many changes apart from os-win ?13:33
alexpilottithere are some significant changes in Nova and the Hyper-V driver13:34
sagar_nikamok13:34
sagar_nikamwe will test it as soon as we move to Mitaka13:34
sagar_nikamwill let you know when we start13:34
alexpilottiit's not too difficult but surely not trivial13:34
sagar_nikamok13:35
sagar_nikamin case you do it for any customer, let us know, we can test and provide feedback13:35
alexpilottisure, thanks!13:35
alexpilottimoving on13:35
alexpilotti#topic Hyper-V shielded VM13:36
*** dedery has quit IRC13:36
alexpilottithis is another one of the major topics for Hyper-V in 201613:36
alexpilottiwe're working on it since quite a bit13:37
alexpilottiitoader is quite well into the implementation and we'll have the patches ready for review quite soon13:37
alexpilottisagar_nikam is this something you guys are looking to have?13:38
*** pavel_bondar has quit IRC13:38
sagar_nikamis it in WIN 2016  server version ?13:38
alexpilotti2016 on any SKU13:38
sagar_nikamas of now we dont have WIN 2016 yet13:38
*** yamamoto has quit IRC13:38
alexpilottiI mean, server SKU13:39
sagar_nikambut yes, we would be intrested13:39
*** vgridnev_ has joined #openstack-meeting-313:39
sagar_nikamwhenever we move to WIN 201613:39
sagar_nikamis there a BP13:39
sagar_nikamhave not seen it13:39
alexpilottiwe're waiting to send the updated BP spec13:40
sagar_nikamok, let us know when the spec is ready13:40
alexpilottias we prefer to wait for the next 2016 public preview13:40
sagar_nikamwe will check it13:40
sagar_nikamalso can you provide us the link from where we can get WIN 201613:41
alexpilottiin order to avoid surprises in the feature's behaviour that require changes in the BP itself13:41
sagar_nikamok, got it, TP5 ?13:41
sagar_nikamwill it have the details13:41
itoader With ws2016 comes the feature of vtpm which works as a virtual tmp for a vm. By adding a vtpm to a vm, there is the shielding option which based on some attestations, it allows only specific hosts to have access to that vm.13:41
*** fawadkhaliq has joined #openstack-meeting-313:42
alexpilotti#link https://www.microsoft.com/en-us/evalcenter13:42
*** vgridnev has quit IRC13:42
alexpilottithe current TP4 preview is available here ^13:43
sagar_nikamok13:43
sagar_nikamany idea when is TP5 ?13:43
*** yamamoto has joined #openstack-meeting-313:43
*** doug-fish has quit IRC13:44
alexpilottinothing that I can comment publicly unfortunately :)13:44
alexpilottido you guys have any topic that you'd like to add to the agenda today?13:44
*** dhellmann has quit IRC13:44
*** dims has joined #openstack-meeting-313:45
sagar_nikamok13:45
sagar_nikamfreerdp13:45
sagar_nikamcan we discuss that, had some questions13:45
*** dhellmann has joined #openstack-meeting-313:47
alexpilottisure13:47
alexpilotti#topic FreeRDP13:47
sagar_nikamlast meeting we started on it and could not complete13:48
sagar_nikamfreerdp-webconnect13:48
sagar_nikamis what we need13:48
sagar_nikamin hyperv13:48
*** reedip_ has quit IRC13:48
sagar_nikamit can be installed on linux and windows13:48
sagar_nikamwhat is the recommended option13:48
alexpilotticorrect13:48
*** sankarshan is now known as sankarshan_away13:49
alexpilottiwe do most of the testing on Windows13:49
sagar_nikamok13:49
alexpilottialso the binary release that we distribute is for Windows13:49
sagar_nikamis linux version stable ?13:49
*** tsufiev has left #openstack-meeting-313:50
alexpilottisaid that, we are constantly working on ensuring that wsgate works on Ubuntu 14.04 and CentOS / RHEL 713:50
*** yamamoto has quit IRC13:50
sagar_nikami did not find a debian for it, should it be installled only using code13:50
*** matrohon has quit IRC13:50
sagar_nikami mean cloning the code and running the script to install it13:50
alexpilottiwe dont test on debian, but it's the same packaging as the ubuntu one13:50
sagar_nikamthe last debian is for ubuntu 12.0413:50
sagar_nikamon which version of ubuntu do you test ?13:51
alexpilottithe main issues might be the dependencies13:51
alexpilottitake a look at #link https://github.com/FreeRDP/FreeRDP-WebConnect13:51
sagar_nikamdo you install using .deb or using the script ?13:52
alexpilottiand let us know13:52
alexpilottithe recommended way is to build it, package it (create a deb in this case) and distribute the deb13:52
sagar_nikamhave seen that link13:52
sagar_nikamthe only install option on linux seems to be ./setup-all.sh13:52
sagar_nikamno deb package is available13:53
sagar_nikamis ti correct ?13:53
alexpilottino, you need to package it after the build13:53
sagar_nikamthe last deb works only on ubuntu 12.0413:53
sagar_nikamok13:53
alexpilottiwe dont provide binary releases for linux13:53
sagar_nikamso we need to package, got it13:53
alexpilottianother point is that in a hyper-converged scenario we prefer to have wsgate running on the compute nodes13:53
sagar_nikamanybody from freerdp community packages it ?13:54
alexpilottiso this means that it's the Windows version running directly on Hyper-V13:54
sagar_nikamon freerdp running on hyperv host13:54
alexpilottisagar_nikam: no, we are the maintainers for FreeRDP-WebConnect13:54
sagar_nikamhow many networks does the hyperv host have13:55
*** DevonBoatwright has joined #openstack-meeting-313:55
*** DevonBoatwright has left #openstack-meeting-313:55
sagar_nikamdo you do management and freerdp access on same network ?13:55
alexpilottidepends13:55
alexpilottion the size of the deployment13:55
*** nelsnelson has joined #openstack-meeting-313:55
alexpilottiif bandwidth allows, they can share the same network13:55
sagar_nikamwe should not have tenant users accessing freerdp console on the same network which is used for managemtn13:55
*** annegentle has joined #openstack-meeting-313:55
alexpilottithen a separate VLAN overlay can help13:56
sagar_nikamyes13:56
alexpilottior a completely separate physical network segment13:56
*** nelsnelson has quit IRC13:56
*** baoli_ has joined #openstack-meeting-313:56
sagar_nikambut freerdp we can provide only 1 network13:56
sagar_nikamin the conf file13:56
sagar_nikamand when nova sends the IP13:57
*** yamamoto has joined #openstack-meeting-313:57
sagar_nikamit will send a IP which the customer needs13:57
alexpilottiyou have the configuration for the keystone AUTH_URL13:57
sagar_nikamto access the console13:57
alexpilottithat can be on a separate network13:57
*** nelsnelson has joined #openstack-meeting-313:57
alexpilottiwsgate can listen on a specific network, instead of 0.0.0.013:57
alexpilottinote: 2' to meeting end13:58
alexpilottiso you can separate management from rdp13:58
*** brunograz has joined #openstack-meeting-313:58
sagar_nikami had some more questions on freerdp, can we discuss it sometime on hyperv channel13:58
sagar_nikamtomorrow13:58
*** vgridnev_ has quit IRC13:58
*** nelsnelson has quit IRC13:59
sagar_nikamyou can let me know the time13:59
*** neelashah has joined #openstack-meeting-313:59
alexpilottiok, thanks for joining today!13:59
*** baoli has quit IRC13:59
sagar_nikamthanks13:59
alexpilotti#endmeeting13:59
openstackMeeting ended Wed Feb 17 13:59:38 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-02-17-13.02.html13:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-02-17-13.02.txt13:59
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-02-17-13.02.log.html13:59
*** matrohon has joined #openstack-meeting-314:00
*** hogepodge has joined #openstack-meeting-314:00
*** abalutoiu_ has quit IRC14:00
*** brunograz has left #openstack-meeting-314:00
*** sergek has quit IRC14:01
*** sergek has joined #openstack-meeting-314:03
*** bryan_att has joined #openstack-meeting-314:03
*** annegentle has quit IRC14:07
*** vgridnev_ has joined #openstack-meeting-314:07
*** kvinod has quit IRC14:07
*** annegentle has joined #openstack-meeting-314:08
*** dims has quit IRC14:09
*** dims has joined #openstack-meeting-314:10
*** julim has quit IRC14:10
*** nelsnelson has joined #openstack-meeting-314:11
*** dougwig has joined #openstack-meeting-314:12
*** mkovacik_ has quit IRC14:12
*** nelsnelson has quit IRC14:12
*** sagar_nikam has quit IRC14:12
*** sweston has joined #openstack-meeting-314:13
*** vhoward has joined #openstack-meeting-314:14
*** tshtilma has quit IRC14:18
*** jpomeroy has joined #openstack-meeting-314:19
*** dtardivel has quit IRC14:20
*** dtardivel has joined #openstack-meeting-314:20
*** Guest14304 is now known as dansmith14:24
*** dansmith is now known as Guest8441114:25
*** dimtruck is now known as zz_dimtruck14:26
*** Guest84411 is now known as dansmith14:27
*** doug-fish has joined #openstack-meeting-314:28
*** vgridnev__ has joined #openstack-meeting-314:30
*** itoader has quit IRC14:30
*** dougwig has quit IRC14:33
*** vgridnev_ has quit IRC14:33
*** yamamoto has quit IRC14:35
*** dims_ has joined #openstack-meeting-314:35
*** dims has quit IRC14:36
*** Swami has joined #openstack-meeting-314:45
*** tej has joined #openstack-meeting-314:46
*** abalutoiu has quit IRC14:47
*** vgridnev__ has quit IRC14:51
*** vgridnev__ has joined #openstack-meeting-314:52
*** mkovacik has joined #openstack-meeting-314:52
*** rhochmuth has joined #openstack-meeting-314:52
*** lblanchard has quit IRC14:53
*** rbak has joined #openstack-meeting-314:53
*** flaper87 has quit IRC14:54
*** flaper87 has joined #openstack-meeting-314:54
*** julim has joined #openstack-meeting-314:55
*** vgridnev__ has quit IRC14:55
*** lazy_prince has joined #openstack-meeting-314:56
*** vgridnev__ has joined #openstack-meeting-314:56
*** bklei has joined #openstack-meeting-314:57
*** bmotz has joined #openstack-meeting-314:58
*** shinya_kwbt has joined #openstack-meeting-314:58
*** pradipm has joined #openstack-meeting-314:58
*** Kamil has joined #openstack-meeting-314:58
*** vgridnev__ has quit IRC14:58
*** AndreasM has joined #openstack-meeting-314:58
*** ho_away has joined #openstack-meeting-314:58
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Feb 17 15:00:02 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
openstackThe meeting name has been set to 'monasca'15:00
rhochmutho/15:00
rbako/15:00
KamilHello15:00
*** oheydorn has joined #openstack-meeting-315:00
rhochmuthhi kamil15:00
shinya_kwbto/15:00
bkleio/15:00
*** zawisza has joined #openstack-meeting-315:00
rhochmuthagenda is as follows:15:01
rhochmuthAgenda for Wednesday February 17, 2016 (15:00 UTC)15:01
rhochmuth1.Grafana v2 update15:01
rhochmuth2.Agent thread-pool not restarting.15:01
rhochmuthlink at, https://etherpad.openstack.org/p/monasca-team-meeting-agenda15:01
*** ddieterly has joined #openstack-meeting-315:01
rhochmuthwe should also probably look at outstanding reviews15:01
*** piet has joined #openstack-meeting-315:01
ho_awayhello15:02
pradipmHello15:02
rhochmuthhi ho_away15:02
rhochmuthhi pradipm15:02
rhochmuthplease feel free to update the agenda at the link15:02
*** brunograz has joined #openstack-meeting-315:02
rhochmuth#topic grafana v215:02
rbakJust a short update on this today15:03
*** dims_ has quit IRC15:03
*** jobrs has joined #openstack-meeting-315:03
*** baohua has quit IRC15:03
*** tgraichen has joined #openstack-meeting-315:03
*** brunograz has left #openstack-meeting-315:03
rbakGrafana has some concerns about having another auth method, so the patches are on hold for the moment.15:03
rbakBut they've offered to work with us to find a way to offer the integration.15:03
rbakI have a call with them later this week.15:04
rhochmuthsounds goo15:04
rbakSo this will happen, it just might take a little longer15:04
rbakThat's all I have for the moment.15:04
*** annegentle has quit IRC15:04
*** dhellmann has quit IRC15:05
*** annegentle has joined #openstack-meeting-315:05
rhochmuthok, thanks, hopefully i'll get to trying this out soon15:05
Kamilshort question. What would be the other auth-method? O-Auth?!15:05
*** dhellmann has joined #openstack-meeting-315:05
rbakPossibly?  Or maybe working out some sort of pluggable auth system to keystone doesn't need to be part of the main repo.15:06
rbakI'll know more next week15:06
*** Christian_ has joined #openstack-meeting-315:06
Kamilokay. Thx15:06
rhochmuthlet me know if you want me involved15:06
rbakwill do15:06
rhochmuthi had a discussion with raj15:06
rhochmuthand they are doing some really cool things with grafana15:07
*** annegentle has quit IRC15:07
rhochmuthso, next topic then15:07
rhochmuth?15:07
*** Swami_ has joined #openstack-meeting-315:07
rbaksure15:07
*** shwetaap has joined #openstack-meeting-315:07
*** gabriel has quit IRC15:07
rhochmuth#topic agent thread-pool not restarting15:07
rbakThis one is also mine15:07
rhochmuththat doesnt' sound good15:08
*** gabriel-bezerra has joined #openstack-meeting-315:08
*** gabriel-bezerra is now known as gabriel15:08
*** vgridnev__ has joined #openstack-meeting-315:08
rbakBasically in the collector monasca-agent uses a custom thread pool rather than a library.15:08
rbakBut the terminate function in the thread pool doesn't actually terminate threads15:08
rbakSo if a thread gets stuck it does a restart, which is terminate and join, and blocks there forever.15:09
*** dims has joined #openstack-meeting-315:09
rbakI'm just wondering if anyone who wrote the original thread pool is around to fix it?15:09
rbakOr maybe we need to switch to a thread pool library instead?15:10
rhochmuthhmmm, probably not15:10
rhochmuthso, if the thread is left in this state, what problem are you seeing, that we haven't seen after all this time15:11
rbakWe have issues with agents locking up like this every few days, and they require a manual restarts15:11
rbakI'm not sure what causes threads to get stuck15:11
*** Swami has quit IRC15:11
*** sigmavirus24_awa is now known as sigmavirus2415:11
rhochmuthhmmm, we haven't seen that15:11
rhochmuthis it a specific plugin that is failing that we aren't running15:11
*** dhague_ has joined #openstack-meeting-315:11
rhochmuthpossibly?15:12
rhochmuthor is it any thread/plugin15:12
rbakNo, I've seen it on http_check15:12
rbakAnd another that I can't remember15:12
rhochmuthok, so http_check was written by david schroeder15:12
*** marios has quit IRC15:13
rbakI think those are probably bugs in their own right, but the thread_pool shouldn't lock up.15:13
rhochmuthso, if you have a library in mind that you want to switch too that sounds good to me15:13
rhochmuthjust need to ensure licensing is ok on it15:13
rhochmuthapache, bsd, …15:14
rhochmuthbu not gplv215:14
rhochmuthif you want to touch-base with david, then i can get you in contact with him15:14
rbakI tried switching to the multiprocessing module yesterday.  That seems to be what the monasca thread pool is based on.15:14
rbakBut there are architecture reasons that doesn't work15:14
rbakI'll have to look around for other options15:15
rhochmuthwe haven't seen any problems with our http_check15:15
rhochmuththat we are performing in helion, btw15:15
*** jmckind has joined #openstack-meeting-315:15
rhochmuthok, i guess next topic15:16
rhochmuth#topic Mitaka Release planing (ansible-installer, devstack, etc.)15:16
*** piet has quit IRC15:16
Kamilokay that's mine15:16
rhochmuthhi kamil15:17
*** yamahata has joined #openstack-meeting-315:17
KamilHi. Openstack uses devstack to install a test/dev environment. I know that there exist already an integration for monasca. Do we plan to contribute this to devstack?15:17
*** atuvenie has quit IRC15:17
rhochmuthit is already done15:17
Kamilah okay... haven't seen it yet15:17
*** jtomasek_ has joined #openstack-meeting-315:17
rhochmuthSee, https://github.com/openstack/monasca-api/tree/master/devstack15:17
Kamiland will be the monasca-vagrant (ansible) also a part of mitaka release?15:18
*** jlanoux_ has joined #openstack-meeting-315:18
rhochmuthThere is also a Vagrantfile in that directory that you can use to build in one step15:18
*** piet has joined #openstack-meeting-315:18
*** marios has joined #openstack-meeting-315:18
*** jlanoux has quit IRC15:18
rhochmuthmonasca-vagrant is another development environment that predates devstack15:18
rhochmuthwe are still using monasca-vagrant15:19
rhochmuthbut, as it is only a dev environment, that repo isn't a part of the official release15:20
Kamilokay... but the devstack integration is still in monasca-api repo. Do we want to contribute it to the devstack repo?15:20
Kamili mean to this one: https://git.openstack.org/openstack-dev/devstack15:20
rhochmuththere are only specific "core" projects that are part of the devstack repo15:20
rhochmuthall the new projects are done as plugins15:21
rhochmuthso, there are projects like nova and swift that are part of devstack15:21
*** iyamahat has joined #openstack-meeting-315:21
rhochmuthbut newer projects, like murano and manilla are not15:21
Kamilokay. Thx. So that means, that we will need an installation script for log functionality15:22
rhochmuthi forget the actual specificis of whether a project is in or not15:22
rhochmuthi think we need to build a devstack plugin for the log api15:22
*** zz_dimtruck is now known as dimtruck15:22
rhochmuthone was already in progress or done15:22
KamilGood. Thanks for the information. That's all from my side15:23
rhochmuthactually, i might be confused15:23
rhochmuththere are tempest tests for the log api15:23
rhochmuthbut i don't see a devstack plugin15:23
*** mbound has quit IRC15:23
rhochmuthi think it would be developed similar to the current monasca plugin15:24
Kamilyes. I also haven't seen a plugin from log-api15:24
rhochmuthi would like to move off of the monasca-vagrant environment15:24
rhochmuthat some point15:24
*** MarkAtwood has joined #openstack-meeting-315:24
rhochmuthit is time consuming managing two environments15:24
rhochmuththere are several advantages of the monasca-vagrant env though15:25
rhochmuthnot sure how to resolve that15:25
*** numans has quit IRC15:26
Kamilmonasca-vagrant is a very good dev environment for testing purposes15:26
rhochmuthso, i should point out that the monasca devstack plugin is used by the openstack ci system15:26
*** mtanino has joined #openstack-meeting-315:26
*** ajmiller has joined #openstack-meeting-315:26
rhochmuthevery code review goes through openstack ci, which builds an devstack vm with monasca and then runs all the tempest tests against it15:27
rhochmuthcurrently, those tests are run against mysql and influxdb15:27
*** neelashah has quit IRC15:27
rhochmuthif you wanted to test hibernate/postgres, you could potentially add that as a configuration15:28
*** vgridnev__ has quit IRC15:28
rhochmuthwe test both the python and java apis15:28
rhochmuthbut not all variations of databases15:28
rhochmuthjust mysql and influxdb15:29
ddieterlythe gates only test the api, right?15:29
Kamili think yes15:29
rhochmuththe gates test the api15:29
ddieterlyso, we don't have gate jobs on the other monasca componenents15:29
*** neelashah has joined #openstack-meeting-315:30
ddieterlyi think it would be great if somebody created a devstack plugin for each of the other monasca components15:30
ddieterlyi.e., persister, threshold, notification15:30
ddieterlythen we could get tempest tests and gate jobs on those componenents15:31
*** vgridnev__ has joined #openstack-meeting-315:31
rhochmuthi'm not sure what you are saying15:31
rhochmuthusually teh tempest tests test the api15:31
ddieterlyit would be nice if each component had tempest tests15:32
rhochmuththe persister doesn't have an api15:32
ddieterlyso, we could have gate jobs for each component15:32
*** mhoppal has joined #openstack-meeting-315:32
ddieterlydoes tempest only tests api's?15:32
rhochmuththe tempest tests are usually for testing apis15:32
rhochmuththey are integration or system tests15:32
ddieterlyok, then other tests for the other components running in a gate job15:32
ddieterlyso, if you check in a review for the persister, then the gate tests are run15:33
rhochmuththere are gates on the persister, which include tempest15:33
rhochmuththe monasca devstack plugin is used by the monasca-persister15:34
ddieterlydoes the persister have a devstack plugin?15:34
ddieterlyoh, it is shared15:34
rhochmuthyes, it is shared15:34
ddieterlyit would be nice if it had it's own devstack plugin to isolate testing to just the persister15:35
rhochmuththe devstack plugin in the monasca-api is used by multiple projects15:35
*** sdake has quit IRC15:35
*** vgridnev__ has quit IRC15:35
*** vijendar has joined #openstack-meeting-315:36
ddieterlyinteresting15:36
pradipmWhen we mention enable_plugin monasca-api git://git.openstack.org/openstack/monasca-api - all the monasca mini services are getting installed (persistor, monasca-threh .. etc. etc. ..) right?15:36
rhochmuthcorrect15:36
*** sdake has joined #openstack-meeting-315:37
*** vijendar1 has joined #openstack-meeting-315:37
*** vgridnev__ has joined #openstack-meeting-315:37
rhochmuth#topic other15:38
rhochmuthho_away: are you still looking at anomaly detection?15:39
ho_awayrhochmuth* yep but mainly discussion with my colleague to explain of current implementation15:39
rhochmuthi saw an interesting article on fujitus applying deep learning to classification of time series data yesterday15:40
rhochmuthi've also started spinning up again on nonparametric statistics15:40
ho_awayrhochmuth: really, can you point out the link?15:40
*** vijendar has quit IRC15:41
*** dslevin has joined #openstack-meeting-315:41
rhochmuthhttp://phys.org/news/2016-02-fujitsu-deep-technology-time-series-high.html15:41
*** dslevin has quit IRC15:41
*** vgridnev__ has quit IRC15:42
ho_awayrhockmuth: thanks! i will find out the writer :-)15:42
*** vgridnev__ has joined #openstack-meeting-315:42
pradipmI am seeking an export opinion for one usecase .. if possible in monasca ..........15:42
rhochmuthplease note, that joe keen made some improvements to the kafka consumer in monasca-common15:42
*** nkrinner has quit IRC15:43
*** jtomasek_ has quit IRC15:43
*** dslevin has joined #openstack-meeting-315:43
rhochmuththis bumps the persister performance probably somewhere in the 10-20 K messages per sec15:43
ddieterlyjava or python or both?15:44
rhochmuththanks ho_away15:44
rhochmuthpython15:44
ddieterlynice15:44
rhochmuthjava was always fast15:44
rhochmuththese improvements address the python persister which we hadn't done as much analysis on15:45
*** rbak has quit IRC15:45
*** agentle has joined #openstack-meeting-315:45
rhochmuthso, does anyone want to talk about the log-api performance15:45
rhochmuthok, i've left my analysis and latest performance numbers15:47
*** vijendar1 has quit IRC15:47
KamilUnfortunaly, i am not aware of the current status of log-api. I think witek wrote you an email15:47
*** vijendar has joined #openstack-meeting-315:49
rhochmuthok, sounds like we are wrapping up15:49
pradipmI am seeking an export opinion for one usecase .. if I can discuss once here.15:49
rhochmuthsure15:50
rhochmuththe floor is yours15:50
*** vijendar1 has joined #openstack-meeting-315:50
*** galstrom_zzz is now known as galstrom15:50
pradipmIs there a way to run some simple rules on the alarm-history output?15:50
rhochmuthlike what15:50
pradipmfor example: over a time of say 5 hours, if IOPS have been breached in some pattern over 80%15:51
ddieterlyi don't believe that we have any filters/options on alarm-history at this time15:51
rhochmuththere is a topic in kafka that any consumer can consume from15:51
*** piet has quit IRC15:52
*** vgridnev__ has quit IRC15:52
rhochmuthif you want to consume alarm state transition events that would be easy15:52
*** vgridnev__ has joined #openstack-meeting-315:52
pradipmI see. ... directly from kafka?15:52
pradipmIt's already in the alarm-state-history .. right?15:52
*** vgridnev__ has quit IRC15:52
*** piet has joined #openstack-meeting-315:52
rhochmuthYou can also use the API15:53
*** AndreasM has quit IRC15:53
rhochmuththe entire alarm state history is in the API15:53
*** vijendar has quit IRC15:53
*** dwalleck has joined #openstack-meeting-315:53
rhochmuthyou can also "subscribe" to alamrs via webhook notifications15:53
pradipmthats correct. Is there any component in monasca that runs some form of rule-check on anywhere else?15:54
rhochmuthno15:54
pradipmOk....15:54
rhochmuththere has been some interest in various forms of this15:54
rhochmuthfor example, there is a group that is interested in alarm clustering15:55
pradipmany suggestion if I want to define some simple rules (filters as in alarm-history .. or similar) ... what shd be the best approach?15:55
*** jose_falavinha has joined #openstack-meeting-315:55
rhochmuththe Vitrage project is also interested in alarm correlation15:55
ddieterlyget the alarms from the api and do something externally15:55
pradipmVitrage is in Monasca? I am not aware of .. sorry for ignorance.15:55
rhochmuthVitrage is another openstack project15:55
ddieterlyactually, get the alarm-history...15:56
*** cjvolzka has joined #openstack-meeting-315:56
rhochmuthhttps://wiki.openstack.org/wiki/Vitrage15:56
pradipmmake sense ...ddieterly15:56
ddieterlypradipm: there is an option in the cli to get the raw json, that would help with external tools15:56
pradipmThanks rhochmuth15:56
rhochmuthi think understanding your specific use case would be good15:56
pradipmsure ...15:57
rhochmuthIf you want to plugin to kafka the message schema is at, https://wiki.openstack.org/wiki/Monasca/Message_Schema15:57
rhochmuthit depends on what you want to do though.15:57
*** rbak has joined #openstack-meeting-315:57
pradipmso basically I want to do some conformance on storage object underneath cinder/manila15:57
rhochmuthyou could filter alarm state transition events that are created by the threshold engine15:57
*** stendulker has joined #openstack-meeting-315:58
rhochmuthso, i'm guess that would best be handled via the api15:58
*** catherineD has joined #openstack-meeting-315:58
rhochmuthi should also point out that fabiog, who isn't here today, is adding support for Congress in Monasca15:58
rhochmuthCongress is a policy engine15:58
pradipmI see ... yeah .. something like that ...15:58
*** jose_idar has joined #openstack-meeting-315:58
rhochmuthPlease check out, https://wiki.openstack.org/wiki/Congress15:59
rhochmutha fabiog would be the contact15:59
pradipmcan I configure a policy (like simple rules) and run on top of say alarm-state-history apu ..15:59
rhochmuththis meeting is coming to an end i just realized15:59
*** gema has joined #openstack-meeting-315:59
pradipmwill try to chat to fabiog15:59
*** kebray has quit IRC15:59
pradipmthanks rhochmuth. thanks a lot for all the pointers.15:59
rhochmuthby everyone16:00
ho_awaythanks rhochmuth and all :-)16:00
rhochmuth#endmeeting16:00
pradipmbye and take care.16:00
openstackMeeting ended Wed Feb 17 16:00:29 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-02-17-15.00.html16:00
KamilBye @all16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-02-17-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-02-17-15.00.log.html16:00
tgraichenbye16:00
markvoelker#startmeeting defcore16:00
openstackMeeting started Wed Feb 17 16:00:48 2016 UTC and is due to finish in 60 minutes.  The chair is markvoelker. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
*** ho_away has left #openstack-meeting-316:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
openstackThe meeting name has been set to 'defcore'16:00
eglute_so/16:00
markvoelkero/16:01
dwallecko/16:01
gemao/16:01
*** bmotz_ has joined #openstack-meeting-316:01
markvoelker#topic agenda16:01
*** pradipm has left #openstack-meeting-316:01
markvoelker#link https://etherpad.openstack.org/p/DefCoreRing.1216:01
catherineDo/16:01
markvoelkerIf anyone has additional items for today, please note them in the etherpad.  We'll be talking about RefStack in the latter part of the meeting since catherineD may be on a bus at the moment. =)16:02
markvoelker#topic MidCycle Reminder16:02
markvoelkerOur midcycle is fast approaching (March 8-9 in Austin)16:02
markvoelkerThere's an etherpad started with agenda items here:16:02
markvoelker#link https://etherpad.openstack.org/p/DefCoreSpring2016MidCycle16:02
* catherineD yes on public bus16:03
markvoelkerIf there are additional items you want to discuss, please add them ASAP.  We'd like to start nailing down the agenda and assigning timeslots.16:03
*** jobrs has quit IRC16:03
*** salv-orl_ has joined #openstack-meeting-316:03
*** claudiub has quit IRC16:03
markvoelkerIt would also be helpful if you'd leave your name beside items you add so we know who to contact with questions. =)16:03
eglute_s+1!16:04
markvoelkerI'd like to take a first pass at timeboxing by next week's meeting so everyone can see it and suggest changes.16:04
*** cartik has joined #openstack-meeting-316:04
*** bmotz has quit IRC16:04
*** lblanchard has joined #openstack-meeting-316:04
*** Kamil has quit IRC16:04
markvoelkerOh, also: if you are attending in person and haven't yet responded to the dietary restrictions Doodle, please do so right away.16:05
*** baoli_ has quit IRC16:05
markvoelker#link http://doodle.com/poll/ewsiepmhv9p6r8e716:05
markvoelkerAny questions on the midcycle?16:05
*** obondarev has quit IRC16:05
*** vijendar1 has left #openstack-meeting-316:05
*** salv-orlando has quit IRC16:05
markvoelkerOk, moving right along then...16:06
markvoelker#topic New Capabilities16:06
*** piet has quit IRC16:06
*** zawisza has quit IRC16:06
purpo/16:06
markvoelkerFor the 2016.01 Guideline we divvied up the task of identifying potential new Capabilities by project and had one or two folks play point for each.16:06
markvoelkerI think that was extremely useful in getting things done, so I'd like to do it again.  And it's that time in the cycle where we need to get cracking. =)16:07
markvoelkerTo that end, we need volunteers to tackle ID'ing potential new capabilities for each project.16:07
*** banix has joined #openstack-meeting-316:07
markvoelker(as well as potentially removing older ones that are no longer useful or have been deprecated)16:07
*** vtech has quit IRC16:08
dwalleckI'd be happy to help with compute :)16:08
markvoelkerWould a quick breakdown of what you're signing up for be helpful before I start calling for volunteers? =)16:08
* gema nods16:08
markvoelkerOk, here's how it works:16:08
markvoelkerBasically your task is to identify new Capabilities in the project that potentially meet DefCore's Criteria ( https://github.com/openstack/defcore/blob/master/doc/source/process/CoreCriteria.rst )16:09
markvoelkerGenerally, you should talk with the PTL's/project committers to help pinpoint new capabiliteis16:10
*** shinya_kwbt has quit IRC16:10
markvoelkerOperators and end-users can be helpful, as well as user surveys, etc.16:10
markvoelkerOnce you think you've identified Capabilities, you'll put them into a patch against https://github.com/openstack/defcore/blob/master/working_materials/scoring.txt16:11
markvoelkerAnd we'll all discuss.  We generally expect several iterations of patchsets, so don't feel like you have to nail it all on the first go-around16:11
*** piet has joined #openstack-meeting-316:12
markvoelkerMake sense so far?16:12
gemayep16:12
markvoelkerAgain, your job is really just to make a first pass at it...once the candidates are posted we'll all be able to suggest ones that we think probably don't cut it, or suggest additional ones.16:13
*** agentle has quit IRC16:13
markvoelkerIf anyone has additional questions about the mechanics, just ping me on #openstack-defcore and I'll be happy to assist.16:13
gemaok, I will try to do keystone16:14
markvoelkergema, dwalleck: great, thanks!  Could you add your names to the etherpad please?16:14
markvoelkerI took Neutron last time and am happy to do so again.16:14
*** agentle has joined #openstack-meeting-316:14
dwalleckdone16:14
gemadone16:15
markvoelkercatherineD: you were talking with the Heat folks last time, can I coerce you into working on that again? =)16:15
*** eliqiao has joined #openstack-meeting-316:15
* markvoelker forgets that catherineD is still on a bus...ok, we'll come back to that16:15
markvoelkerThanks to those of you who've signed up--I'll send out a note to the ML soliciting additional signups this week.16:16
markvoelker#action markvoelker to send email soliciting signups for IDing new capabilities and giving a summary of the process16:16
*** piet has quit IRC16:17
markvoelker#action everyone sign up to help with capabilities16:17
markvoelkerAnything further on IDing new capabilities?16:17
gemamarkvoelker: by when do we need to have it?16:17
*** piet has joined #openstack-meeting-316:17
*** irenab has quit IRC16:17
markvoelkergema: ideally if we could have a first pass before the midcycle that would be awesome.  But we have about a mont.16:18
markvoelkers/mont/month/16:18
gemamarkvoelker: ack, will try16:18
*** irenab has joined #openstack-meeting-316:18
*** kebray has joined #openstack-meeting-316:18
markvoelkerAny other questions?16:18
*** egallen has quit IRC16:18
*** dougwig has joined #openstack-meeting-316:18
eglute_si think it is still too early for ceilometer16:19
*** armax has joined #openstack-meeting-316:19
eglute_sjust looking at the maturity of the project here: https://www.openstack.org/software/project-navigator/16:19
*** irenab has quit IRC16:20
*** guitarzan has joined #openstack-meeting-316:20
markvoelkereglute_s: yeah, there's some debate about that (see last user survey which says it's about as widely deployed in prod as Swift).  I lean that way too, but I'm inclined to have the discussion.16:20
gemawe use ceilometer with various degrees of success16:21
gemanot sure how a user would access it, though16:21
*** irenab has joined #openstack-meeting-316:21
*** r1chardj0n3s_afk has quit IRC16:21
markvoelkerAnything else on scoring for now?16:21
eglute_s+1 on the discussion, but the fact the maturity is 2, compared to Heat's 6 and Swift16:21
eglute_s's 716:21
*** mhoppal has quit IRC16:21
eglute_si also agree with gema, not sure how it would be exposed to users16:22
*** jose_idar has quit IRC16:22
*** jose-idar has joined #openstack-meeting-316:22
*** Guest46279 is now known as redrobot16:22
*** r1chardj0n3s has joined #openstack-meeting-316:22
markvoelkereglute_s: Perhaps the best way to handle this is for you take Ceilometer, and simply submit rationale for why you think it's not ready for inclusion yet?  That way we can still have a nice open discussion on the patch.16:23
*** Swami has joined #openstack-meeting-316:23
eglute_ssure16:23
markvoelkereglute_s: excellent16:24
*** Swami_ has quit IRC16:24
markvoelkerOK, anything else on this topic?16:24
eglute_snext :)16:24
markvoelker#topic Designated code sections16:25
eglute_sdwalleck can you speak to that?16:25
dwalleckeglute_s: sure16:25
dwalleckI've had a lot of questions internally at Rackspace about the designated code sections16:26
dwalleckThey were somewhat confused by the fact that there are critical code sections that are listed, but marked "false" for required16:26
*** piet has quit IRC16:26
dwalleckI'm assuming this means that they aren't required, but it seems a bit contridictory16:27
*** sarob has quit IRC16:27
markvoelkerdwalleck: I think I can speak to that16:27
dwalleckThere's also some concerns I'm hearing about the critical code sections being a bit too vague, but that's another topic :)16:27
*** atuvenie has joined #openstack-meeting-316:28
markvoelkerSO basically I think this dates back to early in DefCore's history when formats for this hadn't really been hammered out yet (frankly I'm not totally sure they have been yet =p)16:28
markvoelkerThe idea was to provide some additional clarity about things that were explicitly not required16:29
markvoelkerSo there were no questions about whether a thing (drivers, in the case you cited in the etherpad) was required or not16:29
markvoelkerSounds like that didn't exactly happen. =p  But your interpretation is correct: if it's listed as not required, it's not required (explicitly, rather than implicitly).16:30
markvoelkerMake sense?16:30
dwalleckMakes complete sense!16:30
dwalleckI don't think we have any issues, but I wanted to make sure my understanding was correct regardless16:30
jose-idarI had one question actually16:31
markvoelkerjose-idar: sure, go ahead16:31
jose-idarapi": { "description": "API section means actually the CODE that exposes the API, not just API-comparability", "designated": true, "comment": ""}16:31
jose-idarexactly what part of the code is that designating?16:31
eglute_sjose-idar can you link to the line?16:31
markvoelkerSo, a bit more history...16:31
*** yamahata has quit IRC16:32
markvoelkerEarly on there was a notion of whether something could be called OpenStack if it provided an alternate but fully compatible implementation16:32
jose-idarto be more general, how does defcore define the exact code that must be run?16:32
*** iyamahat has quit IRC16:32
markvoelkerThe decision was reached that for things like drivers that are meant to be pluggable, that's fine16:32
markvoelkerBut for things like the API server, that's not kosher because those are not intended to be swappable by the community16:33
* catherineD will work on Heat scoring16:33
markvoelkerHence the additional clarifier in the comment there that API-compatibility isn't all that's needed; the actual API server code is.16:33
purpIIRC, the core of this is that participation in the codebase is what matures the project and the community, and that's something OpenStack as a whole values.16:33
jose-idarI guess what I'm asking is, where is the list that says  "these are the approved .py's"16:33
jose-idarfor any given project16:34
markvoelkerjose-idar: it doesn't exist. =)  We've not attempted to define it down to that level, partly because that's an ever-changing list.  Rather, the intent was to give guidance and handle specific questions as they came in16:34
*** pcaruana has quit IRC16:35
jose-idarthat clears up the vagueness a little, thanks16:36
markvoelkerSure.  Designated sections are indeed a bit of a grey area, so if folks have suggestions on how to make them clearer, we're happy to entertain them.16:37
markvoelkerAnything else on this topic?16:37
eglute_swould it be worthwhile to add designated sections to midcycle discussions?16:38
markvoelker#topic Data privacy in RefStack16:38
purpeglute_s Yes16:38
markvoelkerwhoops, changed topic just too soon I guess =)  Sure, add it to the etherpad please16:38
eglute_sthanks purp, will do!16:38
*** bklei has quit IRC16:39
purpAdded.16:39
markvoelkercatherineD: are you available now, or should we tackled dwalleck's topic first?16:39
*** sarob has joined #openstack-meeting-316:39
* eglute_s thanks purp 16:39
catherineDyes let's discuss the RefStack topics16:39
catherineDthx16:39
*** bpokorny has joined #openstack-meeting-316:39
markvoelkerThe floor is yours madame. =)16:39
catherineDSo RefStack is implementing vendor registration .... and the users belong to the vendor16:40
*** killer_prince has joined #openstack-meeting-316:40
catherineDLet me discribe how users information got stored in RefStack16:40
catherineDRefStack uses OpenStack OpenID for authentication ...16:41
*** bpokorny has quit IRC16:42
catherineDwhen a user log into RefStack , the request is send to OpenStack OpenID for authentication ... https://openstackid.org/16:42
*** kzaitsev_mb has quit IRC16:42
*** bpokorny has joined #openstack-meeting-316:43
catherineDfron the response from OpenID , RefStack saves the user full name , email and OpenID to RefStack DB16:43
*** lazy_prince has quit IRC16:43
catherineDthat is how a user is register to RefStack ..16:43
gemacatherineD: who are the users?16:43
gema(as opposed to the vendor, I mean)16:44
catherineDuser is anyone who log into RefStack site and have an OpenStack ID16:44
gemayeah but who do you expect is going to be doing that16:44
hogepodgeMany users can be associated with one vendor, and users can move to different vendors16:44
gemasomeone that belongs to the vendor org?16:44
gemahogepodge: makes sense thanks, I was thinking about end users (the people running the apps on the clouds)16:45
catherineDlet's defer the vendor discussion a bit later ... I will come back to that16:45
*** SammyD has joined #openstack-meeting-316:45
gemaok16:45
*** salv-orl_ has quit IRC16:46
catherineDso my first question is ... should RefStack provides a API to list the users in RefStack ... and this REST API can be called by anyone with or without an OpenStack ID?16:46
catherineDthat is anonymous user who go to the RefStack site and do not sign in16:46
markvoelkercatherineD: I guess I'm not sure what the use case for that would be...e.g. why would we want that to be possible?16:47
purpcatherineD I'd expect that's an authenticated call.16:47
eglute_sI would think not16:47
hogepodgeWith privileged access, yes. But not anonymously or to all users. That's my inclination.16:47
eglute_s+1 to what hogepodge said16:48
gemaagreed, authenticated16:48
SammyD+1 hodgepodge16:48
eglute_salso, in terms of priority, is this API/feature of high priority? i would not think so16:48
catherineDmarkvoelker: I actually see no use case for anonumous user but just want to check ...16:48
eglute_sthis sounds like a nice to have later16:48
catherineDgreat ..16:48
markvoelkercatherineD: Ok.  I think we have consensus here that it's definitely not something we'd want to see done anonymously, and maybe only to privilleged users.16:49
catherineDnow even with an authenticated users ... now on the list of user what info should be returned .... 1) user name (for sure) 2) user email 3) user OpenID16:49
catherineDmarkvoelker: would you please log the agreement ... Thanks!16:50
purpcatherineD: Is there a use case behind adding a "list RefStack users" API call?16:50
markvoelker#agreed No anonymous API for listing all users and their OpenStackID info16:50
*** salv-orlando has joined #openstack-meeting-316:50
catherineDpurp: yes.. list user  API is what we are working on now ...16:50
*** killer_prince has quit IRC16:50
*** sheeprine has quit IRC16:50
purpcatherineD: I get that. What problem does it solve?16:51
markvoelkercatherineD: purp: I guess I could see that being useful for Foundation staff.  The average authenticated RefStack user...notsomuch.16:51
purpI can see wanting to list results. I'm struggling for a case where I'd want to get the list of all RefStack users.16:51
*** SotK_ has quit IRC16:51
catherineDpurp: yup...16:52
*** sheeprine has joined #openstack-meeting-316:52
* markvoelker notes we have 8 minutes remaining16:52
* eglute_s agrees with purp 16:52
* catherineD could we continure this discussion in #openstack-defcore16:52
*** rockyg has joined #openstack-meeting-316:52
hogepodgeFor administrative tasks I can see it as useful, but for general users I'm concerned about privacy. We should protect identifying information as we can.16:53
* catherineD since RefStack is kind of stuck right now16:53
purphogepodge +116:53
catherineDhogepodge: purp: +116:53
purpI'd say return the OpenStackID only, and require a lookup elsewhere.16:53
* rockyg sneaksl into the back of the channe16:53
markvoelkerhogepodge: +1.  As a Foundation staffer who would likely be the target audience for such an API if I'm reckoning correctly: would you find it useful, or can do what you need to do without it? =)16:53
purpI can control what's shown at OpenStackID (name, email, photo). I don't want to expose anything beyond what I've allowed there through any channel.16:54
*** belmoreira has joined #openstack-meeting-316:54
*** lazy_prince has joined #openstack-meeting-316:54
eglute_scatherineD we can definitely continue this in defcore channel later as well16:54
eglute_s+1 for privacy16:54
markvoelkerI think what I'm hearing is "we don't think we need this at all today, so backburner it until we find a case in which we do".  Accurate?16:54
hogepodgemarkvoelker: it would be useful in matching up vendors with users and doing some analysis. I'm building a defcore results database and could see it somehow interacting with it.16:54
purpcatherineD: Can certainly continue in #openstack-defcore, though I have a hard stop at 9a PST.16:54
catherineDeglute_s: thx for continuing the discussion16:55
catherineDso it seems like foundation member can see the list of users ...16:55
hogepodgemarkvoelker: +116:55
eglute_sdwalleck - we wont have time for your topics, wait until next week, mailing list discussion, openstack-defcore later, or all of the above?16:55
catherineDand the infor can be name, email, OpenID16:55
*** alaski has joined #openstack-meeting-316:56
dwalleckeglute_s: mailing list or next week is fine16:56
eglute_sthanks dwalleck16:56
dwalleckI'm still putting together some data around the topics I had16:56
catherineDnow for a vendor .... vendor will have a group of vendor users ...vendor should be able to list all users in the vendor16:56
eglute_scatherineD yes, that makes sense for a vendor to see what users they have. can they do it through UI now?16:57
*** baoli has joined #openstack-meeting-316:57
catherineDeglute_s: not yet .. .but it is the plan for Mitaka16:57
*** pt_15_ has joined #openstack-meeting-316:57
eglute_sok16:58
*** julim has quit IRC16:58
catherineDI think I get the guidedances on users (that is foundation can list all users in RefStack, vendor can list user in vendor)16:58
*** agentle has quit IRC16:58
eglute_s+116:58
catherineDnext topic vendor info16:59
eglute_swe are out of time...16:59
eglute_smove to defcore channel?16:59
markvoelkercatherineD: I think I wouldn't even worry about foundation staffers listing all users at this point, hogepodge said he probably doesn't have a use for it at the moment so it could be tabled until later16:59
catherineDthank you I won't take long ..16:59
markvoelkerYes, please: over to #openstack-defcore16:59
markvoelkerThanks everyone!16:59
eglute_sthanks markvoelker16:59
markvoelker#endmeeting16:59
openstackMeeting ended Wed Feb 17 16:59:50 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
*** iyamahat has joined #openstack-meeting-316:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-02-17-16.00.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-02-17-16.00.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-02-17-16.00.log.html16:59
*** mriedem has joined #openstack-meeting-317:00
alaski#startmeeting nova_cells17:00
openstackMeeting started Wed Feb 17 17:00:17 2016 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
openstackThe meeting name has been set to 'nova_cells'17:00
*** gema has left #openstack-meeting-317:00
mriedemo/17:00
alaskio/17:00
*** dwalleck has left #openstack-meeting-317:00
belmoreirao/17:00
*** cartik has quit IRC17:01
*** oheydorn has quit IRC17:01
alaskithis could be a short meeting17:01
alaskibut let's get going17:01
bauzas\o17:01
alaski#topic Cells testing/bugs17:01
mriedemi assume doffm is here17:01
alaskihmm, topic didn't work17:02
bauzasopenstack you there ?17:02
*** agentle has joined #openstack-meeting-317:02
*** tgraichen has quit IRC17:02
*** julim has joined #openstack-meeting-317:02
alaskiI have not heard of any issues regarding testing/bugs17:02
alaskibelmoreira: you had wanted to raise some high priority bugs17:02
alaskido you have a list?17:02
alaskior at least raise some bugs to get prioritized17:02
*** pt_15_ is now known as pt_1517:03
belmoreiralet me find my list17:03
*** vgridnev__ has joined #openstack-meeting-317:03
*** ccarmack has joined #openstack-meeting-317:04
*** rockyg has quit IRC17:04
alaskiokay, we'll swing back around in open discussion17:04
alaski#topic open reviews17:04
*** vgridnev__ has quit IRC17:04
bauzasthere are a lot :)17:04
alaskihttps://etherpad.openstack.org/p/mitaka-nova-priorities-tracking is your one stop shop for all things review related17:04
*** catherineD has left #openstack-meeting-317:05
alaskibauzas: yep, it's awesome17:05
alaskieveryone should drop everything and go review some cells code17:05
bauzascould we maybe try to reorganize like we did with the sched prio ?17:05
bauzasit's a bit hairy and a bit hard to follow17:06
bauzaslike sections per topic17:06
alaskisure17:06
*** jlanoux_ has quit IRC17:06
mriedemi should be +2 on the flavor tables today17:06
mriedemjust need to get back to it, doffm updated that one17:06
alaskimriedem: excellent17:06
alaskiI'll take a look as well17:06
bauzasmriedem: yeah was my next review17:07
belmoreiramriedem great17:07
*** e0ne has quit IRC17:07
bauzasthat one was stale recently AFAIR17:07
bauzasoh yeah17:07
alaskiit was updated yesterday17:07
alaski#topic Open Discussion17:08
bauzasyeah just saw17:08
belmoreirajust saw it17:08
alaskibelmoreira: are you ready with your list?17:08
*** cjvolzka has left #openstack-meeting-317:08
*** kebray has quit IRC17:09
belmoreirabug #1532562 was critical for was some weeks ago17:09
openstackbug 1532562 in OpenStack Compute (nova) "Cell capacities updates include available resources of compute nodes "down"" [Undecided,In progress] https://launchpad.net/bugs/1532562 - Assigned to Belmiro Moreira (moreira-belmiro-email-lists)17:09
belmoreiraI did a patch that I deployed in our infrastructure and it would be great to have some feedback17:09
alaskiokay, I'll take a look17:10
mriedemseems pretty straight-forward17:11
alaskianything else that is a high priority for you?17:11
bauzasbut it calls the SG API17:11
bauzaswhich is a bit concerning me, but let's discuss that offline17:11
belmoreirawe started using NUMA topology and hit #151700617:11
alaskibauzas: as long as it's calling it within a cell I think it's fine from a cells pov, but if you have other concerns we should certainly discuss17:12
bauzasalaski: that's the concern I wanted to be super-sure :)17:12
mriedemisn't there an attr on the service object that can give us the same info w/o the sg API?17:13
mriedemlike last_seen_up?17:13
bauzasmriedem: well, it's a long convo17:13
bauzasmriedem: and we have some BPs for that17:13
*** atuvenie has quit IRC17:13
belmoreirabauzas: that was my simple way to try to fix it. happy to change it17:13
bauzasbut AFAIK, the Service object is not yet having that kind of filed17:13
bauzasfield17:13
mriedembauzas: it's in the object class17:14
bauzasbelmoreira: nah, just need to think about the implications of your patch17:14
mriedemyou mean it's not getting set?17:14
bauzasmriedem: I know17:14
bauzasmriedem: well, remember, the SG API is a pure fun17:14
bauzasmriedem: and last_seen_up is a driver thing17:14
belmoreirai just raised that bug because we were suffering from it for a while without noticing... I imagine other are having the same problem17:14
bauzasthat's why we have 2 specs from someone trying to fix that17:15
alaskibelmoreira: that one could be tricky (#1517006). if it's adding new functionality it may have to wait, but I wonder if you can work around it by manually ensuring your flavors in the cells match17:15
*** ddieterly has quit IRC17:15
*** yamahata has joined #openstack-meeting-317:15
*** matrohon has quit IRC17:15
belmoreiraI have a work around... but very ugly to try to submit something17:16
alaskiright. honestly I'm not sure it's something we should spend time on, but I may not fully understand it17:16
belmoreirafine17:17
alaskiany others?17:17
ccarmackI have a question about cells and quotas …. if the quota usages get out of sync vs. the actual usage, there are 2 config options (until_refresh and max age) to refresh the usages  â€¦. would those work for cells?17:17
belmoreiramy point last meeting was that most bugs related with cells were not even triaged. I see that changed17:17
belmoreirathanks for having the time17:17
alaskibelmoreira: yep. thanks for reminding me :)17:18
alaskiccarmack: yes17:18
ccarmackexcellent .. thanks17:18
*** lazy_prince has quit IRC17:18
alaskithose are used way down in the db api so they're not affected by cells17:18
ccarmackyup17:18
alaskianything else for today?17:19
*** dhague_ has quit IRC17:19
alaskiI'm still waiting on an update on the resource pools/classes/providers work from jaypipes to get a clear picture on how that will work with cells17:20
*** SammyD has quit IRC17:20
mriedemhow much of that is actually expected to happen in mitaka?17:20
alaskiand doffm has been involved in those discussions as well17:20
mriedemi haven't been following along17:20
alaskimriedem: they're planning to get it all in17:20
mriedemjeez17:20
alaskiyeah, we'll see17:20
bauzasthe resource-pools, yes17:21
alaskiit is moving17:21
bauzasreally not sure for resource-providers17:21
jaypipesnot the allocations or scheduelr bits.17:21
bauzaswe're 2 weeks from FF :)17:21
jaypipesonly the resource-providers schema, the generic-resource-pools, and a bit of the compute node inventory bp17:21
alaskiokay, that's not a ton17:21
alaskibut generic-resource-pools is still an open question17:22
jaypipesI will have the g-r-p bp revised and sent up by end of today17:22
alaskicool, I'm ready to go through it again17:23
alaskiother than that I think most cells related work has patches up17:23
*** lazy_prince has joined #openstack-meeting-317:24
alaskiI would still like to try to move instance creation to the conductor, but if something big comes up in that work I may not be able to work around it in time17:24
alaskianything else?17:24
alaskicool. everyone has an extra 30 mins to go review code :)17:25
alaskithanks all!17:25
*** killer_prince has joined #openstack-meeting-317:25
*** mriedem has left #openstack-meeting-317:25
alaski#endmeeting17:25
openstackMeeting ended Wed Feb 17 17:25:31 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:25
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-02-17-17.00.html17:25
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-02-17-17.00.txt17:25
bauzas++17:25
*** ccarmack has left #openstack-meeting-317:25
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-02-17-17.00.log.html17:25
*** belmoreira has quit IRC17:25
*** lazy_prince has quit IRC17:28
*** kebray has joined #openstack-meeting-317:29
*** alaski has left #openstack-meeting-317:29
*** itxaka is now known as itxaka|afw17:29
*** sigmavirus24 has quit IRC17:30
*** xgerman has quit IRC17:31
*** rbak has quit IRC17:31
*** agentle has quit IRC17:32
*** xgerman has joined #openstack-meeting-317:32
*** carl_baldwin has quit IRC17:33
*** sarob has quit IRC17:34
*** dtardivel has quit IRC17:34
*** davidmichaelkarr has quit IRC17:34
*** scottda has quit IRC17:34
*** lekha has quit IRC17:34
*** zhenguo_ has quit IRC17:34
*** skath_ has quit IRC17:34
*** ameade has quit IRC17:34
*** GheRivero has quit IRC17:34
*** DuncanT has quit IRC17:34
*** wendar has quit IRC17:34
*** toan has quit IRC17:34
*** darrenc has quit IRC17:34
*** davidlenwell has quit IRC17:34
*** zigo has quit IRC17:34
*** dimtruck has quit IRC17:34
*** njohnston has quit IRC17:34
*** rbak has joined #openstack-meeting-317:35
*** wendar has joined #openstack-meeting-317:35
*** krtaylor_ has quit IRC17:35
*** eglute_s has quit IRC17:35
*** JayF has quit IRC17:35
*** lbragstad_ has quit IRC17:35
*** darrenc has joined #openstack-meeting-317:35
*** hdaniel has quit IRC17:35
*** sankarshan_away has quit IRC17:36
*** zigo has joined #openstack-meeting-317:36
*** toan has joined #openstack-meeting-317:37
*** davidlenwell has joined #openstack-meeting-317:37
*** zhenguo_ has joined #openstack-meeting-317:39
*** carl_baldwin has joined #openstack-meeting-317:39
*** eglute has joined #openstack-meeting-317:39
*** dimtruck has joined #openstack-meeting-317:39
*** lbragstad_ has joined #openstack-meeting-317:39
*** sankarshan_away has joined #openstack-meeting-317:39
*** njohnston has joined #openstack-meeting-317:39
*** JayF has joined #openstack-meeting-317:39
*** DuncanT has joined #openstack-meeting-317:39
*** krtaylor_ has joined #openstack-meeting-317:39
*** sarob has joined #openstack-meeting-317:39
*** davidmichaelkarr has joined #openstack-meeting-317:40
*** GheRivero has joined #openstack-meeting-317:41
*** ameade has joined #openstack-meeting-317:41
*** skath_ has joined #openstack-meeting-317:41
*** sigmavirus24 has joined #openstack-meeting-317:41
*** vgridnev__ has joined #openstack-meeting-317:42
*** scottda has joined #openstack-meeting-317:43
*** dtardivel has joined #openstack-meeting-317:43
*** stendulker has quit IRC17:44
*** lekha has joined #openstack-meeting-317:46
*** ChanServ sets mode: +o openstack17:46
*** Aish has joined #openstack-meeting-317:47
*** jose-idar has quit IRC17:52
*** agentle has joined #openstack-meeting-317:53
*** jose-idar has joined #openstack-meeting-317:53
*** lpetrut has quit IRC17:54
*** e0ne has joined #openstack-meeting-317:57
*** agentle has quit IRC17:57
*** _sarob has joined #openstack-meeting-317:58
*** egallen has joined #openstack-meeting-317:59
*** itxaka|afw has quit IRC18:03
*** julim has quit IRC18:03
*** _sarob has quit IRC18:03
*** SotK has quit IRC18:04
*** neiljerram has quit IRC18:04
*** andymaier has quit IRC18:05
*** julim has joined #openstack-meeting-318:05
*** _sarob has joined #openstack-meeting-318:06
*** Swami has quit IRC18:06
*** jwarendt has joined #openstack-meeting-318:07
*** woodster_ has joined #openstack-meeting-318:08
*** kebray has quit IRC18:08
*** sarob_ has joined #openstack-meeting-318:08
*** kebray has joined #openstack-meeting-318:10
*** _sarob has quit IRC18:11
*** SotK has joined #openstack-meeting-318:12
*** jpomeroy has quit IRC18:13
*** e0ne has quit IRC18:15
*** e0ne has joined #openstack-meeting-318:16
*** safchain has quit IRC18:17
*** e0ne has quit IRC18:17
*** hdaniel has joined #openstack-meeting-318:18
*** SridarK has joined #openstack-meeting-318:19
*** dslevin has left #openstack-meeting-318:19
*** agentle has joined #openstack-meeting-318:21
*** Swami has joined #openstack-meeting-318:23
*** pc_m has joined #openstack-meeting-318:30
*** sc68cal has joined #openstack-meeting-318:30
sc68calhi all18:31
SridarKsc68cal: and all Hi18:31
* pc_m lurking18:31
SridarKsc68cal: so we are mtg now ?18:31
sc68cal#startmeeting networking_fwaas18:31
openstackMeeting started Wed Feb 17 18:31:38 2016 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.18:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:31
*** openstack changes topic to " (Meeting topic: networking_fwaas)"18:31
openstackThe meeting name has been set to 'networking_fwaas'18:31
sc68calSridarK: yeah. I goofed last week18:31
SridarKsc68cal: no worries i think we started the year that way18:32
sc68calThe issue was I had not deleted my calendar for the meeting, so that bug in the yaml2ical has been biting me18:32
SridarKso i was not sure either18:32
sc68calI .... think I have it right now. I sent an e-mail to the ML last week about it, so it may take a bit of time for things to settle back down18:32
SridarKyes no worries18:33
SridarKping xgerman:18:33
SridarKtoday maybe there is some confusion18:33
sc68calyeah there might be :(18:35
*** agentle_ has joined #openstack-meeting-318:35
SridarKif we get xgerman and mickeys we could run thru18:36
sc68calHere was the e-mail18:36
sc68calhttp://lists.openstack.org/pipermail/openstack-dev/2016-February/086267.html18:36
SridarKyes i saw it18:36
sc68calI guess I should have actually stated the time that the meeting was to occur. sorry.18:36
*** sdague has quit IRC18:36
SridarKother folks may have missed the email18:36
*** sdague has joined #openstack-meeting-318:37
sc68calyeah18:37
*** neelashah has quit IRC18:38
SridarKshould we reconvene at the "wrong time" again for this week ?18:38
SridarKand settle down from the next week ?18:38
sc68calnah, I think we should just stick to now - and next week we18:39
sc68calwill be at the 0000 UTC time18:39
sc68calso basically take the hit on the chin now :)18:39
*** agentle has quit IRC18:39
SridarKsure18:39
xgermanok, my other meeting ended early18:39
SridarKaah good xgerman is on too18:40
xgermanI updated our HP calendars with the new time so we are good that way ;-)18:40
SridarKgood we are set18:40
SridarKwe can do a quick run thru of things18:41
xgermank18:41
xgermanPostgres support?18:41
xgermanI send to the ML and I think Postgres is out :-)18:42
SridarKxgerman: yes i was not sure on where we stand on that - i thought we always supported that before18:42
xgermanyeah, for me support and having gates go hand-in-hand18:43
SridarKok18:43
SridarKi think this was the review from madhu_ak ?18:45
xgermanyep18:45
xgermanand that was in response to the gate failing...18:45
*** eliqiao_ has quit IRC18:45
SridarKok, so we can move fwd on that ?18:45
xgermanyeah, I think we can18:46
SridarKi was not sure on the postgress part but looks like u are saying we are good18:46
SridarKok good18:46
xgermanwe also had some side bar in the neutron room the other week and we got talked into reviving #link https://review.openstack.org/#/c/223343/18:48
xgermanjwarendt will look into that18:48
*** eliqiao_ has joined #openstack-meeting-318:48
SridarKyes on the l3 agent inheritance - bharath from brocade also got a WIP out for observer hierarchy18:50
xgermanyeah, saw that18:50
SridarKso btwn these 2 we should be clean18:50
xgermanawesome…18:50
SridarKxgerman: on the reviews, u brought up last week - i think we are caught up with things18:51
xgermanyes, it looks much better now18:51
xgermangreat work — I know from other projects how frustrating it is to wait for reviews forever18:52
xgermanso this is grande18:52
SridarKxgerman: yes for sure thanks for the nudge18:52
*** jpomeroy has joined #openstack-meeting-318:54
SridarKon to fwaas v2 updates, i was hoping to be at a point where we can start looking at the rpc - i hacked up something on the db i/f and debugging an issue18:54
SridarKi am hoping at least this week we can start throwing some darts at the rpc/versioned objects18:55
xgermanthat would be good. I should be able to code them up in the next few days --18:55
*** baoli has quit IRC18:55
*** doug-fis_ has joined #openstack-meeting-318:55
SridarKok great18:55
*** baoli has joined #openstack-meeting-318:56
xgermanyeah things have been crazy lately18:56
SridarK+118:56
xgermanmy next meeting is coming up in 3 minutes...18:57
*** rossella_s has quit IRC18:57
sc68calmilestone-3 is always a bad time18:58
*** rossella_s has joined #openstack-meeting-318:58
xgermanyep18:58
SridarKsc68cal: yes and this cycle is always more crazy18:58
xgermanI think v2 is likely Newton18:58
*** bpokorny_ has joined #openstack-meeting-318:59
SridarKit seems - but atleast if we have some things moving we can get it in N118:59
*** doug-fish has quit IRC18:59
xgermanok, I am off to another meeting… will read the transcript...19:00
SridarKok19:00
*** doug-fis_ has quit IRC19:00
SridarKsc68cal: any other things we want to discuss ?19:00
sc68calno, I think it's pretty clear we're all getting beaten down pretty good :)19:00
*** s3wong has joined #openstack-meeting-319:00
SridarK:-)19:01
sc68calstay strong all19:01
SridarK+119:01
SridarKok then if nothing else we can call it a wrap, i can get back to my debugging19:01
*** ivar-lazzaro has joined #openstack-meeting-319:02
*** bpokorny has quit IRC19:02
*** doug-fish has joined #openstack-meeting-319:03
*** ivar-lazzaro has quit IRC19:03
sc68calsounds good19:03
sc68calthanks all19:03
SridarKthanks all19:03
sc68calnext week is the APAC time - 0000 UTC19:03
sc68cal#endmeeting19:04
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:04
SridarKyes19:04
openstackMeeting ended Wed Feb 17 19:04:00 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:04
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2016/networking_fwaas.2016-02-17-18.31.html19:04
SridarKbye19:04
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2016/networking_fwaas.2016-02-17-18.31.txt19:04
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2016/networking_fwaas.2016-02-17-18.31.log.html19:04
*** pc_m has left #openstack-meeting-319:04
*** neelashah has joined #openstack-meeting-319:04
*** agentle has joined #openstack-meeting-319:04
*** ivar-lazzaro has joined #openstack-meeting-319:04
*** jose_falavinha has quit IRC19:05
*** rhochmuth has quit IRC19:06
*** jmckind has quit IRC19:06
*** vgridnev__ has quit IRC19:07
*** doug-fish has quit IRC19:07
*** agentle_ has quit IRC19:08
*** baoli has quit IRC19:09
*** baoli has joined #openstack-meeting-319:10
*** vgridnev__ has joined #openstack-meeting-319:11
*** hdaniel has quit IRC19:11
*** doug-fish has joined #openstack-meeting-319:13
*** vgridnev__ has quit IRC19:14
*** bpokorny_ has quit IRC19:17
*** bpokorny has joined #openstack-meeting-319:17
*** dtardivel has quit IRC19:18
*** vgridnev__ has joined #openstack-meeting-319:18
*** vgridnev__ has quit IRC19:19
*** mchestr has joined #openstack-meeting-319:22
*** vgridnev__ has joined #openstack-meeting-319:22
*** Christian_ has quit IRC19:23
*** vgridnev__ has quit IRC19:25
*** agentle has quit IRC19:27
*** piet has joined #openstack-meeting-319:29
*** MarkAtwood has quit IRC19:30
*** vgridnev__ has joined #openstack-meeting-319:32
*** fawadkhaliq has quit IRC19:33
*** agentle has joined #openstack-meeting-319:35
*** baoli has quit IRC19:35
*** baoli has joined #openstack-meeting-319:36
*** vgridnev__ has quit IRC19:38
*** vgridnev__ has joined #openstack-meeting-319:38
*** dedery has joined #openstack-meeting-319:39
*** neelashah1 has joined #openstack-meeting-319:41
*** neelashah has quit IRC19:41
*** armax has quit IRC19:42
*** baoli has quit IRC19:42
*** ivar-lazzaro has quit IRC19:43
*** vgridnev__ has quit IRC19:44
*** baoli has joined #openstack-meeting-319:44
*** dedery has quit IRC19:46
*** piet has quit IRC19:46
*** evgenyf has joined #openstack-meeting-319:47
*** dedery has joined #openstack-meeting-319:48
*** killer_prince has quit IRC19:49
*** jose-idar has left #openstack-meeting-319:49
*** sdake has quit IRC19:54
*** TravT has joined #openstack-meeting-319:55
*** mnaser has joined #openstack-meeting-319:55
*** sdake has joined #openstack-meeting-319:57
*** r1chardj0n3s has left #openstack-meeting-319:57
*** jmckind has joined #openstack-meeting-319:58
*** ^Gal^ has joined #openstack-meeting-319:58
*** robcresswell has joined #openstack-meeting-319:59
*** sdake has quit IRC19:59
*** sdake has joined #openstack-meeting-319:59
robcresswello/20:00
robcresswellanyone about?20:00
*** matt-borland has joined #openstack-meeting-320:01
mnaserhello20:01
bpokornyHi all20:01
^Gal^hello20:01
*** r1chardj0n3s has joined #openstack-meeting-320:01
matt-borlando/20:01
TravT'ello20:01
r1chardj0n3so/20:01
robcresswell#startmeeting HorizonDrivers20:01
openstackMeeting started Wed Feb 17 20:01:22 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: HorizonDrivers)"20:01
openstackThe meeting name has been set to 'horizondrivers'20:01
r1chardj0n3shey, a bot!20:01
robcresswellSuccess!20:01
TravTif i remember right, david-lyle is on biz travel this week20:02
robcresswellYup20:02
robcresswellSo, notices20:02
*** lhcheng has joined #openstack-meeting-320:02
robcresswell2 weeks till M-3. Make sure your bps are ready for review and start nagging them cores.20:02
*** vgridnev__ has joined #openstack-meeting-320:02
*** jed56 has quit IRC20:03
robcresswellI'd like to avoid having quite so many FFEs this cycle :)20:03
TravTi have an idea for clearing the review backlog20:03
robcresswellWe have the midcycle coming up too so we can get through some reviewing I imagine20:03
TravTlet's just approve all of them and see what happens.  :P20:04
*** ivar-lazzaro has joined #openstack-meeting-320:04
robcresswell>.<20:04
^Gal^I have a design question, was told the drivers meeting is the place to be20:04
^Gal^regarding a patchset i suggested20:04
robcresswellThe other notice is the midcycle: make sure your topics are up for discussion https://wiki.openstack.org/wiki/Sprints/HorizonMitakaSprint20:05
robcresswellSee the etherpad linked inside20:05
robcresswellIf you can't make it, ask somebody else to represent :)20:05
robcresswellAnyone else have any general notices?20:05
robcresswell^Gal^: One moment :)20:06
r1chardj0n3sgot that bug smash link handy? :-)20:06
^Gal^sure, np :)20:06
r1chardj0n3shttps://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka20:06
robcresswelldammit, beat me to it.20:06
r1chardj0n3s(still open from last night ;-)20:06
robcresswellSo, this is very similar to the bug day we've been doing within Horizon, but much bigger.20:06
robcresswellWell. more with a focus on actually solving them20:07
robcresswellEither way, it aligns well IMO, and it would be good to drive attendance.20:07
robcresswellSo please read the etherpad and get involved.20:07
*** sarob_ has quit IRC20:08
*** tsufiev has joined #openstack-meeting-320:08
robcresswellI think thats all for notices, and there are no agenda items.20:08
robcresswell#topic Open Discussion20:08
*** openstack changes topic to "Open Discussion (Meeting topic: HorizonDrivers)"20:08
robcresswell^Gal^: Go ahead20:09
^Gal^yey20:09
^Gal^regarding the patchset https://review.openstack.org/#/c/271771/20:09
^Gal^Added option for cell_attributes_getter to return row data20:09
^Gal^Hm I needed cell to access fellow cell's data20:09
^Gal^and came out with a solution20:09
^Gal^but it is not quite neat design wise20:10
^Gal^just wanted to hear your thoughts and how should I approach that one20:10
tsufievtables code is already crumbling upon its own weight :/20:11
^Gal^yeah I guess we'll better of angular20:11
^Gal^but just for a quick python solution20:11
robcresswellWe're not giving up on python tables just because angular exists :/20:11
^Gal^:)20:12
tsufievIf it's needed by only one table, why not implement it in that specific table?20:14
^Gal^just what I did20:14
^Gal^just thought it'll be nice to have in Horizon base20:14
*** agentle has quit IRC20:14
^Gal^IMO anyhow20:14
robcresswellHmm. If its not common code, and there doesn't appear to be any need from other developers20:14
robcresswellI'm inclined to say no20:15
^Gal^I understand where you're coming from, just thought it is quite basic for cell to adress its row members20:15
robcresswellRight, but there's no need for it20:16
robcresswellUnless there's a good use case for Horizon, I don't really see the value in adding more complexity.20:17
^Gal^OK20:17
tsufiev+1 on banning more complexity w/o clear use cases20:17
^Gal^hmm20:17
^Gal^my use case is a tooltip20:17
^Gal^of a success row20:18
^Gal^if it is unsecessful, show the error on a quick hover20:18
^Gal^unsuccessful20:18
^Gal^but if you guys think it's an overhead for the entire Horizon, I understand20:19
robcresswellYeah, I'd prefer you just kept it in the plugin unless there is a requirement from other code.20:19
^Gal^sure20:19
robcresswellAny other bps/ items to discuss?20:19
tsufiev^Gal^: do you want to show a specific tooltip for a any cell in a row if a specific cell has specific state?20:20
^Gal^thanks for your thoughts20:20
*** hdaniel has joined #openstack-meeting-320:20
mnaseri had some ideas regarding the long term arch. of horizon.  i wanted to know how does everyone feel about adopting a model where horizon becomes a lightweight proxy (that basically works around cross domain requests) with an option for deployers to just use apache + mod_proxy as a stronger option.. and basically having a strong powerful frontend that talks to native openstack api's... this would obviously be a very long-term thing20:20
*** jmckind has quit IRC20:20
mnaserhaving this type of thing implemented with swift for starters would make it much better performing and makes scaling horizon easier for example20:20
^Gal^tsufiev: yep something like that20:20
*** vgridnev__ has quit IRC20:21
^Gal^tsufiev: I did manage to acheive what I was after, just thought I'll contribute it20:21
tsufiev^Gal^: then you could add a specific class to every cell and act accordingly20:21
^Gal^tsufiev: oh - I wanted only to show tooltip on one cell, but to alter the tooltip data20:22
tsufievmnaser: are you talking about swift refactoring richardjones is currently working on?20:22
robcresswellmnaser: Aren't you basically just proposing a different UI?20:22
*** tej has quit IRC20:23
^Gal^tsufiev: and for that i needed to access the row data, for me to get to other cells data20:23
robcresswellI mean, that sounds like an entire rewrite without using any of the existing code, no?20:23
mnaseruser interface can be the same, but the idea is to minimize client => horizon communication and try to adopt a client => openstack APIs directly20:23
tsufiev^Gal^: well, you could just modify that cell attrs with oython20:24
tsufievPython20:24
mnaserif horizon keeps adopting more angular related things in it and includes more client-side logic, then why not just talk directly with openstack if most of the logic will sit in the angular controllers/et20:24
mnaseri'm not sure if the current swift refactoring includes communicating directly with swift, so im not aware of that20:25
robcresswellmnaser: The "why not" would be because we don't have time to start rewriting APIs that frankly, work okay.20:25
mnasersure, but the idea is to look into adopting the model (as I can see, there's lots of refactors happening to use angular that still talk with horizon)20:26
robcresswellWell... propose a patch :)20:26
*** egallen has quit IRC20:26
robcresswellIIRC krotscheck was working on CORS support20:27
mnaserwell, the idea was to hear what everyone feels about it as a project before starting some work20:27
mnaserif there's any stoppers or issues that may seem problematic for anyone here, perhaps its good to hear them20:27
r1chardj0n3ssorry, wandered off for a moment there20:27
tsufievI feel it's many steps ahead of where we're now20:28
*** vgridnev__ has joined #openstack-meeting-320:28
*** vgridnev__ has quit IRC20:28
r1chardj0n3smnaser: your proposal is pretty much what I took to the Horizon devs about 18 months ago20:28
krotscheckyesssss20:28
*** vgridnev has joined #openstack-meeting-320:28
robcresswellkrotscheck: Heh, thought you might like to be involved.20:28
krotscheckYeah, reading backscroll20:28
mnaseri'll disclose, we have our own control panel (vexxhost), we spent a lot of time building it but we want to start adopting horizon now instead of our own portal20:28
r1chardj0n3smnaser: and the community decision at the time was to go with the middle ground approach we're currently implementing20:28
krotscheckSwift is the only API that is not using the oslo middleware cors support - they ahve their own implementation.20:29
mnaserwe started out with a similar horizon model, right now, we have angular talking to openstack APIs directly (with nginx proxying for cors issues)20:29
r1chardj0n3smnaser: my implementation is here https://github.com/r1chardj0n3s/angboard20:29
krotscheckAll other API's implement oslo_middleware's version.20:29
mnaseri know it's a huge leap but the performance improvements we saw, as well as easier overall code usage20:30
mnaserkrotscheck: we wanted to avoid messing with existing cors settings of services so we proxied back to the api endpoints using nginx, this could be easily done in apache over the long term20:30
mnaseri know it's a biiiiiig leap away, but long term it'll help scaling, make codebase easier (logic is kinda duplicated), and runs much faster20:31
krotscheckmnaser: That only works until you hit API's that express internal data relationships in absolute URL's.20:31
mnaserr1chardj0n3s: i've actaully ran into that impl and i was sad to see it was kinda left out20:31
mnaserkrotscheck: true, but we basically started using async.js to do fetching logic to retrieve what we need20:32
*** vgridnev has quit IRC20:32
mnaserfor example, for server detail page, initial server request, then flavor and image info request can happen in parallel too20:32
mnaserfirst-load will be much faster, extra info will load in eventually after20:33
TravTmnaser: i've been thinking about doing that kind of approach on my search panel20:33
*** krotscheck is now known as krotscheck_dcm20:34
TravTare you coming to the mid-cycle?20:34
* krotscheck_dcm wasnt able to line up daycare.20:34
mnaserTravT: no, ill be at the summit however20:35
mnaser(but that could be a bit too late :-p)20:35
r1chardj0n3swhy too late?20:35
TravTmnaser: that's not too late.20:35
mnaseroh okay, that works then :)20:36
r1chardj0n3sas I said, this conversation started 2 years ago :-)20:36
mnaserand i dont mind sharing our experience in this and maybe even showing some of the code which we use and how we solved issues that the horizon team might feel like they will come up down the road20:36
robcresswellI don't think anyone strongly disagrees with it. Any idea that results in a faster UI is obviously good. The issue is how to manage workload and how we maintain a forward moving UI while simultaneously rewriting huge chunks of it.20:37
r1chardj0n3swhat rob said20:37
tsufiev+120:38
mnaserI guess all it boils down to: first, the foundation has to be laid down, the ability to requests that go through a very very lightweight path and using an auth token only to talk with any API from the existing angular modules20:38
TravTmnaser: i do have a question that you could maybe refer me to. why async.js over angular promises and $q functions?20:39
r1chardj0n3smnaser: that's the easy bit ;-)20:39
r1chardj0n3s(I was also curious about async.js)20:39
mnaserTravT: easier flow control mostly.  async.js gives you a nice way to transition between one callback to another20:39
mnaser$q doesnt allow for as easy or clean code for these flows20:40
mnaseri think if i remember, you have $q method to allow for using more than a single promise20:40
mnaserbut, that's about it20:41
mnaserr1chardj0n3s: but i think once we establish the foundation, and we can get one or two small panels migrated (say.. list of agents, or something like that)20:42
robcresswellSo much deja vu, this is glitch in the matrix time.20:42
tsufievHehe20:42
mnaserand then the simplicity and how fast the code works could perhaps encourage slowly starting to use it for bigger use-cases20:42
r1chardj0n3srobcresswell: heh, I know, right?20:42
mnaserhaha :-P20:42
TravTmnaser: that's already in progress.20:42
TravTcome join the fun20:43
mnaserthis is why i wanted to bring this up here and maybe help speed up the process :)20:43
r1chardj0n3swe're not using a direct proxy because the APIs are typically quite terrible :-)20:43
r1chardj0n3sand Horizon already wraps them in a layer of nice20:43
r1chardj0n3swell20:43
*** agentle has joined #openstack-meeting-320:43
r1chardj0n3snicer20:43
mnaserso what stops us from having that layer of nice on the client side? :)20:43
r1chardj0n3sthat's precisely what we're doing right now :-)20:44
r1chardj0n3soh, not the API fix stuff20:44
TravTwell, eventually API could get us there20:44
r1chardj0n3sbecause that stuff is already written in Horizon20:44
TravTwe have a API layers client and horizon server side20:44
r1chardj0n3swhy write it again in JS when it's already there in Python?20:44
TravTin *THEORY* the client side API could at some point change to direct access *if needed*.20:45
robcresswellOne thing I am curious about, is why python hangs when loading a detail page but angular manages it in <1 second, when hitting the same API.20:45
r1chardj0n3shmm, the API "layer" is intentionall very thin on the client side, yes TravT?20:45
tsufievrobcresswell: django overhead?20:45
r1chardj0n3srobcresswell: which detail page in particular?20:45
mnaserrobcresswell: my experience is the same, i've always tried to figure out why but never could.  there is just so much django overhead20:45
r1chardj0n3sOK, wait up20:45
robcresswellr1chardj0n3s: Compare images in python to angular. The difference is v noticeable.20:45
r1chardj0n3sthe swift UI, which also goes through Django, is almost delay-free20:46
r1chardj0n3sso I'd like to know which angular details page appears to be incurring a Django hit, as I'd like to know why20:46
tsufievI think horizon tables code is then to blame20:46
r1chardj0n3s(sorry, the *new* swift UI, obviously ;-)20:46
robcresswellNono, you're misreading I think.20:46
mnaser(ps: the new swift ui proposal looks amazing! +1)20:47
robcresswellI'm saying that if you compare python image details to angular, I'm surprised at how fluid angular is. Granted, there are obvious benefits to client side magic.20:47
r1chardj0n3sok, so Python details pages are doing *way* more than just hitting that one API. They're also typically hitting all those other APIs like extensions, etc20:47
r1chardj0n3smnaser: thanks :-)20:47
robcresswellAnd the angular ones just aren't right now?20:47
robcresswellwell, angular *one* :p20:48
r1chardj0n3srobcresswell: for an initial angular page load, yes you still need to hit those things (because we're not Single Page App yet) but for the ng images stuff the detail page is SPA and only needs to load that one API call because the rest of the page is already loaded20:48
r1chardj0n3sI *think* that minght be the detail page you're thinking of20:49
robcresswellSure, thats the one.20:49
TravTmnaser: this talk from vancouver gives some background on where we are (which is after when the big explosions happened at the summit before it).20:49
TravThttps://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/beyond-the-horizon-innovating-and-customizing-horizon-using-angularjs20:49
robcresswellJust surprised at the speed difference. Makes me think we're doing something very wrong in our django views.20:49
r1chardj0n3salso, the images detail page async loads several APIs to fill in its details whereas the Python implementation will serially hit those APIs in turn20:49
mnaseri'll spend sometime looking at that20:49
r1chardj0n3srobcresswell: yes, zero parallelisation :-)20:50
robcresswellThat could be causing it. I'll look into it more.20:50
r1chardj0n3sparallelising inside django ... eek :-=)20:50
mnaserso i guess what we could say here is to continue to build on these client facing APIs of horizon20:50
TravTr1chardj0n3s: robcresswell: even if we parallelized on django side, you wouldn't get the progressive disclosure without intro-ing some other black magic20:50
r1chardj0n3syep20:51
mnaserand should we one day want to speed things up, we can implement those "nice" APIs on the client side?20:51
TravTe.g. show base instance details and paint in additional project, flavor, etc details afterwards20:51
r1chardj0n3smnaser: that was my secret plan, yes20:51
TravTshhh20:51
*** _sarob has joined #openstack-meeting-320:51
r1chardj0n3sit's not really a secret ;-)20:51
robcresswellTravT: Oh sure. The angular is a big improvement on fluidity.20:51
TravTdon't tell anybody!20:51
mnaseralright, well this clears things out overall20:51
mnaserone question (and maybe i should go read the horizon codebase about this)20:51
TravTmanser: there is a really cool demo that a few of will be doing at the mid-cycle using searchlight as well20:52
TravTmaybe we'll make a recording and send it along20:52
robcresswellTravT: As I said, I was just suprised at the sheer difference. On devstack its like zero load in angular vs a several second hang in django.20:52
robcresswellr1chardj0n3s: I was arguing with the london designers about swift UI today :p20:52
mnaseroops i almost printed the entire buffer of this channel out, hah.20:52
r1chardj0n3srobcresswell: fight the good fight! :-)20:52
r1chardj0n3sI've tried to be inspired by some of their ideas in my patch20:53
mnaserbut are the angular pages still very much tied up to the django backend (ex: table actions, etc) or are they defined in the angular side of things?20:53
*** jwarendt has left #openstack-meeting-320:53
*** _sarob has quit IRC20:53
TravTangular side20:53
r1chardj0n3syep, very much angular side20:53
robcresswellr1chardj0n3s: I told them to shift the breadcrumb so its usable, work on making the container delete more clear20:53
TravTdjango provide API pass through, negotiation20:53
r1chardj0n3srobcresswell: snap, that's what I told 'em too :-)20:53
*** _sarob has joined #openstack-meeting-320:54
mnaserok good, we're really really trying to leave our panel and move our customers to horizon, but we want to get it to a good state20:54
mnaser(i'd be more than happy to share our customers feedback as the roll out starts)20:54
TravTsounds like a great topic for the summit in Austin20:54
mnaserfor example, instance actions right now are really poorly done :-(20:54
r1chardj0n3smnaser: we have a UX team that's always looking to involve actual users in their design process!20:54
robcresswellmnaser: Best way would be to get involved in the angular work IMO. The API is good enough I think.20:54
mnaseron the details page, they're stolen from the table instance actions, so doing any action will redirect you back to the list of servers20:55
robcresswellYeah, talk to piet!20:55
r1chardj0n3smnaser: please talk to piet!!20:55
* tsufiev curious if with all these great promises we still need to optimize django views performance?20:55
TravTrobcresswell: r1chardj0n3s: that is part of what the registry patch solves on angular side20:55
robcresswelltsufiev: We're still a long way from replacing all of django.20:55
r1chardj0n3stsufiev: we still need to concern ourselves with horrible API performance :-)20:55
TravTdecoupling actions for views20:55
tsufievPage more tables, optimize calls, other stuff...20:55
mnaserwe also introduced a new networking tab into horizon, perhaps we'll submit a patch if folks feel that it's something that's wanted? let me show quickly20:55
mnaserand i'll try to get in touch with piet in that case20:55
r1chardj0n3sTravT: not sure I follow the connection20:55
mnaseri mean our horizon doesnt look so horizon-y anymore but20:56
robcresswellmnaser: Just looking at time, but feel free to share images or blueprint ideas in the Horizon chat after.20:56
mnaserah gotcha20:56
*** jmckind has joined #openstack-meeting-320:56
robcresswellThe intel guys in London have some good suggestions for improving the base Horizon theme.20:56
TravTr1chardj0n3s: connection is that we want the actions to truly not be bound to any particular view (details, particular table, etc)...20:57
robcresswellux midcycle has been interesting so far20:57
TravTbut maybe better to talk elsewhere (time running thin)20:57
*** kzaitsev_mb has joined #openstack-meeting-320:57
mnaseri'll be in #openstack-horizon20:57
r1chardj0n3sTravT: sure, I'm cool with that :-)20:57
TravTrobcresswell: what's coming out of it20:57
robcresswellmnaser: FYI, there are simple workarounds for that redirect issue in django.20:57
robcresswellWe could definitely fix that.20:58
mnaseryup, its quite poor ux imho20:58
*** neelashah has joined #openstack-meeting-320:59
*** neelashah1 has quit IRC20:59
robcresswellWe're almost at time20:59
robcresswellAnything else?20:59
mnaseri'm good, good interesting discussion :)20:59
r1chardj0n3sthanks all20:59
robcresswellYup, good discussion, thanks everyone!20:59
^Gal^thanks, take care21:00
robcresswell#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Wed Feb 17 21:00:04 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
*** r1chardj0n3s has left #openstack-meeting-321:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-02-17-20.01.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-02-17-20.01.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-02-17-20.01.log.html21:00
*** robcresswell has left #openstack-meeting-321:00
*** tsufiev has left #openstack-meeting-321:00
*** lhcheng has left #openstack-meeting-321:00
*** ^Gal^ has quit IRC21:00
*** TravT has left #openstack-meeting-321:00
*** _sarob has quit IRC21:03
*** e0ne has joined #openstack-meeting-321:04
*** evgenyf has quit IRC21:06
*** galstrom is now known as galstrom_zzz21:23
*** galstrom_zzz is now known as galstrom21:25
*** rtheis has quit IRC21:26
*** shwetaap has quit IRC21:28
*** rtheis has joined #openstack-meeting-321:29
*** armax has joined #openstack-meeting-321:41
*** shwetaap has joined #openstack-meeting-321:50
*** mnaser has left #openstack-meeting-321:53
*** jmckind has quit IRC22:02
*** salv-orl_ has joined #openstack-meeting-322:03
*** jtomasek is now known as jtomasek|afk22:04
*** banix has quit IRC22:05
*** sdake has quit IRC22:05
*** guitarzan has left #openstack-meeting-322:06
*** salv-orlando has quit IRC22:06
*** eliqiao_ has quit IRC22:11
*** bpokorny has quit IRC22:13
*** eliqiao_ has joined #openstack-meeting-322:13
*** vhoward has quit IRC22:15
*** neelashah has quit IRC22:19
*** rhochmuth has joined #openstack-meeting-322:19
*** matt-borland has quit IRC22:19
*** _sarob has joined #openstack-meeting-322:20
*** _sarob has quit IRC22:21
*** _sarob has joined #openstack-meeting-322:21
*** _sarob has quit IRC22:21
*** _sarob has joined #openstack-meeting-322:22
*** _sarob has quit IRC22:22
*** _sarob has joined #openstack-meeting-322:23
*** _sarob has quit IRC22:23
*** vtech has joined #openstack-meeting-322:24
*** rtheis has quit IRC22:25
*** jmckind has joined #openstack-meeting-322:25
*** e0ne has quit IRC22:27
*** sdake has joined #openstack-meeting-322:27
*** galstrom is now known as galstrom_zzz22:31
*** doug-fish has quit IRC22:33
*** doug-fish has joined #openstack-meeting-322:34
*** doug-fish has quit IRC22:34
*** doug-fish has joined #openstack-meeting-322:34
*** _sarob has joined #openstack-meeting-322:35
*** kebray has quit IRC22:36
*** lblanchard has quit IRC22:46
*** julim has quit IRC22:46
*** baoli has quit IRC22:51
*** armax has quit IRC22:51
*** baoli has joined #openstack-meeting-322:52
*** baoli has quit IRC22:54
*** baoli has joined #openstack-meeting-322:55
*** doug-fish has quit IRC22:57
*** doug-fish has joined #openstack-meeting-322:57
*** rossella_s has quit IRC22:57
*** rossella_s has joined #openstack-meeting-322:58
*** baoli has quit IRC23:00
*** ativelkov has quit IRC23:01
*** doug-fish has quit IRC23:02
*** e0ne has joined #openstack-meeting-323:02
*** ativelkov has joined #openstack-meeting-323:02
*** jpomeroy has quit IRC23:03
*** sarob_ has joined #openstack-meeting-323:03
*** sarob_ has quit IRC23:03
*** sarob_ has joined #openstack-meeting-323:04
*** baoli has joined #openstack-meeting-323:04
*** _sarob has quit IRC23:04
*** jmckind has quit IRC23:08
*** mchestr has quit IRC23:11
*** sigmavirus24 is now known as sigmavirus24_awa23:12
*** dims_ has joined #openstack-meeting-323:13
*** krtaylor_ has quit IRC23:13
*** dims has quit IRC23:14
*** _sarob has joined #openstack-meeting-323:15
*** kebray has joined #openstack-meeting-323:16
*** mchestr has joined #openstack-meeting-323:16
*** sdake_ has joined #openstack-meeting-323:18
*** sarob_ has quit IRC23:19
*** sdake has quit IRC23:20
*** kebray has quit IRC23:20
*** mchestr has quit IRC23:22
*** kebray has joined #openstack-meeting-323:23
*** mchestr has joined #openstack-meeting-323:23
*** agentle has quit IRC23:25
*** ivar-laz_ has joined #openstack-meeting-323:26
*** sc68cal has quit IRC23:27
*** e0ne has quit IRC23:27
*** ivar-lazzaro has quit IRC23:29
*** pballand has joined #openstack-meeting-323:32
*** sdake_ has quit IRC23:35
*** dimtruck is now known as zz_dimtruck23:36
*** shwetaap has quit IRC23:36
*** baoli has quit IRC23:36
*** agentle has joined #openstack-meeting-323:37
*** agentle has quit IRC23:38
*** sdake has joined #openstack-meeting-323:41
*** banix has joined #openstack-meeting-323:42
*** armax has joined #openstack-meeting-323:42
*** bpokorny has joined #openstack-meeting-323:44
*** sdake_ has joined #openstack-meeting-323:45
*** hoangcx has joined #openstack-meeting-323:45
*** sdake has quit IRC23:46
*** _sarob has quit IRC23:52
*** alex_xu has quit IRC23:53
*** alex_xu has joined #openstack-meeting-323:55
*** rhagarty has quit IRC23:55

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