Wednesday, 2015-11-18

*** msambol has quit IRC00:00
*** jaypipes has quit IRC00:04
*** rbak has quit IRC00:04
*** Sam-I-Am has joined #openstack-meeting-300:09
*** Sam-I-Am has left #openstack-meeting-300:09
*** rhagarty has joined #openstack-meeting-300:10
*** jckasper has joined #openstack-meeting-300:12
*** bzhou has joined #openstack-meeting-300:15
*** bklei has quit IRC00:15
*** bklei has joined #openstack-meeting-300:16
*** bklei has quit IRC00:20
*** yamamoto has joined #openstack-meeting-300:30
*** shaohe_feng has joined #openstack-meeting-300:39
*** Sukhdev has quit IRC00:41
*** Sukhdev has joined #openstack-meeting-300:43
*** shaohe_feng1 has joined #openstack-meeting-300:43
*** Sukhdev has quit IRC00:44
*** shaohe_feng has quit IRC00:45
*** bklei has joined #openstack-meeting-300:47
*** yamamoto has quit IRC00:48
*** iyamahat has quit IRC00:48
*** bklei has quit IRC00:48
*** bklei has joined #openstack-meeting-300:48
*** mestery has quit IRC00:50
*** shimura_ken has joined #openstack-meeting-300:52
*** hoangcx has joined #openstack-meeting-300:53
*** hoangcx has left #openstack-meeting-300:53
*** armax has joined #openstack-meeting-300:57
*** msambol has joined #openstack-meeting-301:00
*** msambol has quit IRC01:07
*** Aish has quit IRC01:14
*** shaohe_feng1 has quit IRC01:16
*** stevemar_ has quit IRC01:23
*** shaohe_feng has joined #openstack-meeting-301:24
*** Aish has joined #openstack-meeting-301:25
*** Swami has quit IRC01:28
*** baohua has joined #openstack-meeting-301:30
*** mchestr has quit IRC01:31
*** mchestr has joined #openstack-meeting-301:31
*** ivar-laz_ has joined #openstack-meeting-301:32
*** jaypipes has joined #openstack-meeting-301:33
*** shaohe_feng has quit IRC01:34
*** ivar-lazzaro has quit IRC01:36
*** mchestr has quit IRC01:36
*** yamamoto has joined #openstack-meeting-301:37
*** ivar-laz_ has quit IRC01:37
*** ivar-lazzaro has joined #openstack-meeting-301:38
*** ivar-lazzaro has quit IRC01:38
*** ivar-lazzaro has joined #openstack-meeting-301:39
*** ivar-lazzaro has quit IRC01:39
*** tpeoples_ is now known as tpeoples01:40
*** ivar-lazzaro has joined #openstack-meeting-301:40
*** zhenguo has joined #openstack-meeting-301:42
*** Aish has quit IRC01:42
*** kebray has quit IRC01:46
*** ivar-lazzaro has quit IRC01:52
*** stanzgy has joined #openstack-meeting-301:56
*** mestery has joined #openstack-meeting-302:00
*** Aish has joined #openstack-meeting-302:02
*** baoli has joined #openstack-meeting-302:03
*** annp has joined #openstack-meeting-302:06
*** tfukushima has joined #openstack-meeting-302:07
*** bpokorny_ has joined #openstack-meeting-302:09
*** lazy_prince has joined #openstack-meeting-302:10
*** banix has joined #openstack-meeting-302:11
*** bpokorny has quit IRC02:12
*** Aish has quit IRC02:13
*** bpokorny_ has quit IRC02:13
*** stevemar_ has joined #openstack-meeting-302:14
*** dconde has quit IRC02:18
*** shaohe_feng has joined #openstack-meeting-302:22
*** baoli_ has joined #openstack-meeting-302:25
*** baoli has quit IRC02:28
*** sdake has joined #openstack-meeting-302:28
*** dims_ has quit IRC02:30
*** zz_dimtruck is now known as dimtruck02:31
*** s3wong has quit IRC02:36
*** stevemar_ has quit IRC02:42
*** stevemar_ has joined #openstack-meeting-302:42
*** shimura_ken has quit IRC02:51
*** shimura_ken has joined #openstack-meeting-302:52
*** shimura_ken has quit IRC02:53
*** klkumar has joined #openstack-meeting-302:53
*** yantarou____ has joined #openstack-meeting-302:53
*** msambol has joined #openstack-meeting-302:54
*** tfukushima has quit IRC02:55
*** dconde has joined #openstack-meeting-302:56
*** Aish has joined #openstack-meeting-302:58
*** NobodyCam has quit IRC02:59
*** davidmichaelkarr has quit IRC03:00
*** NobodyCam has joined #openstack-meeting-303:00
*** mestery has quit IRC03:03
*** yantarou____ has quit IRC03:17
*** klkumar has quit IRC03:22
*** banix has quit IRC03:26
*** kebray has joined #openstack-meeting-303:26
*** tpeoples is now known as tpeoples_away03:27
*** annp has quit IRC03:28
*** sdake has quit IRC03:35
*** klkumar has joined #openstack-meeting-303:35
*** yantarou has joined #openstack-meeting-303:36
*** dimtruck is now known as zz_dimtruck03:43
*** flwang1 has quit IRC03:43
*** sdake has joined #openstack-meeting-303:45
*** jhesketh has quit IRC03:52
*** jhesketh has joined #openstack-meeting-303:53
*** Aish has quit IRC03:54
*** lazy_prince has quit IRC03:55
*** Aish has joined #openstack-meeting-303:56
*** annp has joined #openstack-meeting-304:04
*** lazy_prince has joined #openstack-meeting-304:05
*** Aish has quit IRC04:25
*** lazy_prince has quit IRC04:30
*** lin_yang_ has joined #openstack-meeting-304:31
*** msambol has quit IRC04:33
*** amotoki has joined #openstack-meeting-304:34
*** markvoelker_ has quit IRC04:40
*** bzhou has quit IRC04:41
*** lin_yang_ has quit IRC04:44
*** Aish has joined #openstack-meeting-304:48
*** amotoki has quit IRC04:49
*** terrylhowe has quit IRC04:54
*** terrylhowe has joined #openstack-meeting-304:58
*** amotoki has joined #openstack-meeting-305:01
*** gcb has joined #openstack-meeting-305:01
*** yuikotakada has joined #openstack-meeting-305:07
*** amotoki has quit IRC05:10
*** amotoki has joined #openstack-meeting-305:14
*** Sukhdev has joined #openstack-meeting-305:17
*** iyamahat has joined #openstack-meeting-305:18
*** vgridnev has joined #openstack-meeting-305:19
*** jaypipes has quit IRC05:20
*** stevemar_ has quit IRC05:27
*** stevemar_ has joined #openstack-meeting-305:28
*** krtaylor has quit IRC05:29
*** stevemar_ has quit IRC05:30
*** msambol has joined #openstack-meeting-305:34
*** msambol has quit IRC05:38
*** amotoki has quit IRC05:40
*** salv-orl_ has joined #openstack-meeting-305:50
*** Sukhdev has quit IRC05:50
*** amotoki has joined #openstack-meeting-305:51
*** salv-orlando has quit IRC05:53
*** salv-orl_ has quit IRC05:55
*** galstrom_zzz is now known as galstrom05:56
*** dedery has joined #openstack-meeting-305:57
*** Aish has quit IRC06:02
*** Aish has joined #openstack-meeting-306:04
*** dconde has quit IRC06:12
*** yuikotakada has quit IRC06:15
*** kebray has quit IRC06:17
*** mchestr has joined #openstack-meeting-306:17
*** vnyyad has joined #openstack-meeting-306:18
*** iyamahat has quit IRC06:19
*** ryu_ishimoto has joined #openstack-meeting-306:21
*** soichi has joined #openstack-meeting-306:23
*** numans has joined #openstack-meeting-306:24
*** kaz has joined #openstack-meeting-306:27
vnyyad#startmeeting taas06:30
openstackMeeting started Wed Nov 18 06:30:11 2015 UTC and is due to finish in 60 minutes.  The chair is vnyyad. 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
yamamotohi06:30
vnyyadHi06:30
soichihi06:30
kazHello06:30
dederygood morning/noon/afternoon/night :)06:30
reedipo/06:30
*** klkumar has quit IRC06:31
vnyyadshall we get into the agenda06:31
vnyyadthanks soichi for proposing the items for this weeks agenda06:32
yamamoto#link https://wiki.openstack.org/wiki/Meetings/taas Agenda06:32
soichii got several important comments from Anil.06:33
vnyyadi guess anil is not in the meeting today but as he replied his commtnst to all of us we can discuss them06:34
yamamotosoichi: kaz: are you sure that "A mirrored traffic double back to br_int" is a real disadvantage?06:35
soichiyes, in terms of efficency.06:35
yamamotoas all userland bridges connected by patch ports are handled by a single datapath anyway...06:35
yamamotosoichi: do you have numbers?06:36
soichiexcuse me, but what do you mean "numbers"?  number of datapath?06:37
vnyyadsoichi : performance numbers i suppose06:37
yamamotoyes, benchmark results06:38
soichicurrently, we does not have.06:38
*** irenab has joined #openstack-meeting-306:38
*** tamari has joined #openstack-meeting-306:39
soichiWe are under planning to mesure.06:39
yamamotook.  my guess is there isn't much difference performance-wise.06:39
kazI thnk it must have complex flow entries.06:40
*** markvoelker has joined #openstack-meeting-306:40
yamamotokaz: userland flows, i agree.  i suspect no much difference in kernel flows though.06:41
kazSorry, what is "kernel flows"?06:43
yamamotokaz: odp flows (vs openflow flows)06:43
*** trinaths has joined #openstack-meeting-306:44
trinathsHi06:44
*** markvoelker has quit IRC06:45
yamamotokaz: are you familiar with ovs implementation?06:45
*** tfukushima has joined #openstack-meeting-306:45
kazI can't answer right now.06:45
vnyyadanil has explained the reasons behind the current design in his mail yesterday06:48
*** klkumar has joined #openstack-meeting-306:48
reedipHello, I saw in  Media: OperationsFromGUI_20151116-01.pdf that the TAP CLIs are supported. But I couldnt find any option in the Neutron Client06:48
yamamotoreedip: currently taas uses a dedicated "taas" command.06:49
soichivnyyad: yes, i am trying to understand the backgroud.06:50
vnyyadreedip: Neutron client support for taas is proposed by soichi06:50
vnyyadshould we have a mail list to discuss these items06:51
*** salv-orlando has joined #openstack-meeting-306:51
trinathstaas - is just port monitoring or helps in vm ha?06:51
yamamotovnyyad: what's wrong with openstack-dev?06:52
vnyyadyamamoto: we can use it, i guess we add [taas] to the subject06:53
yamamototrinaths: just monitoring.  it might be able to be used for some kind of HA but i have no idea.06:53
yamamotovnyyad: sure06:53
reedipyamamoto, vnyyad: It would be good if the following agendas are discussed on emails, so that everyone in loop knows whats happening. And I agree with yamamoto  that the Openstack devlist with [taas] can be used06:53
*** MarkAtwood has joined #openstack-meeting-306:53
vnyyadreedipt: sure, that will be done from now on06:54
dederyshouldn't it be [neutron][taas]?06:54
yamamoto+1 [neutron][taas]06:54
reedipyeah, [neutron][taas] sounds better06:54
trinathsyamamoto: okay. what more can be done using this monitoring?06:54
*** tfukushima has quit IRC06:56
soichi+106:57
kaz+106:57
vnyyadtrinaths: currently it is for mirroring the traffic from a particular port to another port, what you do with the mirrored traffic is not covered under taas right now06:58
*** sankarshan_away is now known as sankarshan06:59
vnyyad+1 [neutron][taas] it will be06:59
yamamotokaz: soichi: are you going to submit horizon patch?07:00
yamamoto#info we'll use [neutron][taas] on openstack-dev07:03
soichiNo, it is just a first prototype. Before submit to horizon, we would like to share in TaaS project.07:03
trinathsvnyyad: can you be more clear on "particular port to another port" *07:03
*** tfukushima has joined #openstack-meeting-307:04
vnyyadtrinaths: from one neutron port of another neutron port (which is call the tap service port)07:04
dederytrinaths: both ports belong to the same tenant07:05
vnyyadsoichi: thanks for the work on horizon support for TaaS07:05
*** ktatsuro has joined #openstack-meeting-307:05
yamamoto+107:05
vnyyaddedery: +107:05
irenabdedery: this maybe the case, that admin wants to mirror tenant traffic07:06
trinathsvnyyad dedery: confused07:06
vnyyadirenab: In the current implementation the admin has to create a user under the tenant to mirror flow07:08
dederyirenab: i'm aware of the use-case (especially lawful intercept) from what i read in the bp there was quite a discussion about this07:08
dederyirenab: not sure if the discussion reached any actionable conclusion07:09
vnyyadirenab: this was done to keep tenant in the loop that their traffic is being monitored by the admin, mainly for privacy07:09
vnyyaddedery: yes it was discussed at length during the spec reviews07:09
*** tfukushima has quit IRC07:10
*** salv-orlando has quit IRC07:12
vnyyadtrinaths: Please refer to https://github.com/openstack/tap-as-a-service and the spec at https://review.openstack.org/#/c/96149/8/specs/juno/tap-as-a-service.rst07:13
yamamotohow about finishing agenda items before having random discussions?07:13
*** nkrinner has joined #openstack-meeting-307:14
dederyyamamoto: +107:14
irenabdedery: fair enough07:14
vnyyadyes sure07:14
vnyyad:)07:14
trinathsvnyyad: thank you. will go through them07:14
yamamotovnyyad: can you use #topic to avoid sidetracking?07:14
vnyyadyamamoto: i will07:14
vnyyad#topic isolation of production and mirrored traffics07:15
*** openstack changes topic to "isolation of production and mirrored traffics (Meeting topic: taas)"07:15
*** armax has quit IRC07:16
soichiWe proposed a dedicated tunnel to carrying mirrored traffic.07:16
trinathssoichi: can you provide the link ?07:17
yamamoto#link https://wiki.openstack.org/w/images/7/78/TrafficIsolation_20151116-01.pdf07:17
trinathsthank you07:18
soichiI didn't mentioned in the document,07:18
vnyyadsoichi: this might be helpful if there is a separate physical network to carry the mirrored traffic07:18
soichidefinitely07:19
vnyyadbut if uses the same underlying physical network what might be the advantage07:19
vnyyadThe design was not to introduce more tunnels then already there07:20
soichiAlthough it depends on the physical configuration of a host, we want to map trafiics to different pysical NIC07:20
vnyyadsoichi: in cases of having a different physical networks i see a good use of the proposed design, one network for production traffic and another for mirrored and admin and other traffic07:22
kazI may be easy to control QoS.07:22
vnyyadany thoughts on this from others07:24
*** subscope has joined #openstack-meeting-307:24
yamamotoi wonder how much it complicates the code07:25
vnyyadwe have 5 mins in the meeting, i propose that we bring this up for discussion in the next meeting too along with discussing this on the mailing list07:26
soichiwe would like to share the source code we have implemented.07:26
yamamotosoichi: great.07:27
yamamotovnyyad: +107:27
vnyyadsoichi: that would be good07:27
yamamotolet's move on quickly07:28
reedipsoichi: +107:28
vnyyadOn the Dashboard support for TaaS, The effort is really appreciated and thanks for that07:28
soichitahnks07:28
yamamoto#link https://wiki.openstack.org/w/images/2/2e/OperationsFromGUI_20151116-01.pdf07:29
reedipI found only Create and Delete options, is an Update option viable?07:29
vnyyadAnil in his mail has some good suggestions on this07:29
vnyyadreedip there is not option for update yet in the TaaS API, we currently support create and delete for Tap Service and Tap Flow07:31
reedipok07:31
yamamotoreedip: i guess it isn't too important as only updatable fields akkkre name and description07:31
vnyyadi have to end the meeting now, but will add the items remaining to the next meeting agenda07:31
reedipyamamoto: I was also thinking in the similar lines07:31
vnyyadany other business07:32
yamamotovnyyad: sure.  and/or discuss on ML.07:32
vnyyadok then07:32
soichithank you07:32
vnyyadBye everybody07:33
reedipPlease share Anil's comments on the ML07:33
yamamotothank you07:33
kazbye07:33
dederythank you all07:33
dederybye07:33
reedipthat would allow everyone to come in sync07:33
vnyyadreedip: we will07:33
vnyyadbye07:33
reedip+1 , tc :)07:33
vnyyad#endmeeting07:33
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"07:33
openstackMeeting ended Wed Nov 18 07:33:31 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2015/taas.2015-11-18-06.30.html07:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2015/taas.2015-11-18-06.30.txt07:33
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2015/taas.2015-11-18-06.30.log.html07:33
*** kaz has quit IRC07:33
*** soichi has left #openstack-meeting-307:35
*** msambol has joined #openstack-meeting-307:36
*** markvoelker has joined #openstack-meeting-307:41
*** msambol has quit IRC07:41
*** mchestr has quit IRC07:43
*** mchestr has joined #openstack-meeting-307:43
*** mchestr has quit IRC07:45
*** markvoelker has quit IRC07:46
*** mchestr has joined #openstack-meeting-307:46
*** mchestr has quit IRC07:50
*** vnyyad has quit IRC07:51
*** galstrom is now known as galstrom_zzz07:55
*** stanzgy has quit IRC07:56
*** stanzgy has joined #openstack-meeting-307:56
*** belmoreira has joined #openstack-meeting-307:57
*** deshipu has joined #openstack-meeting-307:57
*** umargolin has joined #openstack-meeting-308:03
*** Aish has quit IRC08:04
*** alexey_weyl has joined #openstack-meeting-308:04
*** matrohon has joined #openstack-meeting-308:05
*** dtardivel has joined #openstack-meeting-308:11
*** umargolin has quit IRC08:11
*** stevemar_ has joined #openstack-meeting-308:12
*** MarkAtwood has quit IRC08:14
*** stevemar_ has quit IRC08:16
*** salv-orlando has joined #openstack-meeting-308:19
*** oetrog has joined #openstack-meeting-308:19
*** safchain has joined #openstack-meeting-308:20
*** vgridnev has quit IRC08:21
*** annp has quit IRC08:24
*** salv-orlando has quit IRC08:27
*** yamamoto has quit IRC08:28
*** JeanBriceCombebi has joined #openstack-meeting-308:35
*** jlanoux has joined #openstack-meeting-308:45
*** trinaths has left #openstack-meeting-308:46
*** numans has quit IRC08:47
*** emalin has joined #openstack-meeting-308:49
*** Guest26061 has quit IRC08:55
*** aheller has joined #openstack-meeting-308:56
*** ayah has joined #openstack-meeting-308:56
*** eyalb has joined #openstack-meeting-308:56
*** lhartal has joined #openstack-meeting-308:57
*** nadav_yakar has joined #openstack-meeting-308:57
*** numans has joined #openstack-meeting-308:57
*** ifat_afek_ has joined #openstack-meeting-308:59
*** emalin has left #openstack-meeting-308:59
*** bruno has joined #openstack-meeting-308:59
*** ihrachys has joined #openstack-meeting-309:00
*** bruno is now known as Guest1613509:00
ifat_afek_#startmeeting vitrage09:00
openstackMeeting started Wed Nov 18 09:00:20 2015 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
ifat_afek_Hi everyone 09:00
ifat_afek_Our agenda today:09:00
ifat_afek_* Current status and progress from last week09:00
*** umargolin has joined #openstack-meeting-309:01
ifat_afek_* Review action items09:01
*** emalin has joined #openstack-meeting-309:01
ifat_afek_* Next steps09:01
ifat_afek_* Open Discussion09:01
*** elisha_rosenswei has joined #openstack-meeting-309:01
ifat_afek_#topic Current status and progress from last week09:01
*** openstack changes topic to "Current status and progress from last week (Meeting topic: vitrage)"09:01
ifat_afek_Almost all of our blueprints are up to date, and in the process of being reviewed.09:01
*** amir_gur has joined #openstack-meeting-309:02
ifat_afek_. Missing one blueprint with the use cases we are about to support in mitaka.09:02
*** idan_hefetz has joined #openstack-meeting-309:02
ifat_afek_Please invest the time to review each-other’s blueprints.09:02
ifat_afek_We have also asked people from Pinpoint, Doctor, Ceilometer and Monasca to review our blueprints. We got some reviews from Gal Sagie from Pinpoint, which is great.09:02
ifat_afek_Let’s try to finish the review process by next week.09:03
elisha_rosensweiTo clarify: the missing bp is related to the RCA/deduced alarm use case. initial use cases for mitaka in other areas of Vitrage have been determined09:03
lhartalWe had a design meeting where we decided on our first use case – show all topology09:04
lhartalWe split the use case into tasks and assign them between us..09:04
lhartalShow all Topology use case includes building the entity graph with Nova.instances and Nova.hosts and exposing show topology API.09:05
nadav_yakarwe have also made a progress in our synchronizer design -09:05
nadav_yakarit is now adapted to listen for openstack message bus notifications09:06
nadav_yakarin addition to the former design which samples OS services via REST API09:06
nadav_yakaronce we finalise this design and break it down to tasks,09:07
nadav_yakarI am going to update our blueprint and gerrit accordingly09:07
ifat_afek_great. once the API is finished, please add it to vitrage wiki page09:07
ifat_afek_lhartal, that goes for your API as well09:08
*** tamari has quit IRC09:08
*** qwebirc9526 has joined #openstack-meeting-309:09
lhartal#action lhartal document API in Vitrage wiki page09:09
nadav_yakarifat, we are not currently planning on revealing any external API09:10
ifat_afek_ok, so no need to document it09:11
nadav_yakarI will clarify - the latest design is that we are going to be used as an internal library by vitrage09:11
ifat_afek_cool. how is the UI progressing?09:12
ahellerHey.... We have some good news !09:12
ahellerWe have "Hello World" plugin working on the Horizon09:12
oetrog#link http://docs.openstack.org/developer/horizon/plugins.html?cm_mc_uid=47957347875914472483394&cm_mc_sid_50200000=1447685453 we use this as a reference to our vitrage horizon plugin09:13
*** stevemar_ has joined #openstack-meeting-309:13
ahellerWe have a new launchpad for the UI Vitrage project, So we'll move our blueprints09:14
ahellerhttps://launchpad.net/vitrage-dashboard09:14
aheller#link https://launchpad.net/vitrage-dashboard09:14
ifat_afek_that's great news09:15
ahellerWe got some help from robcresswell and it was very helpful09:15
ifat_afek_ok, thanks. any other updates anyone?09:16
*** stevemar_ has quit IRC09:17
eyalbWe created a new python-vitrageclient project and launchpad09:18
eyalbadded some files09:18
elisha_rosensweigreat!09:18
eyalb#link https://launchpad.net/python-vitrageclient09:20
eyalbalso moved the cli blueprint from vitrage to vitrage-pythonclient09:21
ifat_afek_great. so we have one blueprint in vitrage-pythonclient launchpad, and another blueprint on vitrage-dashboard launchpad09:21
*** Piet has quit IRC09:21
nadav_yakarI am currently looking for a best practice for concurrency handling in openstack projects.09:22
nadav_yakarAlthough I see that many projects already use the Eventlet library, I’d rather work with python’s multiprocessing library,  since for my understanding, the later works with processes, in contrast to eventlet.09:22
ifat_afek_and do you know of any project using the multiprocessing library?09:22
ifat_afek_or all use Eventlet?09:23
ayahit is better than use the threading in python09:23
nadav_yakarI have taken a peek at Nova and seen they uses Eventlet,09:23
emalinI think that ceilometer should be good reference09:23
nadav_yakarbut GNOCCHI uses the standard python multiprocessing library\09:24
nadav_yakarI am about to talk with Julian, their PTL09:24
emalinVitrage is more similar to ceilometer than nova09:24
eyalbto my understanding if your program is mostly oi bound then there is no issue with the GIL so you can use threads09:25
eyalb#link https://docs.python.org/2/library/multiprocessing.html09:26
*** salv-orlando has joined #openstack-meeting-309:26
eyalbGIL is always released when doing I/O09:26
eyalb#link https://docs.python.org/2/glossary.html#term-global-interpreter-lock09:27
nadav_yakarthanks Eyal. I will have a look, although that I believe that we'd rather use processes if possible09:28
ifat_afek_ok. let's move on09:29
ifat_afek_#topic Review action items09:29
*** openstack changes topic to "Review action items (Meeting topic: vitrage)"09:29
ifat_afek_let's see if what was our progress regarding the action items from last week09:29
ifat_afek_1. ifat_afek make sure we finish updating our blueprints in the following days09:30
ifat_afek_this is almost done. one blueprint is missing09:30
ifat_afek_#action ifat_afek finish the last blueprint.09:30
ifat_afek_2. talk with them at room openstack-searchlight09:30
*** e0ne has joined #openstack-meeting-309:32
nadav_yakarwe have used searchlight for a reference for using oslo messaging09:32
nadav_yakarso the way that I see it, this AI is done09:33
ifat_afek_no need to talk with them?09:33
nadav_yakarnot at this stage09:33
ifat_afek_ok09:33
ifat_afek_3. all finish the discussions regarding the synchronizer, and optionally update its blueprint09:33
nadav_yakaras I said, we are going to finalize our blueprints once we finish our design and breakdown our tasks09:35
ifat_afek_so it's an action item for next week?09:35
nadav_yakar#action nadav_yakar update synchronizer blueprint and gerrit09:36
ifat_afek_thanks. moving on09:36
ifat_afek_4. all assign blueprints to developers09:36
*** salv-orlando has quit IRC09:36
ifat_afek_done. I assigned the correct developer for each of the blueprints that are going to be implemented in the coming few weeks. Some of them will be implemented by more than one person.09:36
*** salv-orlando has joined #openstack-meeting-309:37
ifat_afek_5. alexey_weyl contact Doctor guys, ask them to review our blueprints09:37
alexey_weylI sent an email to Doctor PTL09:37
alexey_weyland main Doctor contributers09:37
alexey_weylBut they hasn't answered yet09:38
alexey_weylIf the won't answer untill tommorow, I will send them a remainder09:38
*** msambol has joined #openstack-meeting-309:39
ifat_afek_ok09:39
ifat_afek_next09:39
ifat_afek_6. ifat_afek contact PinPoint guys, ask them to review our blueprints09:39
*** yamamoto has joined #openstack-meeting-309:39
ifat_afek_I sent an email to PinPoint guys. Adi said he would review our blueprints. Gal already did09:39
ifat_afek_7. elisha_rosenswei check horizon alarm management blueprint09:40
^Gal^I can update09:40
elisha_rosensweiso we verified the existence of the ceilometer (actually, Aodh) api to list all the alarms, and began checking the ui for this09:41
ifat_afek_go ahead09:41
^Gal^so the Horizon blueprint assigned to sanjana09:41
^Gal^I tried to contact him via mail09:41
^Gal^to offer our assistance and ask where things stand09:42
*** markvoelker has joined #openstack-meeting-309:42
^Gal^I don't know if he's still involved with openstack09:42
ifat_afek_when did you email him?09:42
^Gal^his account doesn't seem active, and I didn't get a reply back09:42
^Gal^week ago09:42
*** tfukushima has joined #openstack-meeting-309:43
^Gal^I would attend Horizon meeting today and ask their ptl for advise09:43
ifat_afek_great09:43
ifat_afek_so it's an action item09:43
elisha_rosensweiOne thing we will need to decide, though, is if we want to use this Aodh ui, or a different one. The main consideration here is to think what we will do if and when we integrate with other projects , like Monasca09:43
*** yamamoto has quit IRC09:43
*** msambol has quit IRC09:44
ifat_afek_#action ^Gal^ understand the status of ceilometer alarms ui blueprint09:44
^Gal^sure do, thanks09:44
*** baohua has quit IRC09:45
ifat_afek_elisha, I think that if we want to push deduced alarms to AODH, we better write the UI on top of AODH09:46
*** markvoelker has quit IRC09:46
ifat_afek_who wants to take this action item?09:48
elisha_rosensweiI'll take it\09:48
elisha_rosenswei#action elisha_rosensweig decide on where to get the list alarms ui09:49
nadav_yakar#action nadav_yakar find a best practice for concurrency handling in openstack projects09:49
*** ohad has joined #openstack-meeting-309:49
*** tfukushima has quit IRC09:50
ifat_afek_ok. let's move to the next topic...09:50
ifat_afek_#topic Next Steps09:50
*** openstack changes topic to "Next Steps (Meeting topic: vitrage)"09:50
ifat_afek_I think we talked about most of them already09:50
ifat_afek_#action finish review of the blueprints09:50
ifat_afek_hopefully by next week our blueprints should pass review09:50
ifat_afek_anything else?09:51
ifat_afek_#topic Open Discussion09:52
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"09:52
*** ohad has joined #openstack-meeting-309:52
elisha_rosensweiOne thing we will need to decide regarding the interaction of the Synchronizer and the graph. Do we assume that all the information, including which resources to attach to in the graph, is contained in the event? or can/should the graph query for additional info after an event arrives?09:54
alexey_weylGood question Elisha09:54
*** umargolin has quit IRC09:55
nadav_yakarelisha, we are still in the process of investigating which data is available for each entity on the message bus09:56
emalinI think it's specific to each entity and reach event09:56
nadav_yakarthis is an ongoing task09:56
emalin*each09:57
nadav_yakartrue09:57
nadav_yakarhence it would be an ongoing task09:57
lhartalHopefully we want to get all the needed info and the initial event. this will help us in performence  - because we dont want to query back and forth for each event09:57
alexey_weylWe should sit and check this more thoroughly09:58
*** ohad has quit IRC09:58
*** amir_gur has quit IRC09:58
*** ohad_ has joined #openstack-meeting-309:58
ifat_afek_we need to finish, let's discuss it later09:58
ifat_afek_#action decide what information is part of the synchronizer events09:59
ifat_afek_thanks everybody09:59
ifat_afek_#endmeeting09:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:59
openstackMeeting ended Wed Nov 18 09:59:46 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2015/vitrage.2015-11-18-09.00.html09:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2015/vitrage.2015-11-18-09.00.txt09:59
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2015/vitrage.2015-11-18-09.00.log.html09:59
*** alexey_weyl has quit IRC10:00
*** oetrog has quit IRC10:01
*** nadav_yakar has quit IRC10:01
*** elisha_rosenswei has quit IRC10:02
*** umargolin has joined #openstack-meeting-310:02
*** quintela has quit IRC10:02
*** lhartal has quit IRC10:02
*** eyalb has quit IRC10:03
*** vgridnev has joined #openstack-meeting-310:04
*** qwebirc9526 has left #openstack-meeting-310:04
*** ifat_afek_ has quit IRC10:06
*** lhartal has joined #openstack-meeting-310:09
*** aheller has quit IRC10:10
*** ^Gal^ has quit IRC10:13
*** ^Gal^ has joined #openstack-meeting-310:13
*** Guest16135 has quit IRC10:19
*** JeanBriceCombebi has quit IRC10:21
*** davidsha has joined #openstack-meeting-310:26
*** yamamoto has joined #openstack-meeting-310:26
*** omer_etrog has joined #openstack-meeting-310:30
*** bruno_ has joined #openstack-meeting-310:30
*** JeanBriceCombebi has joined #openstack-meeting-310:30
*** yamamoto has quit IRC10:31
*** qwebirc72848 has joined #openstack-meeting-310:36
*** ktatsuro has quit IRC10:37
*** ihrachys has quit IRC10:38
*** sankarshan is now known as sankarshan_away10:39
*** emalin has quit IRC10:41
*** umargolin has quit IRC10:42
*** e0ne has quit IRC10:43
*** egallen has quit IRC10:45
*** ziggypup has joined #openstack-meeting-310:46
*** ziggypup has left #openstack-meeting-310:46
*** amotoki has quit IRC10:47
*** stanzgy has quit IRC10:49
*** ^Gal^ has quit IRC10:52
*** lhartal has quit IRC10:54
*** ^Gal^ has joined #openstack-meeting-310:57
*** omer_etrog has quit IRC10:57
*** JeanBriceCombebi has quit IRC11:02
*** e0ne has joined #openstack-meeting-311:04
*** jeblair has quit IRC11:04
*** jeblair has joined #openstack-meeting-311:05
*** jed56 has joined #openstack-meeting-311:06
*** dims has joined #openstack-meeting-311:07
*** dims has quit IRC11:12
*** stevemar_ has joined #openstack-meeting-311:14
*** bruno_ has quit IRC11:17
*** stevemar_ has quit IRC11:18
*** klkumar has quit IRC11:18
*** dims has joined #openstack-meeting-311:18
*** klkumar has joined #openstack-meeting-311:18
*** zhenguo has quit IRC11:27
*** armenaghasar has joined #openstack-meeting-311:28
*** klkumar has quit IRC11:29
*** klkumar has joined #openstack-meeting-311:30
*** yamamoto has joined #openstack-meeting-311:32
*** mwagner has quit IRC11:34
*** vgridnev has quit IRC11:35
*** wojdev has joined #openstack-meeting-311:35
*** yamamoto has quit IRC11:36
*** ihrachys has joined #openstack-meeting-311:40
*** deshipu has left #openstack-meeting-311:41
*** subscope has quit IRC11:41
*** msambol has joined #openstack-meeting-311:41
*** ayah has quit IRC11:42
*** ^Gal^ has quit IRC11:42
*** subscope has joined #openstack-meeting-311:42
*** markvoelker has joined #openstack-meeting-311:43
*** armenaghasar is now known as armen_aghasaryan11:44
*** msambol has quit IRC11:45
*** markvoelker has quit IRC11:47
*** amotoki has joined #openstack-meeting-311:48
*** armen_aghasaryan has quit IRC11:48
*** amotoki has quit IRC11:49
*** robcresswell has joined #openstack-meeting-311:55
*** armen_aghasaryan has joined #openstack-meeting-311:55
*** jhesketh has quit IRC11:55
*** armen_aghasaryan has quit IRC11:55
*** masco has joined #openstack-meeting-311:57
david-lyle#startmeeting HorizonDrivers12:00
openstackMeeting started Wed Nov 18 12:00:34 2015 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: HorizonDrivers)"12:00
openstackThe meeting name has been set to 'horizondrivers'12:00
david-lyleanyone around?12:00
robcresswello/12:00
*** jhesketh has joined #openstack-meeting-312:00
robcresswellWell. Bet you're glad you got up for this one.12:01
*** ^Gal^ has joined #openstack-meeting-312:02
*** doug-fish has joined #openstack-meeting-312:02
*** egallen has joined #openstack-meeting-312:02
david-lylewondering about the long term benefit of this time12:02
david-lylefor a meeting12:02
david-lylethe attendance is generally sparse and the usual suspects typically show for the 2000 UTC12:03
david-lyle:/12:03
mascoo/12:03
david-lyleI looked at the bug list yesterday, > 100012:04
robcresswellYeah, we can just do it every other week at 200UTC I guess12:04
robcresswell:(12:04
robcresswellI just don't have the time to get to get on top of it right now12:04
mrungeo/12:05
david-lyleme either, looked at many yesterday12:05
david-lylesome are very old, and I'm not sure still valid12:05
david-lylebut checking them all is very time consuming12:05
robcresswellAgreed12:05
mascomay be interested people dived with us and validate12:06
mascoand we can discuss during the meeting12:06
*** ohad_ has quit IRC12:06
robcresswellHow would you like to scope cleanup of bugs? I'm inclined to be more aggressive about it, like I was with the bps.12:06
*** betherly has joined #openstack-meeting-312:07
david-lylewe could organize a bug day too for horizon12:07
david-lylejust have people focus on triaging and classifying bugs12:07
david-lyleand cross talk on questions12:07
mrungethat'd be helpful12:07
doug-fishI thought we already tried the bug day thing12:07
doug-fishwasn't Wednesday supposed to be bug day?12:07
david-lyledoug-fish: ?12:08
mrungewho can set the status of a bug?12:08
mascobut we are not following the bug day, i guess12:08
robcresswellIt was brought up a few weeks back12:08
david-lylemrunge: anyone on the horizon-bugs team12:08
mrungeI mean, who can remove assignees?12:08
robcresswellmrunge: I think anyone can assign themselves, unsure about just removing12:09
david-lylesee my above answer12:09
mrungegot you12:09
mrungethanks12:09
david-lylehorizon-bugs is core + a few12:09
david-lylealthough most of the few are now core I think :-)12:09
robcresswell:D12:10
david-lyleI didn't follow through with scheduling a bug day yet, if we agreed to that in the past12:10
mrungeI can't remember that12:10
robcresswellI definitely recall a discussion12:10
david-lylewhich I don't remember12:10
robcresswellMay be going mad...12:10
doug-fishMaybe it didn't happen. Maybe I'm having visions of the future?12:10
david-lylewell I'm forgetful at 5 am too12:11
betherlydoug-fish: time travel12:11
mrungethat hurts, david-lyle12:11
betherlybtw, hi all! :D12:11
doug-fishbetherly: could be. What year is it?12:11
betherly208012:11
mrungewhen do you have dst switch?12:11
doug-fish:-)12:11
doug-fishmrunge: daylight savings change was about 2 weeks ago12:12
david-lylewhile we were in tokyo went to off DST, not back on until spring12:12
betherlydst is annoying12:13
mrungedoug-fish, aha, same for us. I assumed, those times would become saner for you. apparently it did not12:13
mrungethey did not, I meant12:13
mrungeI like the idea of cleaning bugs12:13
mrungethat could even mean, scrub bugs not touched for > 1 year12:14
robcresswellFirst though; do we want to keep this meeting slot?12:14
mrungeI'm +1 for moving to 20 UTC12:14
doug-fish20 UTC is better for me12:15
robcresswellOf the cores its only myself and matthias that this is easier for and usually attend I think12:15
mrungebut that will exclude amotoki12:15
robcresswellAnd I'll nearly always attend the respective 2000UTC anyway12:15
robcresswellAh, true12:15
mrungebut yes robcresswell you're right12:15
mrungemasco, does a meeting at 20 UTC work for you?12:16
mrungethat is in about 8 hours?12:16
mascono way12:16
robcresswellhaha12:16
mascoit is 1 am in india12:16
robcresswellThere is still the usual Horizon meeting12:16
robcresswellThis is just the drivers meeting we're talking about changing.12:16
mrungedavid-lyle, robcresswell the other idea would be to switch session chairs12:17
*** tg has joined #openstack-meeting-312:17
robcresswellThat also works12:17
mrungesince usual suspects like robcresswell and me will attend the other meeting anyways12:17
*** tg is now known as Guest8252712:17
robcresswellAlthough, then it would just be me and mrunge, I expect :p12:17
*** Guest82527 has left #openstack-meeting-312:18
mrungeand masco, amotoki and a few others, who could not attend at 20 UTC12:18
robcresswellSure12:18
* mrunge looking at timur12:18
robcresswellAh yes, he's on PTO I believe12:18
robcresswelldavid-lyle: How does that sound? Me or mrunge could just chair so you don't have to be dragged out of bed at 5am.12:19
robcresswellThe counter point tbh though, is that there isnt much value in a bp discussion with 4/5 people, vs 10 - 20.12:19
david-lylerobcresswell: I don't mind being here at 5am, my concern was more around having a quorum12:19
mrungeand we could use this time for example to clean up bugs12:20
*** shaohe_feng has quit IRC12:20
mrungeright12:20
david-lylebut triaging bugs is a worthy goal as well12:20
robcresswellAlternate bug/bp cleanup?12:20
*** subscope has quit IRC12:20
robcresswellThat sounds sensible12:20
mrungesounds good to me12:20
masco+1 for alternate12:20
*** subscope has joined #openstack-meeting-312:21
*** subscope has quit IRC12:21
david-lyleso do we want to do bps or bugs today?12:21
mrungeI would like to talk about the bp we left undecided last time12:22
mrunge(the local-settings.d one)12:22
mrungebut it was quite controversial12:22
mrungeit might be fairer to move that to the weekly meeting at 20 UTC?12:22
robcresswellI just commented a small while ago12:22
mrungeI just saw that12:23
david-lylemrunge: agree that might be better for 200012:23
robcresswellShall we run through a few bugs then?12:24
mrungeyes please12:24
masco+112:24
david-lylesure12:24
mrungeunfortunately I have to drop off, kid#1 just arrived, demanding lunch12:24
robcresswelldammit kid#¡12:25
*** aarefiev has quit IRC12:25
david-lylemention bugs and people run ;-)12:25
robcresswellha12:25
mrungehahaha12:25
david-lylemrunge: no worries12:25
mrungeat least, I didn't try to assign people to bugs12:25
robcresswellWe might assign some to you while you're gone12:25
david-lyleso I started looking at bugs again yesterday12:26
david-lyleonly about the first 400 even have a priority12:26
david-lylethe next 602 are still undecided12:27
*** aarefiev has joined #openstack-meeting-312:27
*** jkraj has joined #openstack-meeting-312:28
david-lylebut that's not to say all that have a priority set are still valid either12:28
mascofix got merged but still in inprogress https://bugs.launchpad.net/horizon/+bug/146104712:29
openstackLaunchpad bug 1461047 in OpenStack Dashboard (Horizon) "description column is missing in firewall tables" [Undecided,In progress] - Assigned to Masco (masco)12:29
robcresswellI think it might help to define at what point we can just cut a bug and wait for it to be revived if its still an issue12:29
david-lylemasco: fixed12:30
david-lylethanks12:30
mascono problem12:30
david-lylerobcresswell: bugs are harder to cut IMO12:31
david-lylethey really only get cut if they are invalid12:31
david-lylejust because no one has worked on it in 2 years, it can still be a bug12:31
mascoi think that should be fix released i guess12:31
doug-fishmasco: it is again - that was my mistake12:32
david-lylewhile for feature addition, it's just an idea and we can just remove12:32
mascodoug-fish, no problem12:32
david-lyleI would say that most bugs around for 2 years that are valid are either low priority, or blocked12:33
robcresswellSure. I'm just wondering if there's much value in having 800 low bugs that nobody has either the time or money to be inclined to solve.12:33
*** baohua has joined #openstack-meeting-312:33
*** ihrachys_ has joined #openstack-meeting-312:34
robcresswellWe can definitely work on prioritising those 600 that are just unreviewed though12:34
mascohttps://bugs.launchpad.net/horizon/+bug/1461018 same issue12:34
openstackLaunchpad bug 1461018 in OpenStack Dashboard (Horizon) "description column is missing in vpn tables" [Undecided,In progress] - Assigned to Masco (masco)12:34
robcresswellmasco: Done12:35
*** ihrachys has quit IRC12:35
mascothanks rob12:35
*** lhartal has joined #openstack-meeting-312:37
doug-fishwhat about https://bugs.launchpad.net/horizon/+bug/1282089 ? that's been open for a long time and is "high" priority12:38
openstackLaunchpad bug 1282089 in OpenStack Dashboard (Horizon) "keystone client is leaving hanging connections to the server" [High,Confirmed]12:38
*** mbound has joined #openstack-meeting-312:39
*** yamamoto has joined #openstack-meeting-312:39
david-lyledoug-fish: not entirely sure on that one.12:40
doug-fishI'll spend a few mins with it and see if it is still recreatable12:40
david-lylethanks!12:40
david-lyleyeah a lot of these take a fair amount of effort to reproduce12:41
*** ifat_afek has joined #openstack-meeting-312:41
*** mbound has quit IRC12:41
robcresswellSpeak to neillc, it looks like he looked over it recently12:41
doug-fishrobcresswell: sure, sounds good!12:42
robcresswellI'm not sure group discussion of bugs is that helpful? We just need to spend time on it, probably instead of meetings.12:43
*** markvoelker has joined #openstack-meeting-312:43
mascoyes rob, if anything needs to discuss then we can talk in meetings.12:44
david-lylerobcresswell: true12:44
david-lyleI think a bug day is more effective12:45
david-lyleeveryone dives into some and cross-talks as necessary12:45
robcresswellYup12:45
doug-fishworks for me12:45
doug-fishSome tips for what to do on bug day: https://wiki.openstack.org/wiki/BugTriage12:45
mascoi saw some bugs with abandoned patch, what action need to taken on that?12:46
*** vgridnev has joined #openstack-meeting-312:47
david-lylemasco: probably best course on those is to remove the owner12:47
doug-fishmasco: maybe reset from in-progress to new as well12:47
david-lyleif the patch is abandoned and not quickly revived, I don't think they are actively working on it12:48
*** markvoelker has quit IRC12:48
mascolooks good12:48
david-lylerobcresswell: what linting tool are you proposing for SCSS linting?12:48
mascoi don't have permission to do that.12:48
david-lyle#link https://blueprints.launchpad.net/horizon/+spec/scss-lint12:48
* david-lyle went back to bps :P12:48
mascoif i find anything i will ask some of you guys12:48
*** pkarikh_ has joined #openstack-meeting-312:48
robcresswelldavid-lyle: Oh, you can scrap that12:49
robcresswellI was chatting with diana the other day and considering adding something12:49
robcresswellafter about 10 minutes I noped outta there12:49
david-lylegone12:49
david-lyle#info https://blueprints.launchpad.net/horizon/+spec/scss-lint marked obsolete12:49
*** mbound has joined #openstack-meeting-312:50
robcresswellhttps://blueprints.launchpad.net/horizon/+spec/bootstrap-theme-preview << This one, possibly?12:51
david-lyle#info https://blueprints.launchpad.net/horizon/+spec/integrate-magic-search approved per summit discussions12:51
david-lyle#info https://blueprints.launchpad.net/horizon/+spec/bootstrap-theme-preview approved12:52
david-lyleI did mark it low12:52
robcresswelltoo much markup..?12:53
*** klkumar has quit IRC12:53
david-lyleexactly12:54
*** e0ne has quit IRC12:57
robcresswellWhen did we want to hold this bug day?12:58
robcresswellI'm sure previously we said thursday, but I cant find it in the logs12:58
robcresswellWhich worries me, because now I think I may have dreamed of Horizon having a bug day.12:58
doug-fishno! it happened!12:58
mascowe planed12:59
mascobut not executed12:59
david-lyleI must have missed an action assigned to me12:59
doug-fishhmm, maybe this explains the low participation12:59
robcresswellSo... Thursday bug day?12:59
*** sreshetnyak has quit IRC13:00
mascono issue for me13:00
david-lyle#info https://blueprints.launchpad.net/horizon/+spec/address-scopes marked drafting13:00
doug-fishmaybe make it clear its "Bug Triage day", not a day to find more bugs!13:01
mascoi think it is about adding a new panel for address scope13:01
david-lyle#info https://blueprints.launchpad.net/horizon/+spec/bp-cisco-fwaas-horizon marked obsolete13:02
david-lyletime's over, but...13:03
david-lyleI think if we continue to hold this meeting, it needs to stay on bps and leave bug triage for bug days13:03
*** obondarev_afk is now known as obondarev13:04
david-lyleI'm going to sidestep the action this time13:04
robcresswellI honestly don't think we really need it. We still have the usual horizon meeting anyway. This was just for bps, and all the attending cores are happy to do 2000UTC...13:04
david-lyledoes someone want to post an email to the dev mailing list re: bug day?13:04
robcresswellSure. Are we intending it to be weekly?13:05
david-lylerobcresswell: oh no13:05
robcresswellhaha13:05
david-lyleI would like to hold one and see how it goes13:05
robcresswellShall we say a week on Thursday then?13:05
david-lyleif we get decent numbers we can make significant progress13:05
david-lylerobcresswell: sure13:05
doug-fishThanksgiving13:06
*** tfukushima has joined #openstack-meeting-313:06
david-lyleerr no then13:06
robcresswell>.<13:06
robcresswellLets discuss later when its not 5am.13:06
david-lyleok :)13:06
masco:)13:06
robcresswellAnd then I'll send out an email :)13:06
david-lylethanks13:06
david-lyleThanks everyone!13:07
mascothanks13:07
david-lyle#endmeeting13:07
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:07
openstackMeeting ended Wed Nov 18 13:07:21 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:07
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizondrivers/2015/horizondrivers.2015-11-18-12.00.html13:07
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizondrivers/2015/horizondrivers.2015-11-18-12.00.txt13:07
openstackLog:            http://eavesdrop.openstack.org/meetings/horizondrivers/2015/horizondrivers.2015-11-18-12.00.log.html13:07
*** robcresswell has left #openstack-meeting-313:07
*** tfukushima has quit IRC13:07
*** armen_aghasaryan has joined #openstack-meeting-313:08
armen_aghasaryan13:09
*** markvoelker has joined #openstack-meeting-313:09
*** e0ne has joined #openstack-meeting-313:10
*** JeanBriceCombebi has joined #openstack-meeting-313:12
*** masco has left #openstack-meeting-313:12
*** armen_aghasaryan has left #openstack-meeting-313:12
*** klkumar has joined #openstack-meeting-313:13
*** jckasper has quit IRC13:13
*** ifat_afek has left #openstack-meeting-313:13
*** armen_aghasaryan has joined #openstack-meeting-313:14
*** armen_aghasaryan has quit IRC13:14
*** stevemar_ has joined #openstack-meeting-313:15
*** peristeri has joined #openstack-meeting-313:17
*** lhartal has quit IRC13:17
*** stevemar_ has quit IRC13:18
*** ihrachys_ has quit IRC13:18
*** ihrachys has joined #openstack-meeting-313:19
*** pavel_bondar_ has joined #openstack-meeting-313:21
*** irenab_ has joined #openstack-meeting-313:26
*** irenab has quit IRC13:27
*** irenab_ is now known as irenab13:27
*** JeanBriceCombebi has quit IRC13:31
*** ryu_ishimoto has quit IRC13:34
*** egallen has quit IRC13:35
*** kbyrne has quit IRC13:36
*** mwagner has joined #openstack-meeting-313:42
*** msambol has joined #openstack-meeting-313:43
*** kbyrne has joined #openstack-meeting-313:43
*** igordcard has joined #openstack-meeting-313:44
*** msambol has quit IRC13:45
*** krtaylor has joined #openstack-meeting-313:46
*** msambol has joined #openstack-meeting-313:46
*** egallen has joined #openstack-meeting-313:46
*** egallen has quit IRC13:49
*** alexstav has joined #openstack-meeting-313:50
*** alexchadin has joined #openstack-meeting-313:50
*** ostroverkhov has joined #openstack-meeting-313:51
*** absubram has joined #openstack-meeting-313:52
*** julim has joined #openstack-meeting-313:55
*** bruno has joined #openstack-meeting-313:56
*** bruno is now known as brunograz13:56
*** alexchadin has quit IRC13:57
*** alexchadin has joined #openstack-meeting-313:57
*** doug-fish has quit IRC13:58
*** MarkAtwood has joined #openstack-meeting-313:59
*** Aish has joined #openstack-meeting-314:00
*** tpeoples_away is now known as tpeoples14:01
*** betherly has left #openstack-meeting-314:01
*** Aish has quit IRC14:01
*** vmahe_ has joined #openstack-meeting-314:02
*** sankarshan_away is now known as sankarshan14:02
*** ShillaSaebi has joined #openstack-meeting-314:05
*** ShillaSaebi has left #openstack-meeting-314:05
*** jckasper has joined #openstack-meeting-314:05
*** bapalm has joined #openstack-meeting-314:08
*** bryan_att has joined #openstack-meeting-314:10
*** zz_dimtruck is now known as dimtruck14:13
*** MarkAtwood has quit IRC14:13
*** iyamahat has joined #openstack-meeting-314:17
*** jpomeroy has joined #openstack-meeting-314:18
*** terrylhowe has left #openstack-meeting-314:18
*** yamamoto has quit IRC14:19
*** pkarikh_ has quit IRC14:20
*** doug-fish has joined #openstack-meeting-314:21
*** lblanchard has joined #openstack-meeting-314:21
*** jaypipes has joined #openstack-meeting-314:23
*** lsmola has quit IRC14:26
*** jmckind has joined #openstack-meeting-314:26
*** absubram has quit IRC14:27
*** shaohe_feng has joined #openstack-meeting-314:29
*** lsmola has joined #openstack-meeting-314:29
*** lsmola has quit IRC14:31
*** s-kawabata_ has joined #openstack-meeting-314:35
*** msambol has quit IRC14:35
*** jckasper has quit IRC14:37
*** jkraj has quit IRC14:37
*** Swami has joined #openstack-meeting-314:39
*** bapalm has quit IRC14:43
*** bapalm has joined #openstack-meeting-314:43
*** bklei has joined #openstack-meeting-314:44
*** dconde has joined #openstack-meeting-314:46
*** neelashah has joined #openstack-meeting-314:47
*** jckasper has joined #openstack-meeting-314:49
*** iyamahat has quit IRC14:50
*** sigmavirus24_awa is now known as sigmavirus2414:52
*** Swami has quit IRC14:55
*** rhochmuth has joined #openstack-meeting-314:56
*** lin_yang_ has joined #openstack-meeting-314:57
*** bmotz has joined #openstack-meeting-314:57
*** witek has joined #openstack-meeting-314:57
*** Munish__ has joined #openstack-meeting-314:57
*** ddieterly has joined #openstack-meeting-314:57
*** zawisza has joined #openstack-meeting-314:58
*** mbound has quit IRC14:58
*** brunograz has quit IRC14:59
*** Swami has joined #openstack-meeting-314:59
*** tgraichen has joined #openstack-meeting-314:59
*** neelashah has quit IRC15:00
*** tomasztrebski has joined #openstack-meeting-315:00
*** fitoduarte has joined #openstack-meeting-315:00
*** davidmichaelkarr has joined #openstack-meeting-315:00
*** rbak has joined #openstack-meeting-315:01
*** Kuckkuck has joined #openstack-meeting-315:01
*** bruno has joined #openstack-meeting-315:01
*** bmotz has left #openstack-meeting-315:01
*** bmotz has joined #openstack-meeting-315:01
*** ddieterly has quit IRC15:01
*** fabiog has joined #openstack-meeting-315:01
*** bruno is now known as Guest210615:01
rhochmuth#startmeeting monasca15:01
openstackMeeting started Wed Nov 18 15:01:40 2015 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: monasca)"15:01
openstackThe meeting name has been set to 'monasca'15:01
rhochmutho/15:01
*** ddieterly has joined #openstack-meeting-315:01
bkleio/15:01
fabiogo/15:01
tomasztrebskio/15:01
witekhi15:02
bmotzo/15:02
ddieterlyo/15:02
rbako/15:02
s-kawabata_o/15:02
rhochmuthhello everyone15:02
bkleigood morning!15:02
ddieterly\o/15:02
rhochmuthPlease add to agenda at, https://etherpad.openstack.org/p/monasca-team-meeting-agenda15:02
witekgood afternoon :)15:02
tgraichengood afternoon15:02
tomasztrebskimore or less evening even :-)15:02
rhochmuthgooten morgen15:02
bklei:)15:02
s-kawabata_good night :)15:03
tomasztrebski0-015:03
*** neiljerram has joined #openstack-meeting-315:03
*** alexchadin has quit IRC15:03
rhochmuth#topic GPL in monasca-{common, api}15:03
*** openstack changes topic to "GPL in monasca-{common, api} (Meeting topic: monasca)"15:03
ddieterlyGunter glieben glauchen globen15:03
rhochmuthanyone got something to say15:04
bkleibesides we like def lepard?15:04
rhochmuthThe topic is the GPL MySQL library in monasca-common15:04
ddieterlybklei: +115:04
witekyes, we have that mysql-python dependency15:04
*** jckasper has quit IRC15:04
witekwhich brings GPL2 license15:04
rhochmuthThat library isn't an issue for HP15:04
witekApache2 is not compatible with GPL215:05
rhochmuthWe reviewed with our legal15:05
witekhttp://www.gnu.org/licenses/license-list.html#apache215:05
rhochmuthI don't really want to get into why HP Legal feels like we are covered15:05
witekand frankly, we have very little chances that our legal department will let us go with it15:05
*** klkumar has quit IRC15:05
rhochmuthand would rather focus on getting this resolved for the entire community15:06
rhochmuthso, there is an alternative MIT licencsed mysql library15:06
*** vgridnev has quit IRC15:06
witekyes, pymysql15:06
rhochmuthis it a drop in replacement for the MySQL library15:06
witekwe could also take sqlalchemy to make DB replaceble15:07
*** tsv has joined #openstack-meeting-315:07
fabiog+115:07
rhochmuthIf it is, then I think we could modify the requirements file, do some testing to confirm no issues and move on15:07
bklei+1 on avoiding lawyer discussions15:07
*** subscope has joined #openstack-meeting-315:08
ddieterlybklei: the party of the first part agrees with the party of the second part...15:08
rhochmuthSo, SQL alchemy is a much bigger fix15:08
rhochmuthchange15:08
witekyes, but we would definitely be interested in it15:09
witekwithout orm though15:09
rhochmuthWe could debate SQLAlchemy vs hand-written SQL statements and never get anywhere15:09
witekwhat do you mean?15:10
*** egallen has joined #openstack-meeting-315:10
rhochmuthSQLAlchemy can often get in the way15:10
tomasztrebskisimply that there are as many advantages as there is disadvantages for ORM solutions15:11
rhochmuthYes15:11
witekyou can use sqlalchemy without orm15:12
*** ostroverkhov has quit IRC15:12
tomasztrebskiI believe that this is something we did in monasca-notification, right ?15:13
rhochmuthsorry, i'm not an expert on sqlalchemy15:13
witekanyway, i think replacing mysql-python with pymysql ist worth a try15:14
tomasztrebskiok, maybe let's not debate over that matter right now, we have more urgent issue about this GLP stuff15:14
rhochmuthOK, so if the pymysql library is a drop in replacment, that the rest of OpenStack is using, then I would say let's convert over and see if it works15:15
tomasztrebskithere are also other things, that basically from what I learned openstack projects are more or less MIT, Apache2...BSD is less common, and if there's a GPL it is most likely LGLP which is compatible with Apache215:15
rhochmuthwe did somethign similar with the drizzle drive for Java recently15:15
*** stevemar_ has joined #openstack-meeting-315:16
*** cloudtrainme has joined #openstack-meeting-315:16
*** egallen has quit IRC15:16
*** JesseO has joined #openstack-meeting-315:16
*** shaohe_feng has quit IRC15:16
*** jckasper has joined #openstack-meeting-315:16
tomasztrebskias well as the library seems to be active, as I mentioned in mailing list MySQL-Python had recent activity at github over 2 year ago15:16
*** sarob has quit IRC15:16
tomasztrebskiin opposite to pymysql15:17
rhochmuth2 years is a long time15:17
*** sballe has quit IRC15:17
rhochmuthso, let's try converting, then we can discuss sqlalchemy another day15:17
tomasztrebskiI think that anyone'd agree that this is rather a huge gap in IT15:17
*** alexstav has quit IRC15:17
tomasztrebski+115:17
witek+115:17
rhochmuthWhat is the huge gap?15:18
*** sballe has joined #openstack-meeting-315:18
tomasztrebski2 years in development of..pretty much any application, library15:18
rhochmuthoh yes15:18
*** stevemar_ has quit IRC15:18
tomasztrebskijust to close down that subject, porting to pymysql means changes in monasca-{api, thresh, common}, is there is something I forgot ?15:19
*** sarob has joined #openstack-meeting-315:19
s-kawabata_not maintained software is dead I often heard.15:19
rhochmuthI think that is it15:19
*** yamamoto has joined #openstack-meeting-315:20
rhochmuthChanges to requirements are only necessary, right?15:20
*** baohua has quit IRC15:20
witekhave to test15:20
*** sdake has quit IRC15:20
rhochmuthcorrect15:20
*** sdake has joined #openstack-meeting-315:20
rhochmuthno changes to monasca-thresh as that is java only right now15:20
rhochmuthmonasca-persister doesn't use MySQL15:20
rhochmuthmonasca-notification has to be changed15:21
*** rbrndt has joined #openstack-meeting-315:21
rhochmuthmonasca-api, monasca-notification, monasca-common15:21
rhochmuthi think that is the list15:21
witek#action test pymysql replacement for mysql-python15:22
rhochmuthi think that is relatively easy with the new Tempest tests that are in CI15:22
rhochmuthOK, how about a new topic15:23
tomasztrebski+115:23
rhochmuththat was a lot of fun though15:23
tomasztrebski;-)15:23
witek+115:23
rhochmuthwhat topics from last week didn't we cover15:23
*** egallen has joined #openstack-meeting-315:23
rhochmuththat we should go into detail on15:23
bkleinone from me15:24
rhochmuthor discuss15:24
tomasztrebskiI'd like to go with my tempest test and one question from me15:24
rhochmuthok15:24
rhochmuth#topic tempest15:24
*** openstack changes topic to "tempest (Meeting topic: monasca)"15:24
rhochmuthtomasz, the floor is yours15:24
*** mhoppal has joined #openstack-meeting-315:24
tomasztrebskirecently I finally managed to find a time to get back to alarm state history, basically with the fix in gerrit I proposed old tests in AlarmStateHistory are passing in 100%, plus I wrote a new one15:25
tomasztrebskiI tried to present changing the offset (i.e. paging) with changed limit, so every possible combination15:25
tomasztrebskiit also passes15:25
*** vgridnev has joined #openstack-meeting-315:25
*** yamamoto has quit IRC15:25
rhochmuthIs this "Fix for alarm history paging"15:25
tomasztrebskiyeah, that's one15:26
tomasztrebskiusing monasca-api github-master, I have failures, not only in new test but also in those that were already there15:26
ddieterlytomasztrebski: not all tests are passing currently15:27
ddieterlywe are working on that15:27
*** vgridnev has quit IRC15:27
tomasztrebskibut do you mean not all regarding alarm state history ? I concentrated only on that specific test15:27
tomasztrebskiand yesterday when I finished I repeated this this about 9 times and had 9 success15:28
rhochmuthThese changes were in the Java API, and the Java API, was close to 100%.15:28
rhochmuthI think I was seeign only 2 tests fail.15:28
ddieterlyi'm not sure which tests are not passing, but there are a lot that don't pass with the python15:28
rhochmuthThere are 17  passes in the Python API that don't pass15:28
rhochmuthAs far as I know, only 2 fail in Java15:29
*** mbound has joined #openstack-meeting-315:29
rhochmuthSo, we are trying to get that resolved ASAP15:29
rhochmuthSo, what should we do?15:29
rhochmuthSeem liek you think the code is ready to go15:30
tomasztrebskiyes, but only for the java, honestly I did not even think of python:(15:30
rhochmuthSo, we could take a look and run the tests too15:30
*** salv-orlando has quit IRC15:30
tomasztrebskiI think I was too happy that I saw success :D15:30
rhochmuthOK, we'll take a look and render a verdict15:30
tomasztrebskiplease do, thx15:31
*** salv-orlando has joined #openstack-meeting-315:31
rhochmuthtrying to keep the legal theme going today15:31
bklei:)15:31
rhochmuthok, next topic15:31
rhochmuththanks for the test tomasz15:31
rhochmuthand the bug fix15:31
tomasztrebskiif I may, just short question only15:31
tomasztrebskinp :)15:31
rhochmuthsure15:31
*** lazy_prince has joined #openstack-meeting-315:32
rhochmuthschnell, schnell15:32
tomasztrebskido you have any recipe regarding monitoring an app ? For instance I was thinking on adding some metrics to monasca log api, but clearly I have no idea how to do that ? I was a project - monasca-statsd, but I am not sure if that's a right way to go, if I'd like to use monasca-agent to collects stats from monasca-log-apo15:32
tomasztrebskiand ideally create some alarms15:33
witekTomasz is not German, he's Polish :)15:33
rhochmuthSorry, i couldn't resist :-)15:33
*** Kuckkuck has quit IRC15:33
tomasztrebski"szybciej, szybciej" or "ruchy ruchy" if you please :)15:33
tomasztrebskithat's the polish way...I mean polite one :)15:33
tgraichendon't know if it fits here - i had a look at the grafana2 integration from rbak and it looked quite good to me so far - is there any rough timeline for the real keystone integration into the monasca datasource in grafana2?15:34
*** duartea has quit IRC15:34
rhochmuthGetting back the the question15:34
rhochmuthi think monasca-statsd is one good way15:34
rhochmuthit is basically a statsd library with the ability to provide dimensions15:35
*** msambol has joined #openstack-meeting-315:36
tomasztrebskimhm, but do you guys plan to use that for instance for python monasca-api ? I mean, you surely want to have some sort of metrics for main brick in whole system, right ?15:36
rhochmuthyes15:36
rhochmuthwe already instrument the python notification engine using the statsd library15:36
tomasztrebskiand I'd like to keep monasca-log-api in that subject the same as the rest of components15:37
rhochmuthso the goal in the python code is to use statsd for all monitoring of monitoring15:37
rhochmuthso, does that cover that question15:37
tomasztrebskisounds funny :), ok so statsd it is. I don't ask about an agent, it is most likely easy to collect that data later15:37
tomasztrebskiyes, it does, thank you15:38
rhochmuthin hos we deploy the monasc agent on the systems that are running monasca too, and then use statsd for monitoring them in the case of the python components15:38
rhochmuthso we are monitoring monitoring15:38
tomasztrebskisounds cool15:38
*** vgridnev has joined #openstack-meeting-315:38
rhochmuthtgraichen rbak is the engineer doing the grafana 2 integration15:39
rhochmuthrbak are you there?15:39
rhochmuthany updates on grafana 215:39
rbakNothing at the moment.15:40
rbakI got pulled off to work on some other things so hopefully I can get back to grafana soon15:40
*** msambol has quit IRC15:40
*** stevemar_ has joined #openstack-meeting-315:40
tgraichendo you have a complete idea of how the keystone integration should be at the end or are you still in planning stages?15:40
*** vgridnev has quit IRC15:41
rbakJust planning right now.  The auth isn't pluggable so this looks like it's going to be a more complicated change.15:41
rbakAs soon as I know more I'll put the information on the blueprint15:42
tgraichenok - thanks a lot15:42
rhochmuthok, next topic15:42
rhochmuth#topic start/end time args for metrics list change ready for review https://review.openstack.org/#/c/241626/15:42
*** openstack changes topic to "start/end time args for metrics list change ready for review https://review.openstack.org/#/c/241626/ (Meeting topic: monasca)"15:42
bkleithat's me15:42
bklei^^^ is ready from my perspective, bmotz has looked at it, would appreciate more eyes15:43
rhochmuthOK, we'll get to it15:43
bkleigracias15:43
rhochmuthlook like you did java, python and tempest tests15:43
rhochmuthso, i agree looks complete15:44
bkleiyup -- had to blow the dust off my influxdb knowledge :)15:44
*** bpokorny has joined #openstack-meeting-315:44
bkleithx to ddieterly for devstack!15:44
*** vgridnev has joined #openstack-meeting-315:44
ddieterlyur welcome!15:44
bmotzpython looked fine to me, but I did't look at the Java yet15:44
rhochmuththat was me that did that15:44
ddieterlyuh, yea...15:44
bkleithen thx to you rhochmuth!15:44
rhochmuthsorry, inside joke, couldn't resist15:44
bkleigreat for this type of change that touches lots of stuff15:45
rhochmuthddieterly did it15:45
ddieterlywe need to get this review out https://review.openstack.org/#/c/244912/1815:45
bkleioh, then i take it back15:45
rhochmuthjoes are tough in irc15:45
rhochmuthjokes are touch in irc15:45
ddieterlyallows easier development by binding services to externally accessible ip15:45
rhochmuthok, i'll probably just +215:45
bkleilgtm15:46
rhochmuth#topic caching15:46
*** openstack changes topic to "caching (Meeting topic: monasca)"15:46
rhochmuthi started writing some code15:46
bkleicool15:46
rhochmuthunfortunately, i keep getting piled on with meetings15:46
bklei:(15:47
*** qwebirc72848 has quit IRC15:47
rhochmuthi don't have a ETA15:47
bkleinp -- let me know when there's a review to look at15:47
rhochmuthhow long can you wait on this?15:47
bkleisheesh, you know how things are15:47
ddieterlyrhochmuth: do we have a design for that?15:47
*** Sukhdev has joined #openstack-meeting-315:48
rhochmuthi'll review with you15:48
rhochmuthor whoever else want to be involved15:48
rhochmuthbasically adding some hash maps to the measurements repo, similar to the persister15:48
rhochmuthto map from (region, tenant, name, dimensions) => definition_dimensions_id15:49
bkleiare you looking at statistics calls, or statistics and measurements?15:49
*** gabriel-bezerra is now known as gabriel15:49
rhochmuthi'm just look at the measurements right now, but the mechansims is basiclaly the same15:49
ddieterlyis this going to be going into python and java?15:49
rhochmuthonly Java, as this is a Vertica improvment only15:49
bkleino vertica in python, probably not needed15:49
bkleiyeah, what he said15:49
rhochmuth#topic midcycle15:50
*** openstack changes topic to "midcycle (Meeting topic: monasca)"15:50
rhochmuthit is not too soon15:50
rhochmuthto start discussing15:50
bkleicool15:50
bkleiideas on location/hosting?15:50
bkleitwc is in office transition, probably can't host15:51
witekwhen is it planed?15:51
rhochmuthSan Jose or Berlin15:51
fabiogrhochmuth: we can host15:51
fabiogrhochmuth: both in San Jose or Berlin15:51
rhochmuthYes, Cisco was going to host15:51
rhochmuththey have offices in San Jose and Berlin15:52
bkleifabiog maybe you put up another voting site for dates?15:52
fabiogbklei: yes15:52
rhochmuthand locations15:52
bklei+115:52
fabiogwill do that15:52
*** adduarte has joined #openstack-meeting-315:52
rhochmuthjust a quick check then, will folks that are in europe be able to travel to San Jose15:52
fabiogif we do it in SJC I can try to coordinate a joint day/session with Congress15:53
rhochmuthThat would be good to add15:53
witekhave to check15:53
witekwhich month?15:53
fabiogfor SJC in January15:54
tgraicheni think for me and joachim it might be complicated to get to the us - berlin would be perfect though :)15:54
fabiogfor Berlin either week 02/08 or 02/2015:54
rhochmuthbmotz could you travel to berlin or san jose15:54
bkleiwould love to go to berlin, will need to be really nice to my boss to get approval15:55
*** fitoduarte has quit IRC15:55
witekBogdan wanted to organize next one in Munich15:55
witekin Sept15:55
fabiogthere is Cisco Live in Berlin the week of 02/15 so I will be traveling there anyway15:55
rhochmuthyes, that was my preference too15:55
bmotzberlin is probably easier to fit in the travel budget, but further afield isn't impossible15:55
rhochmuthok, thanks bmotz15:56
rhochmuthwe'llk start to need checking with our representative companies15:56
bkleiyup15:56
rhochmuthcan we get to the monasca-log-api in closing15:56
fabiogI'll bring up the subject with Congress too15:56
tsvrhochmuth: +115:57
ddieterlyfabiog: can you talk to the president too? ;-)15:57
rhochmuth#topic monasca-log-api15:57
*** openstack changes topic to "monasca-log-api (Meeting topic: monasca)"15:57
*** egallen has quit IRC15:57
rhochmuthonly 3 minutes15:57
tsv3 reviews :)15:57
fabiogddieterly: in progress ;-)15:58
witektomasz has some code ready, which partly covers same isues15:58
ddieterlycool15:58
*** iyamahat has joined #openstack-meeting-315:58
rhochmuthdidnt' realize you were working on it15:58
rhochmuthtoo15:58
rhochmuthhow soon will your changes be post'd15:59
witeki know, we still have internal reviews15:59
*** zawisza has quit IRC15:59
witekhave to consider to change the workflow15:59
witeknext days15:59
*** yamahata has joined #openstack-meeting-315:59
rhochmuthhow about move discussion to email then15:59
*** cdupont has joined #openstack-meeting-316:00
rhochmuthwe've run out of time16:00
rhochmuthtsv witek and tomasz need to talk off-line16:00
fabiogciao!16:00
*** mounica_ has joined #openstack-meeting-316:00
rhochmuthor in irc16:00
witekok, ciao16:00
bkleithx!16:00
tgraichenbye16:00
ddieterlyciao!16:00
*** adduarte has quit IRC16:00
rhochmuth#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Nov 18 16:00:41 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2015/monasca.2015-11-18-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2015/monasca.2015-11-18-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2015/monasca.2015-11-18-15.01.log.html16:00
*** egallen has joined #openstack-meeting-316:01
*** mhoppal has quit IRC16:01
*** rbrndt has quit IRC16:01
*** msambol has joined #openstack-meeting-316:02
*** bmotz has left #openstack-meeting-316:02
*** fabiog has quit IRC16:03
*** tomasztrebski has quit IRC16:07
*** vgridnev has quit IRC16:07
*** banix has joined #openstack-meeting-316:08
*** ^Gal^_ has joined #openstack-meeting-316:08
*** ^Gal^ has quit IRC16:08
*** ^Gal^_ is now known as ^Gal^16:08
*** cdupont has quit IRC16:10
*** wuhg has quit IRC16:11
*** Guest2106 has quit IRC16:12
*** jaypipes has quit IRC16:13
*** shaohe_feng has joined #openstack-meeting-316:15
*** bruno_ has joined #openstack-meeting-316:15
*** dimtruck is now known as zz_dimtruck16:16
*** tgraichen has quit IRC16:16
*** s-kawabata_ has quit IRC16:18
*** dims_ has joined #openstack-meeting-316:22
*** dims has quit IRC16:24
*** belmoreira has quit IRC16:24
*** yamamoto has joined #openstack-meeting-316:26
*** rbrndt has joined #openstack-meeting-316:28
*** Aish has joined #openstack-meeting-316:28
*** ^Gal^ has quit IRC16:34
*** numans has quit IRC16:36
*** dedery has quit IRC16:37
*** Piet has joined #openstack-meeting-316:38
*** mchestr has joined #openstack-meeting-316:46
*** lazy_prince has quit IRC16:47
*** lazy_prince has joined #openstack-meeting-316:47
*** dheeraj has joined #openstack-meeting-316:52
*** jaypipes has joined #openstack-meeting-316:53
*** vgridnev has joined #openstack-meeting-316:53
*** irenab has quit IRC16:54
*** MattMan has joined #openstack-meeting-316:57
*** belmoreira has joined #openstack-meeting-316:59
*** stevemar_ has quit IRC16:59
alaski#startmeeting nova_cells17:01
openstackMeeting started Wed Nov 18 17:01:02 2015 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: nova_cells)"17:01
openstackThe meeting name has been set to 'nova_cells'17:01
*** igordcard has quit IRC17:01
*** e0ne has quit IRC17:01
alaskianyone around today?17:01
dansmithnot me17:01
dansmithoh wait17:01
dheerajo/17:01
melwitto/17:01
*** igordcard has joined #openstack-meeting-317:01
belmoreirao/17:01
alaski#topic Testing17:01
*** openstack changes topic to "Testing (Meeting topic: nova_cells)"17:01
alaskimelwitt: anything you're aware of in this area?17:02
dansmithI have an almost testing-related thing17:02
melwittno, but I haven't been looking at it lately (sorry)17:02
alaskimelwitt: no worries.  if trouble hasn't found you that's probably good17:03
alaskidansmith: go for it17:03
melwitt:)17:03
dansmithI've got the reno for the api database proposed, which is hung up on a string of deps in infra land17:03
dansmithand has been for a week17:03
dansmithbut after those are resolved,17:03
dansmiththe grenade patch to actually do that thing is passing and can be approved when the release note lands17:03
dansmithso, not testing, but almost testing :)17:03
alaskiheh17:04
belmoreiradansmith: great17:04
alaskithat's great17:04
dansmithno17:04
dansmithit's almost great :)17:04
belmoreirathat will allow us to recheck the flavor code17:04
dansmithbelmoreira: right17:04
dansmithwhich I need to go review and lay some hate on17:05
dansmithanyone have the link to that handy?17:05
* bauzas waves late17:05
dansmithI'll go do that after this meeting17:05
melwitthah17:05
alaskihttps://review.openstack.org/#/c/201606/17:05
alaskiwell, more the followup patch17:05
bauzasso I'll manually test the reno patch and +W17:05
alaskibauzas: cool17:06
bauzasI don't want to have it waiting for something which could come up later17:06
dansmithbauzas: I already depends-on'd it17:06
*** jlanoux has quit IRC17:06
bauzasdansmith: honestly, it could take yet a few days before having the infra patch merged17:06
bauzasdansmith: so it's your call17:07
*** matrohon has quit IRC17:07
alaskia few days seems fine17:07
bauzasdansmith: but like I said, I can act as a jenkins guy if needed17:07
dansmithwe might also just ask the grenade people to land it because the reno is in progress17:07
bauzascall me hudson17:07
dansmithanyway, not a big deal methinks17:07
alaskiyeah.  if it stretches to weeks that might be a problem17:08
dansmithsdague: thoughts?17:08
alaskibut if it's moving now it seems good17:08
dansmithsdague: we can't land the grenade patch before the reno for it, which is stuck in dep hell. Can we just land the grenade patch knowing we'll land the reno as soon as it can?17:08
dansmithsdague: or we can land the reno untested17:09
bauzaswell, tested locally17:09
bauzas'trust me'17:09
bauzas:D17:09
dansmithheh17:09
dansmithalaski: whatever, we can move on, I'll pursue17:09
alaskiok17:09
alaski#topic Specs for Mitaka17:09
*** openstack changes topic to "Specs for Mitaka (Meeting topic: nova_cells)"17:09
alaskidoes anyone have specs up that could use review?17:10
alaskiaccording to https://etherpad.openstack.org/p/mitaka-nova-spec-review-tracking everything should be merged at this point17:10
*** neelashah has joined #openstack-meeting-317:11
alaskiare there specs that we should have and don't?17:11
alaskigreat17:11
alaski#topic Open Reviews17:12
*** openstack changes topic to "Open Reviews (Meeting topic: nova_cells)"17:12
melwittI was thinking, what about that thing we talked about with the cell for error state instances? does that need to be a spec? (sorry it took me too long to type that)17:12
alaskimelwitt: https://review.openstack.org/#/c/238665/17:12
dansmithheh17:12
melwittoops. okay17:13
dansmithonly problem with that is the name17:13
dansmithbut otherwise I think we're good17:13
alaskiit happened quickly, before a lot of people even came back I think17:13
alaskidansmith: :)17:13
bauzasoh I missed that one, but we discussed that at summit :)17:13
melwittnice17:14
bauzasI like the name17:14
alaskicell0, all the flavor, none of the calories17:14
dansmithhah17:14
*** egallen has quit IRC17:14
melwitthaha, that's awesome17:14
bauzasthinking of cellU ?17:14
dansmithbauzas: stop it!17:14
dansmithdon't reward him17:14
alaskibauzas: I didn't make that association until later sadly17:14
belmoreiracell0 will conflict with our existing naming schema :)17:15
bauzaspurgatoryCell17:15
dansmithI don't think the name of it will be enforced17:15
bauzas(c) notme17:15
dansmithi.e. it probably doesn't need a name in the db17:15
alaskiyeah17:15
alaskiin v2 name doesn't really matter, they'll have uuids17:15
bauzasanyways, cellsv1 names shouldn't hit cellsv2 names17:16
bauzass/hit/conflict17:16
alaskiyep17:16
belmoreirayes17:16
alaskiso, open reviews :)17:16
alaskiI'll call out https://review.openstack.org/#/c/211753/ for persisting the request spec object17:17
alaskiif anyone else has anything please add it to https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking17:17
alaski#topic Open Discussion17:18
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"17:18
alaskiI only have one topic17:18
alaskiI propose that we skip this meeting next week17:18
alaskisince it's very close to a US holiday17:18
* bauzas promises to not speak of holidays17:19
bauzasalaski: fair enough17:19
alaskithough if there's a group of folks who will be around and want to have it go ahead17:19
*** mbound has quit IRC17:19
alaskiI should say major holiday.  there are a lot that don't affect much17:20
melwitt:) I'm good with skipping17:20
dansmithum, it's the majorest holiday17:20
*** fitoduarte has joined #openstack-meeting-317:20
alaskidansmith: debatable, but it's up there :)17:21
alaskianything else today?17:21
dansmithalaski: name one better holiday17:21
alaskiI'm quite fond of new years17:21
dansmithalaski: after 21 you stop getting tons of presents on christmas, so like a holiday dedicated to accelerating the adult diabetes is like ... pretty up there17:22
dansmithalaski: meh, boring17:22
*** flwang1 has joined #openstack-meeting-317:22
alaskino real obligations though17:22
dansmithalaski: new years is much less fun on the west coast where the ball drop is taped :)17:22
alaskiheh, fair point17:22
alaskialright, I think we're good for today17:23
alaskisame time in two weeks17:23
alaskithanks everyone!17:23
alaski#endmeeting17:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:23
openstackMeeting ended Wed Nov 18 17:23:20 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-11-18-17.01.html17:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-11-18-17.01.txt17:23
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-11-18-17.01.log.html17:23
*** nkrinner has quit IRC17:23
*** nkrinner has joined #openstack-meeting-317:24
*** belmoreira has quit IRC17:25
*** lazy_prince has quit IRC17:25
*** Sukhdev has quit IRC17:31
*** stevemar_ has joined #openstack-meeting-317:31
*** dheeraj has quit IRC17:35
*** Sukhdev has joined #openstack-meeting-317:36
*** kebray has joined #openstack-meeting-317:36
*** Aish has quit IRC17:36
*** banix has quit IRC17:37
*** mwagner has quit IRC17:38
*** sankarshan is now known as sankarshan_away17:38
*** wojdev has quit IRC17:40
*** davidmichaelkarr has quit IRC17:40
*** mestery has joined #openstack-meeting-317:40
*** armax has joined #openstack-meeting-317:41
*** wojdev has joined #openstack-meeting-317:42
*** cbouch has joined #openstack-meeting-317:42
*** Swami has quit IRC17:44
*** MattMan has left #openstack-meeting-317:44
*** vmahe_ has quit IRC17:45
*** kebray has quit IRC17:50
*** shaohe_feng1 has joined #openstack-meeting-317:52
*** wojdev has quit IRC17:52
*** lin_yang_ has quit IRC17:53
*** shaohe_feng1 has quit IRC17:54
*** shaohe_feng has quit IRC17:54
*** bharath has joined #openstack-meeting-317:56
*** sarob_ has joined #openstack-meeting-317:57
*** idan_hefetz has quit IRC17:58
*** neelashah1 has joined #openstack-meeting-317:59
*** Aish has joined #openstack-meeting-317:59
*** bharath has quit IRC18:01
*** neelashah has quit IRC18:01
*** Swami has joined #openstack-meeting-318:03
*** watanabe_isao has joined #openstack-meeting-318:03
*** belmoreira has joined #openstack-meeting-318:04
*** belmoreira has quit IRC18:05
*** mestery has quit IRC18:05
*** flwang1 has quit IRC18:06
*** neelashah1 has quit IRC18:07
*** sarob_ has quit IRC18:08
*** sdake has quit IRC18:08
*** davidmichaelkarr has joined #openstack-meeting-318:08
*** kebray has joined #openstack-meeting-318:11
*** bharath has joined #openstack-meeting-318:12
*** s3wong has joined #openstack-meeting-318:12
*** watanabe_isao has quit IRC18:13
*** sdake has joined #openstack-meeting-318:13
*** mestery has joined #openstack-meeting-318:15
*** e0ne has joined #openstack-meeting-318:15
*** davidsha has quit IRC18:16
*** banix has joined #openstack-meeting-318:18
*** Sukhdev has quit IRC18:19
*** jmckind has quit IRC18:19
*** Aish has quit IRC18:19
*** Aish has joined #openstack-meeting-318:20
*** wojdev has joined #openstack-meeting-318:21
*** mickeys has joined #openstack-meeting-318:22
*** madhu_ak has joined #openstack-meeting-318:22
*** sarob_ has joined #openstack-meeting-318:22
*** badveli has joined #openstack-meeting-318:23
*** wojdev has quit IRC18:24
*** ihrachys has quit IRC18:24
*** ogzy has joined #openstack-meeting-318:26
*** mwagner has joined #openstack-meeting-318:27
*** kebray has quit IRC18:27
*** vichoward_ has joined #openstack-meeting-318:27
*** sarob_ has quit IRC18:27
*** SridarK has joined #openstack-meeting-318:27
sc68calhello all18:28
SridarKHi All18:28
*** sdake has quit IRC18:28
mickeysHi18:28
ogzyhi all18:28
*** pcm_ has joined #openstack-meeting-318:29
sc68cal#startmeeting networking_fwaas18:29
openstackMeeting started Wed Nov 18 18:29:29 2015 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.18:29
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:29
*** openstack changes topic to " (Meeting topic: networking_fwaas)"18:29
openstackThe meeting name has been set to 'networking_fwaas'18:29
*** annp has joined #openstack-meeting-318:29
vishwanathjhi18:30
sc68calUnless there are any objections i'd like to dedicate the whole hour to just discussing the new api spec18:30
SridarK+118:30
mickeys+118:30
annpHi18:30
*** jpomeroy has quit IRC18:30
bharathHi18:30
xgermanhi18:30
*** jwarendt has joined #openstack-meeting-318:30
badvelihello all18:30
sc68cal#topic API spec review - https://review.openstack.org/24387318:31
*** openstack changes topic to "API spec review - https://review.openstack.org/243873 (Meeting topic: networking_fwaas)"18:31
jwarendthi18:31
madhu_akhi18:31
xgermanyeah, I like us to get that approved right after Thanksgiving18:31
xgermanaka M118:31
sc68calxgerman: ack. the latest revision has me hopeful18:32
xgermanme, too18:32
xgerman:-)18:32
SridarKyes i think we are fairly close too18:32
s3wonghello18:32
mickeysWhat do we intend for scope of the spec. Just defining the API? Or going into backend reference implementation as well?18:32
sc68calmickeys: just the API.18:32
xgerman+118:32
badvelii had some questions on the common backend which i will point out in spec18:33
sc68calbadveli: no do not talk about backends in the spec please18:33
xgermanwell, that doesn’t matter on the API18:33
SridarKso for the referennce implementation - we can create another one going off this as the master spec18:33
badvelibut i am not very clear on how we are going to incorporate18:33
badveliok thanks we will take it in another spec18:34
*** jaypipes has quit IRC18:34
xgermansc68cal we should alo talk midcycle18:34
xgermanafter the API discussion18:34
sc68calxgerman: good point, 15 minutes enough?18:35
xgermanyep18:35
xgermanlikely less18:35
xgermanso back to API18:35
*** neelashah has joined #openstack-meeting-318:35
* sc68cal opens up gertty18:36
badvelii am thankful for incorporating the service group and firewall group's18:37
*** pavel_bondar_ has quit IRC18:37
*** MarkAtwood has joined #openstack-meeting-318:37
xgermanhow is tuff called? accept, reject, deny — or drop?18:37
sc68calthe issue is there does not seem to be a way to actually add ports to a policy18:37
sc68calerr18:37
SridarKI am in the midst of the latest rev - one thought is that given that we are taking the reference impl out of this discussion - what we are going after is the final form ?18:37
sc68calfirewall gropu18:37
sc68cal*group18:38
xgermanSridarK we should be able to start implementing a stubbed API server18:38
badveliyes looked to me it is a consturct to group address18:38
xgermanor extension18:38
mickeysThrough firewall group port association. Everything is CRU.18:38
badvelifirewall groups to be a construct to group address18:38
sc68calmickeys: right - but how is a association created via the API?18:38
xgermanthose class are missing18:39
mickeysWhen I wrote things up in the etherpad, I was thinking of all the tables as API18:39
mickeysI was not thinking that some are data model and others are API18:39
xgermanwell, we need to spec out the calls like we did for the rest18:39
mickeysAish: xgerman: What was the thought behind calling some data model?18:39
xgermanyeah, we probably need to specify our tables somewhere18:40
SridarKi think so too adding the CRU on an attribute should cover that18:40
sc68calMy suggestion - perhaps add an attribute to the firewall group REST API resource - ports?18:40
mickeysI think of the Firewall group attributes table and firewall group port association tables as the JSON body of REST APIs18:41
xgermanmickeys, part of the spec are some example calls so we should do the same for the new constrcuts18:42
xgermanand base it on those tables18:42
xgermanotherwise we are inconsistent18:42
mickeysAgreed. We need to define endpoints/URIs and give examples18:42
*** kebray has joined #openstack-meeting-318:42
sc68calwe're worse than inconsistent - we leave it undefined.18:42
SridarKsc68cal: i think u are asking for something along the lines for policies etc that are shown18:43
sc68calSridarK: right - that will help, but we also need to show how someone would associate a port to a firewall group18:43
sc68calvia the REST API18:43
SridarKsc68cal: ok i get it makes it more clear for sure18:44
*** zz_dimtruck is now known as dimtruck18:44
sc68caldon't forget - this API spec will be around for a loooooong time, people will be using it to figure out how to implement18:45
badveliyes looked from the firewall groups it looked like more address groups but not sure how they are applied ports18:46
mickeysFirewall groups are primarily a collection of ports. Firewall group port association table is how you apply to ports.18:46
*** obondarev has quit IRC18:46
mickeysWhether addresses should be in firewall groups in addition to ports, or have a separate address group is an open issue. Right now there is a separate address group. We need to decide this soon, preferrably now.18:47
*** cloudtrainme has quit IRC18:47
SridarKmickeys: my sense is that it would be simpler to keep them separate and the validation around this will be simpler18:48
sc68calmickeys: firewall group port association table is how we *store*18:48
badvelithanks mickey i am trying to understand how is the firewall group port association table populated18:49
sc68calmickeys: it does not specify how a user actually sends an API request to get it to store18:49
sc68caland how it's formatted/structured/expressed18:49
xgermanyep, that’s the gap we need to close with the next respin18:50
*** mchestr has quit IRC18:51
mickeysOriginal preference was extension to port table, so that it could be defined when a port is created, but that was seen as potentially controversial. So we talked about specifying it in FWaaS tables. The question is whether there is a list of ports in the firewall group table, or a separate URI just for the firewall group port association18:51
sc68calmickeys: you're still thinking database tables though18:51
*** mchestr has joined #openstack-meeting-318:51
mickeysFirewall group must be its own endpoint/URI, with the attributes specified in the table18:52
sc68calas a consumer of this API, what URI, what kind of JSON do I send to get Port AAAAA associated with firewall group BBBBB ?18:52
mickeysAgreed that we need to specify this.18:52
sc68calI'm in agreement with the database model side, we're good there.18:53
mickeysAish: xgerman: You added the firewall group port table. Are you thinking separate URI?18:53
xgermannope, I think we mixed data model and REST calls18:53
jwarendtUsually there is an encoded URI association ../firewall/<id>/ports/... at the REST level, or separate resources with URI/ID links.  Need REST api first - db is implementation.18:54
sc68caljwarendt: +118:54
*** salv-orl_ has joined #openstack-meeting-318:54
*** salv-orl_ has quit IRC18:54
mickeysSo add a list of ports as an attribute to the firewall group URI when we add that?18:54
jwarendtThough ultimately need: 1) plugin interface 2) driver interface 3) db layer to go along with REST.18:54
sc68calmickeys: that sounds reasonable to me18:55
xgerman2) I think we have more than one driver interface for different aspects18:55
xgermansc68cal +!18:55
xgerman+118:55
*** mbound has joined #openstack-meeting-318:56
xgermanyeah, one of the aims of the new API is to not make it more difficult for the user. So he does;t have to create 10 things to get a firewall...18:56
*** kebray has quit IRC18:56
*** bpokorny has quit IRC18:56
*** mchestr has quit IRC18:56
*** mchestr has joined #openstack-meeting-318:56
*** bpokorny has joined #openstack-meeting-318:57
sc68calwe're very close - I can feel it18:57
xgerman+118:57
*** salv-orlando has quit IRC18:57
mickeysDo we want to mention the port extension as well, and note that it may come later? The rationale for the port extension is that the person creating the port can adjust associated firewall groups as they are creating the port. I doubt an application deployer is going to mess with FWaaS.18:57
*** neelashah has quit IRC18:58
sc68calI'd rather not18:58
mickeysThere was some concern about the difficulty in adding things to the port table18:58
xgermanwell, as soon as you do something for all of Neutron velocity dies18:58
SridarKso the fw group is the binding point of the policy and where it is applied - from a db perspective the association to ports can be a separate table18:58
*** jpomeroy has joined #openstack-meeting-318:58
xgermanyep, and that keeps us adding things to the port table of the critical path18:59
SridarKagree on the port extension - let that come later18:59
*** ogzy has quit IRC18:59
*** obondarev has joined #openstack-meeting-319:00
s3wongmickeys: wouldn't the sequence of event being user creating port, and associate the port with a FW group? Why would a FW group already been associated with a port being created?19:00
*** doug-fis_ has joined #openstack-meeting-319:00
*** jmckind has joined #openstack-meeting-319:00
SridarKs3wong: the vm port case19:00
sc68cal^ this19:01
*** kebray has joined #openstack-meeting-319:01
xgermans3wong we like the concept of a default firewall19:01
sc68calassociate a new vm port to an existing policy19:01
mickeyss3wong: That is the issue. By the time there is a VM port for us to associate / put in the list in the firewall group, the VM port is already active19:01
sc68cals/policy/firewall group/19:01
mickeysSo, the default firewall group would apply temporarily19:01
xgermanand then the user can change it to his likings19:01
xgermanin the future you might be able to specify a firewall group on nova create19:02
SridarKxgerman: thats vision :-)19:02
xgermanyep, I should have said far future19:02
SridarK:-)19:02
s3wongxgerman: not a bad vision19:03
sc68calDo we have a good description of what service_group attribute of a firewall rule is?19:03
SridarK+119:03
mickeysAs far as document structure, I think the firewall group attributes should be moved to the API section, with the addition of a port list. We then need to figure out where to put the data model section, including the firewall group port association table19:03
*** doug-fi__ has joined #openstack-meeting-319:03
*** kebray has quit IRC19:04
*** doug-fish has quit IRC19:04
xgermanagreed, I think their is a data model impact in the spec teamplate19:04
*** doug-fi__ has quit IRC19:04
badvelisc68cal: the service group UUID can be referred by firewall, we had it in the service group spec19:04
*** Guest12059 is now known as med_19:04
mickeyssc68cal: For service group, the question is how we can reference it as an important part of the API, but specify it outside in a separate spec19:04
*** med_ has quit IRC19:04
*** med_ has joined #openstack-meeting-319:04
*** doug-fish has joined #openstack-meeting-319:04
*** doug-fish has quit IRC19:04
*** doug-fis_ has quit IRC19:05
sc68calmickeys: badveli: ok - but what does it *do* ?19:05
mickeysIs it OK to leave it in the attributes table and refer to another spec?19:05
*** doug-fish has joined #openstack-meeting-319:05
*** ivar-lazzaro has joined #openstack-meeting-319:05
badvelimickeys: i think that is fine19:05
xgermanI think this is what we have to do19:05
SridarKmickeys: yes i think we can point to badveli's spec19:06
badveliwe can reference it19:06
mickeysA group of objects, each with protocol, source L4 port range, dest L4 port range. In the future, L7 objects such as application ID.19:06
SridarKand leave it as something that is being explored for the future19:06
xgerman(and might become some classifier)\19:06
*** jckasper has quit IRC19:06
*** ivar-lazzaro has quit IRC19:06
*** doug-fish has quit IRC19:06
badvelisc68cal: the service group spec clearly mentions the functionality i did not add L7 objects as of now19:07
mickeysThe thought is, for a particular application, there will be certain protocol/L4port combinations that you will want enabled. Once someone specifies the service group for that application, you can reuse that over and over again, wherever that application is deployed.19:07
*** doug-fish has joined #openstack-meeting-319:07
sc68calso basically a classifier19:07
mickeysExchange, SAP, etc19:07
sc68calor multiple classifiers19:07
mickeysNot a full classifier. Nothing to do with addresses or identity.19:07
sc68calclassifier doesn't have to require addresses19:08
s3wonglist of application classifiers19:08
xgermanyeah, so I think keeping that out of the API spec gives us some flexibility later19:08
mickeysSay if I want to use exchange or SAP or FTP ...19:08
sc68caland I'd like to remove the attribute from the API for now19:08
sc68calwe can add it back in once we have something more concrete19:08
xgermanmmh, we have the service group so it shouldn’t matter if they are done with classifiers or not19:09
xgermanmatter to the API19:09
sc68calwe're already making a big hunk of work by having address groups19:09
badvelisc68cal: should we have it there , i am pretty sure this will decouple the notion of service from the firewall19:09
sc68calas well as firewall gruops19:10
*** mbound has quit IRC19:10
*** ivar-lazzaro has joined #openstack-meeting-319:10
sc68calSridarK: what are your thoughts19:11
SridarKsc68cal: yes i have some concerns on actually what we will implement - but if we keep this spec as the end goal and we call out implementation for M outside of this19:11
SridarKsc68cal: u read my mind19:11
SridarKsorry straddling mtgs19:11
xgermanyeah, I think we should spec out what we want and then figure out the implementation strategy later19:12
sc68calOk. let me noodle on it a bit more - I think if we make it more clear what it will do - API interaction wise, i'll be more happy with leaving it in19:12
*** mbound has joined #openstack-meeting-319:12
sc68caland let me re-read badveli 's spec - the link to it might satisfy me19:12
badvelisc68cal: let me know if you have questions19:13
badvelithanks19:13
mickeysI am unclear where are ending up. Leave service group as is, but clarify the reference? Define it completely in the spec? Take it out?19:13
*** bharath- has joined #openstack-meeting-319:13
sc68calmickeys: leave it in, and give me a link over to badveli's spec in the notes19:13
badveli+119:13
xgermanunderstood19:13
mickeysReference the Kilo version?19:13
mickeysbadveli: Any plans to resubmit for Mitaka?19:13
*** bharath has quit IRC19:13
badveliyes i am doing it19:14
sc68calI think this will work - if this is the most up to date - http://specs.openstack.org/openstack/neutron-specs/specs/juno/service-group19:14
xgermanyeah, specs usually just roll forward...19:14
mickeysThere is a kilo spec19:14
badvelihttps://review.openstack.org/#/c/13159619:14
SridarKi think we can use the kilo spec19:14
SridarKbadveli: u will need to clean this up and resubmit ?19:14
sc68calok then use http://specs.openstack.org/openstack/neutron-specs/specs/kilo/service-group.html19:15
*** bharath- is now known as bhag19:15
xgermanyep19:15
badveliyes, should we add the notion of L719:15
mickeys+119:15
mickeysNot yet19:15
*** MarkAtwo_ has joined #openstack-meeting-319:15
*** MarkAtwood has quit IRC19:16
badveliwill it be ok to resubmitt before our API spec gets approved?19:16
sc68callet's use a HTTP link to the rendered HTML - if your spec gets approved for mitaka we can always update the link19:16
sc68calto point to the new URL19:17
sc68calfrom the firewall side there isn't any difference - since we're just storing a UUID19:17
xgerman+@19:17
xgerman+119:17
*** absubram has joined #openstack-meeting-319:18
mickeys+119:18
badveliok thanks.19:18
SridarKyes it is a resource we refer to19:18
sc68calok, we've got about 10 minutes left - xgerman - midcycle?19:18
SridarKso +119:18
xgerman#topic midcycle19:18
sc68calsorry I didn't add you as chair19:18
sc68cal#topic midcycle19:18
*** openstack changes topic to "midcycle (Meeting topic: networking_fwaas)"19:18
xgerman#link https://etherpad.openstack.org/p/lbaas-mitaka-midcycle19:18
xgermanso dougwig likes to colocate with LBaaS19:18
xgermanthey picked 1/13-1/16 as potential dates19:19
xgermanwould they work for you guys?19:19
* sc68cal checks 19:19
s3wong1/16 is a Saturday?19:19
xgermanreally?19:19
s3wongyep19:20
*** neelashah has joined #openstack-meeting-319:20
sc68calso 1/12 to 1/15?19:20
xgermanwould be fine by me19:20
sc68calworks for me too19:21
*** cloudtrainme has joined #openstack-meeting-319:21
jwarendtworks19:21
xgermanawesome19:21
mickeysNo conflicts for me19:21
sc68calis the Idaho option - dougwig 's house?19:21
xgermanmight be some hunting cottage19:21
mickeysIdaho in January? That wouldn't be Sun Valley, would it? :-)19:21
*** bklei has quit IRC19:22
sc68calwhat's seattle like in jan?19:22
SridarKBrr!!19:22
*** jckasper has joined #openstack-meeting-319:22
xgermannope, I think Seattle and San Antonio are more realistic  options19:22
SridarK+119:22
*** doug-fish has quit IRC19:22
*** bklei has joined #openstack-meeting-319:22
sc68callol "somewhere new" crossed out19:22
s3wonglike any other months, raining :-)19:22
*** doug-fish has joined #openstack-meeting-319:23
*** bapalm has quit IRC19:23
sc68calI think whichever is easiest to organize and host19:23
*** bklei_ has joined #openstack-meeting-319:24
sc68calsan antonio weather probably is better than SEA, but i'm not picky19:24
xgermanyeah, big concern from Doug is that we go to Seattle each time but...19:24
* sc68cal sneaks over to mountains to snowboard after midcycle19:24
SridarKi always welcome u too the bay area19:24
jwarendtxgerman cannot fit  us all in San Diego unfortunately if chasing good weather.19:25
s3wongsunny California!19:25
xgermanI can probably work something out but there are also budgetary constraints19:25
*** bapalm has joined #openstack-meeting-319:26
vishwanathjWhich company will host in San Antonio, will that be rackspace?19:26
xgermanyep19:26
xgermanthere is a lot of travel budget thinling behind locations19:26
*** bklei has quit IRC19:27
xgermanok, I guess we are good19:28
xgermanplease vote on location19:28
xgermanand I think we are done for today ;-)19:29
vishwanathjbye all19:29
sc68calyup19:29
sc68calbye all19:29
*** pcm_ has left #openstack-meeting-319:29
SridarKbye all19:29
vichoward_o/19:29
mickeysbye19:29
sc68cal#endmeeting19:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:29
xgermano/19:29
jwarendtbye19:29
openstackMeeting ended Wed Nov 18 19:29:31 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:29
badvelibye19:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-11-18-18.29.html19:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-11-18-18.29.txt19:29
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-11-18-18.29.log.html19:29
*** vishwanathj has quit IRC19:29
*** jwarendt has quit IRC19:30
*** vichoward_ has quit IRC19:35
*** neelashah has quit IRC19:36
*** jckasper has quit IRC19:37
*** Sukhdev has joined #openstack-meeting-319:38
*** bklei_ has quit IRC19:38
*** bklei has joined #openstack-meeting-319:39
*** TravT has joined #openstack-meeting-319:39
*** fitoduarte has quit IRC19:44
*** fitoduarte has joined #openstack-meeting-319:44
*** vkmc is now known as vkmc-afk19:44
*** ddieterly has quit IRC19:45
*** MarkAtwo_ is now known as MarkAtwood19:45
*** neelashah has joined #openstack-meeting-319:46
*** Sukhdev has quit IRC19:49
*** jckasper has joined #openstack-meeting-319:50
*** flwang1 has joined #openstack-meeting-319:53
*** jed56 has quit IRC19:54
*** MarkAtwood has quit IRC19:54
*** matt-borland has joined #openstack-meeting-319:56
*** ying_zuo has joined #openstack-meeting-319:57
*** robcresswell has joined #openstack-meeting-319:58
matt-borlandhola robcresswell19:58
*** r1chardj0n3s has joined #openstack-meeting-319:58
robcresswello/19:58
matt-borlando/19:58
*** wojdev has joined #openstack-meeting-319:59
*** hurgleburgler has joined #openstack-meeting-320:00
*** ducttape_ has joined #openstack-meeting-320:00
david-lyle#startmeeting Horizon20:00
openstackMeeting started Wed Nov 18 20:00:52 2015 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
hurgleburgler(◠‿◠✿)ノ20:00
*** openstack changes topic to " (Meeting topic: Horizon)"20:00
openstackThe meeting name has been set to 'horizon'20:00
TravTo/20:01
*** esp_ has joined #openstack-meeting-320:01
*** pauloewerton has joined #openstack-meeting-320:01
*** Rockyg has joined #openstack-meeting-320:01
mrunge\o/20:02
krotscheck\/20:02
esp_o/20:02
*** wojdev has quit IRC20:03
david-lyleHi all20:03
doug-fishhi20:03
peristerio/20:03
ying_zuoo/20:04
david-lyleThe only general items I have today is a reminder that M-1 is Dec 320:04
r1chardj0n3s(also, lurker here, I'd like to push a little on getting midcycle nailed down ;-)20:04
matt-borlandr1chardj0n3s +120:04
david-lyletalked to possible hosts, need to pin down dates20:05
*** igordcard has quit IRC20:05
mrungeyeah, good to know it in advance20:05
*** Sukhdev has joined #openstack-meeting-320:05
*** subscope has quit IRC20:06
hurgleburglerwhere are the possibilities?20:06
david-lylemostly west coast so far20:06
*** subscope has joined #openstack-meeting-320:06
david-lyleTexas and Colorado are also options, but twice to texas in 6 months is way too much20:06
hurgleburglerdavid-lyle +120:07
*** sqchen has joined #openstack-meeting-320:07
david-lyleonce is a bit much20:07
* krotscheck likes seattle :)20:07
hurgleburgleryou are all welcome to come to Tucson20:07
hurgleburglerIt'll be warmer here :-D20:07
krotscheckThere could be snow on the volcano :)20:07
david-lylehurgleburgler's living room it is20:08
hurgleburgler\o/20:08
david-lyleLet me negotiate dates20:08
david-lyleand narrow it down20:08
david-lyleSeattle, Portland and San Jose are three easy locations on the west coast with offers to host20:09
*** subscope has quit IRC20:09
hurgleburglerSan Diego will be warmer :-D20:09
hurgleburglerand they have super impressive amounts of craft beer20:09
TravTi'll email san diego20:09
TravTanybody have their address?20:09
robcresswellbeer?20:09
*** subscope has joined #openstack-meeting-320:10
krotscheckI think at this point, impressive amounts of craft beer is not a distinguishing feature anymore.20:10
* krotscheck points at both portland and seattle.20:10
TravTmaybe we could just reach out to these folks20:10
TravThttp://www.meetup.com/OpenStack-SD/20:10
hurgleburglersan diego won't have snow though20:10
*** MarkAtwood has joined #openstack-meeting-320:11
*** salv-orlando has joined #openstack-meeting-320:11
krotscheckSnow, to me, is a bennefit.20:11
*** egallen has joined #openstack-meeting-320:11
david-lyleski holiday in sunny colorado?20:11
krotscheckHorizon-team ski outing :)20:11
mrunge2 hops to fly, about 22 hours in total :-/20:11
doug-fishI can probably host in MN if we really need snow ...20:12
*** jtomasek has quit IRC20:12
hurgleburgler*shivers*20:12
TravTif we want snow, then i vote Colorado20:12
hurgleburglersnow: -120:12
mrungewe could ask tsufiev, if you want snow and cold temperatures20:12
krotscheckSure, let's do russia!20:12
krotscheckOn an unrelated note, I'm slowly trying to upgrade the eslint rules to the newer version of eslint-config-openstack, and wouldn't mind some help.20:13
r1chardj0n3sI would also like to add a preference for date: week of 18th Jan please :-)20:13
*** e0ne has quit IRC20:13
david-lylelet's table the midcycle for a bit20:14
*** neelashah has quit IRC20:14
david-lyleand get a brief status on https://etherpad.openstack.org/p/mitaka-horizon-priorities20:14
*** neelashah has joined #openstack-meeting-320:14
david-lyledocumentation patches are in progress20:15
jasondotstaro/20:15
david-lylethe extensibility service merged20:15
david-lyleTheming is one for two20:16
david-lylethe doc patch for theming isn't on the etherpad20:17
david-lylehurgleburgler: status?20:17
*** subscope has quit IRC20:17
david-lylepbr is still being spec'd20:17
r1chardj0n3sxstatic/pbr is still is indeed still in spec hell, but I think we're making progress20:18
david-lyleand nothing is linked for "Angular performance tuning"20:18
david-lyleanyone with work on that please link it20:18
sqchenjust crealte BP20:18
*** MarkAtwood has quit IRC20:18
sqchenin progress20:18
TravTnothing is up for upgrading angular or other libs right?20:19
TravTi thought that was discussed20:19
david-lyleI would appreciate folks linking their patches and bps to the ehterpad20:19
sqchendavid-lyle: ok20:19
TravTwe don't want those to come in at end of cycle20:19
*** neiljerram has quit IRC20:19
david-lyleTravT: that was blocked by pbr20:19
robcresswellTravT: Releasing things is not easy without pbr20:19
*** qwebirc90523 has joined #openstack-meeting-320:20
TravTright...20:20
hurgleburgleryeah, i wanna update bootstrap, but blocked by pbr :(20:20
mrunger1chardj0n3s, would it be an option to drop the release as fourth component? or to use as last comporent version.release?20:20
matt-borlanddavid-lyle, just FYI on the Angular side alone (Users/Images/Launch Instance), I count ~30 outstanding patches, but I don't want to clutter up the etherpad20:21
matt-borland(does not count Flavors or other deprioritized work)20:21
david-lylematt-borland: I'd rather see them on there for priority items or at very lest the link to the bp20:21
matt-borlandsounds good20:21
matt-borlandwill do20:21
*** yamahata has quit IRC20:21
r1chardj0n3smrunge: I think we can get there, with 4 digits20:21
mrungeok, I was just reading apevec comment on https://blueprints.launchpad.net/pbr/+spec/pbr-fourth-component20:22
*** iyamahat has quit IRC20:22
mrungebut, that is still 3 dots in the version number20:22
mrungeso, forget that please20:22
hurgleburglergotta leave early today o/20:23
*** hurgleburgler has left #openstack-meeting-320:23
david-lylethat covers the criticals and would appreciate updates to the etherpad so we can track better, since launchpad is launchpad20:23
matt-borlandI'll update the angular work20:24
david-lylethanks20:24
david-lylethe agenda for today is available at20:24
david-lyle#link https://wiki.openstack.org/wiki/Meetings/Horizon#Agenda_for_November_1820:24
david-lyle#topic reno for release notes20:24
*** openstack changes topic to "reno for release notes (Meeting topic: Horizon)"20:24
david-lyleThe two patches lhcheng linked are now merged20:25
david-lylebut the idea was to raise awareness20:25
david-lylerelease notes are now included in the tree when warranted, then the compilation becomes the final release notes at the end20:26
david-lylethe process documentation for horizon was documented in https://review.openstack.org/#/c/246124/20:26
*** egallen has quit IRC20:26
david-lylethe idea is if it's release note worth as outlined in the doc content there, the release note component should be merged at the same time or in a follow on patch20:27
david-lyleso reviewers help remind/enforce this20:27
david-lylethe process is new for mitaka, so try to remember20:28
david-lylequestions?20:28
*** evgenyf has joined #openstack-meeting-320:28
david-lyleperfect20:29
david-lyle#topic Domain scoped tokens DOA patches bpokorny, esp20:29
*** openstack changes topic to "Domain scoped tokens DOA patches bpokorny, esp (Meeting topic: Horizon)"20:29
mrungeshould we consider missing release notes as blocker?20:29
mrungesorry, too slow to type20:29
*** neelashah has quit IRC20:29
david-lylemrunge: I think yes20:29
mrungeack david-lyle20:29
david-lylecan be a dependent patch, but should be in progress20:30
david-lyleI think writing the migration part will also inform some patch work :)20:30
r1chardj0n3sI'd also like to plug the phantomjs/webdriver patches for review please20:30
*** neelashah has joined #openstack-meeting-320:30
david-lyleok esp_, do you want to type?20:30
esp_sure20:31
david-lyleack r1chardj0n3s20:31
r1chardj0n3shttps://review.openstack.org/#/c/242926/ and https://review.openstack.org/#/c/243946/20:31
esp_brad is absent today but we’d like to make a bid for merging these DOA patches20:31
esp_https://review.openstack.org/#/c/141153/20:31
esp_https://review.openstack.org/#/c/196328/20:31
bpokornyI just got back also, just in time :)20:31
esp_^ allows for keystone v3 integration in horizon by support a domain scoped token in the session20:32
esp_cool bpokorny20:32
david-lyleso, I'm on the fence and as one of the authors that's an odd place to be20:33
david-lyleI think the code is sane20:33
esp_aye, I believe doug-fish and lin have reviewed pretty well and gave their blessing20:34
david-lylethe last lingering concern that was raised at the summit and I'm coming around to appreciating better is the log noise20:34
robcresswellIt has 2 +2s? Was there too much uncertainty?20:34
esp_yeah, talked to lin about the extra logging this morning20:34
david-lylethe will conceivably be many failures in the horizon and keystone logs20:34
doug-fishrobcresswell: it wasn't merged because it really isn't useful without the follow on policy patch; I'd expect them to get merged together20:35
robcresswelldoug-fish: Understood20:35
david-lyle*there20:35
mrungeyeah, we might want to change default settings for sessions then20:35
*** mickeys has quit IRC20:35
mrungesince this will cause a session overflow otherwise20:36
david-lylethere's that too20:36
doug-fishmrunge: there is a check for that in the code IIRC20:36
* ducttape_ can't believe we are still talking about session overflow20:36
bpokornyYeah, there's a check for the session backend being used.20:36
mrungedoug-fish, that's not enough20:36
mrungeducttape_, that's reality20:36
*** egallen has joined #openstack-meeting-320:37
david-lyleducttape_: signed cookies is a much simpler and HA ready session backend20:37
mrungebut we're still talking about utf-820:37
david-lyleas a default it makes sense20:37
esp_david-lyle: if we can, I’d like to tackle that as a bug to keystone to reduce logging or at least include better info regarding when a user doesn’t have a domain associated with it20:37
ducttape_what if we added a cache call for the catalog, and didn't store that in session?  I thought that was like 75% of the cookie20:38
esp_mrunge and ducttape_: we know there is still on going work to combine the domain token with the project token and are prepared to refactor when it’s ready.20:38
doug-fishmrunge: I'm not sure I fully understand your concern about the default session backend. You think it's unreasonable to say some options require other, non default options?20:39
mrungedoug-fish, I was just suggesting to change the default anyways20:39
doug-fishgot it20:39
*** JeanBriceCombebi has joined #openstack-meeting-320:39
mrungesince that's, what deployers will need to do20:40
mrungeand this is *one* reason.20:40
david-lyleesp_: I'd really like to see proper v3 support merge20:40
mrungeyes!20:40
*** neelashah has quit IRC20:40
ducttape_so thats the two patches above, right?20:40
* david-lyle will resurrect his devstack patch for memcache20:40
*** neelashah has joined #openstack-meeting-320:40
david-lyleducttape_: that's the start20:40
david-lylethere's a mess in horizon beyond that20:41
*** egallen has quit IRC20:41
david-lylethe reuse of the admin role by keystone in the sample file is pure lunacy, but we need to handle it20:41
david-lyle*sample policy file20:41
ducttape_so proper v3 support really means better policy file usage, right?20:42
esp_david-lyle: agreed, it’s a first step but I think there is enough there to be useful.  bpokorny and others are already using it.20:42
david-lyleand different tokens have to be used for different resources20:42
ducttape_whoah, you need different tokens for different policy checks ?20:42
*** oetrog has joined #openstack-meeting-320:42
ducttape_that's not optimal20:42
david-lyleducttape_: yes and proper use of the domain scoped token when warranted over the project scoped token20:42
david-lyleit's idiotic, but it's v320:42
ducttape_so can we just place both v2 and v3 tokens to the policy engine, and have the policy file pick and choose which to use?20:43
*** oetrog has quit IRC20:44
esp_ducttape_: I don’t think we want to run v2 and v3 concurrently20:44
david-lylewell we'd have a project scoped token and a domain scoped token instead of v2 v3 but yeah20:44
david-lylethat's what the second patch to d-o-a does20:44
esp_aye20:44
ducttape_if you hard code to pass one token vs the other for a particular check, that is going to come back and bite us20:44
ducttape_my bad.... I mean project scoped vs domain scoped20:44
david-lylewell only keystone wants a domain scoped token20:45
*** iyamahat has joined #openstack-meeting-320:45
david-lyleso the toggle is simpler, except you have to know whether you're asking at the domain or project level20:45
esp_right, it’s only used for identity mgmt (talking to the keystone api) https://review.openstack.org/#/c/196328/20:45
esp_ducttape_: ^20:45
david-lyleI have days worth of rants that esp_ has heard about the brilliance here20:45
esp_def :)20:46
david-lylebut I'll refrain for now20:46
david-lylethere was no earthly reason for a second token type20:46
ducttape_that is going to be a problem for deployment20:47
david-lyleand that's actually in discussion to correct20:47
david-lyle3 years later20:47
ducttape_you are going to want to write policy files that would have both credentials and domain_credentials support at the same time20:47
david-lyleducttape_: maybe20:48
david-lyledepends how much you're wanting to expose to a domain admin20:48
david-lyleoutside of keystone20:48
david-lylebut yeah, it's a mess IMO20:48
ducttape_lets dig back out of the rathole we are in.   esp_ and brad have a couple of patches, lets get those merged I guess20:48
david-lylethe other options aren't pretty either and this code has been thoroughly tested20:49
* ducttape_ hopes we are done with the airing of grievances 20:49
* david-lyle puts away the pole20:49
esp_thx, I owe some more docs upstream as well20:49
mrungeand release notes20:50
david-lylehmm20:50
* david-lyle wonders about d-o-a release notes20:50
robcresswellDoes d_o_a do its release notes in Horizon?20:50
ducttape_yep, please include docs with patches.  docs are not difficult.  yes robcresswell, most of the time20:50
david-lylerobcresswell: I usual put important items in the release proposal20:50
robcresswellducttape_: I realise we have done previously, I meant with reno20:51
mrungedidn't we want to merge d-o-a in horizon?20:51
david-lyled-o-a is easier to track20:51
* esp_ will need to spend some time looking at reno20:51
david-lyleI think the clients may use reno20:51
david-lylemight need to add to d-oa-20:51
david-lylerearrange chars as necessary20:52
*** neelashah has quit IRC20:52
david-lyleok, doc it20:52
david-lylemerge it20:52
david-lyle#topic Open Discussion20:52
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"20:52
robcresswellYeah, we'll need to set up reno in doa then20:52
* krotscheck points at eslint patches.20:52
* krotscheck goes back to lurking20:52
david-lylehey look eslint patches20:52
krotscheckActually, I lied.20:52
krotscheckThere's a new rule under discussion here: https://review.openstack.org/#/c/244257/20:53
r1chardj0n3sjust back to the midcycle - snow is lovely and all but let's please not hold it in a location where travel could be affected by adverse weather20:53
robcresswellhttps://review.openstack.org/#/c/244910/ << thats the top of the chain, I think, for eslint.20:53
ducttape_r1chardj0n3s +1.   south pacific island would be lovely20:54
krotscheckrobcresswell is correct.20:54
david-lylekrotscheck: so there was a patch to add space after ";" but then you end up with "blah = {var b = 'super'; }" which felt odd20:54
* krotscheck volunteers Honolulu20:54
*** shwetaap has joined #openstack-meeting-320:54
krotscheckdavid-lyle: Yeah, I saw that too and was trying to figure out if they fix it in a future version of the rule.20:54
* krotscheck promptly got distracted.20:54
*** Sukhdev has quit IRC20:55
krotscheckdavid-lyle: Feel free to -1 that one for more investigation. I may be able to update eslint upstream to get it fixed.20:55
david-lylekrotscheck: no worries, I was just hoping there was another rule coming along to rationalize that20:55
robcresswellI updated this, btw: https://wiki.openstack.org/wiki/Horizon/WeeklyBugReport If anyone wants some bugs to look at :)20:55
* r1chardj0n3s notes that accountants don't like approving midcycles in pacific islands ;-)20:55
*** dimtruck is now known as zz_dimtruck20:55
r1chardj0n3sthanks again for that robcresswell!20:55
robcresswelldavid-lyle: We also need to discuss bug day20:56
david-lylerobcresswell: ah, was missing on the agenda20:56
robcresswelldavid-lyle: Yes, my fault :(20:56
david-lylebug report that is20:56
david-lyleyes, so my latest look at the bug list show ~1000 bugs20:56
david-lylewhich is just wow20:56
david-lylesome are 2+ years old20:56
david-lylewhile age is not an indication of validity, some may not exist20:57
david-lyleand actually about 600 of those are not even prioritized20:57
david-lylewhat I would like to do is let robcresswell organize a bug day to try to clean up that list20:57
doug-fishhooray robcresswell!20:58
robcresswell...trapped again20:58
david-lylethe concept would be to take a day to have people focus on triaging/classifying bugs and cross-talk when there are questions20:58
*** shwetaap has quit IRC20:58
david-lylejust take different parts of the list and have at it20:59
*** evgenyf has quit IRC20:59
robcresswellOriginally thinking next week, but apparently thanksgiving20:59
*** zz_dimtruck is now known as dimtruck20:59
david-lyleI've been told we've discussed this previously and not followed through20:59
david-lylehence robcresswell is taking the helm21:00
robcresswellI *will* find those logs21:00
david-lyleand I can rue about v321:00
robcresswellI'll send out an email on the dev mailer tomorrow21:00
david-lylethanks!21:01
r1chardj0n3syay bug day21:01
david-lyleok time's up. Thanks everyone, have a lovely week.21:01
david-lyle#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Wed Nov 18 21:01:23 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-11-18-20.00.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-11-18-20.00.txt21:01
*** r1chardj0n3s has left #openstack-meeting-321:01
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-11-18-20.00.log.html21:01
*** ducttape_ has left #openstack-meeting-321:01
*** robcresswell has left #openstack-meeting-321:01
*** TravT has left #openstack-meeting-321:01
*** matt-borland has left #openstack-meeting-321:02
*** openstack has joined #openstack-meeting-321:03
*** ChanServ sets mode: +o openstack21:03
esp_thx!21:03
*** esp_ has left #openstack-meeting-321:03
*** mbound has quit IRC21:04
*** mbound has joined #openstack-meeting-321:06
*** Aish has quit IRC21:07
*** sqchen has quit IRC21:07
*** sdake has joined #openstack-meeting-321:08
*** e0ne has joined #openstack-meeting-321:09
*** dconde has quit IRC21:09
*** mbound has quit IRC21:11
*** kebray has joined #openstack-meeting-321:20
*** sjmc7 has joined #openstack-meeting-321:21
*** kebray has quit IRC21:22
*** JeanBriceCombebi has quit IRC21:23
*** peristeri has quit IRC21:25
*** kebray has joined #openstack-meeting-321:26
*** sjmc7 has left #openstack-meeting-321:26
*** ying_zuo has quit IRC21:26
*** sjmc7 has joined #openstack-meeting-321:26
*** sjmc7 has left #openstack-meeting-321:27
*** pauloewerton has quit IRC21:28
*** dconde has joined #openstack-meeting-321:31
*** e0ne has quit IRC21:31
*** Rockyg has quit IRC21:31
*** vnyyad has joined #openstack-meeting-321:33
*** JeanBriceCombebi has joined #openstack-meeting-321:34
*** bhag has quit IRC21:41
*** Aish has joined #openstack-meeting-321:47
*** e0ne has joined #openstack-meeting-321:47
*** Aish has quit IRC21:47
*** Aish has joined #openstack-meeting-321:48
*** MarkAtwood has joined #openstack-meeting-321:50
*** e0ne has quit IRC21:50
*** yamahata has joined #openstack-meeting-321:51
*** julim has quit IRC21:51
*** vgridnev has quit IRC21:52
*** shwetaap has joined #openstack-meeting-321:54
*** neillc has joined #openstack-meeting-321:55
*** neillc has left #openstack-meeting-321:55
*** JeanBriceCombebi has quit IRC21:55
*** mounica_ has quit IRC21:56
*** salv-orl_ has joined #openstack-meeting-321:57
*** salv-orlando has quit IRC21:57
*** vnyyad has quit IRC21:58
*** shwetaap has quit IRC21:59
*** JeanBriceCombebi has joined #openstack-meeting-322:02
*** lblanchard has quit IRC22:06
*** kebray has quit IRC22:08
*** doug-fish has quit IRC22:10
*** jmckind is now known as jmac22:10
*** jmac is now known as mkz22:10
*** mkz is now known as jmckind22:11
*** banix has quit IRC22:18
*** Munish__ has quit IRC22:19
*** fitoduarte has quit IRC22:24
*** mickeys has joined #openstack-meeting-322:25
*** Sukhdev has joined #openstack-meeting-322:26
*** kebray has joined #openstack-meeting-322:26
*** MarkAtwood has quit IRC22:27
*** jaypipes has joined #openstack-meeting-322:47
*** cbouch has quit IRC22:51
*** sigmavirus24 is now known as sigmavirus24_awa22:53
*** jpomeroy has quit IRC22:54
*** shwetaap has joined #openstack-meeting-322:54
*** mestery has quit IRC22:55
*** safchain has quit IRC22:55
*** JeanBriceCombebi has quit IRC22:56
*** shwetaap has quit IRC22:59
*** jckasper has quit IRC23:03
*** Sukhdev has quit IRC23:04
*** Piet has quit IRC23:05
*** bklei has quit IRC23:06
*** bklei has joined #openstack-meeting-323:06
*** kebray has quit IRC23:10
*** bklei has quit IRC23:11
*** mchestr has quit IRC23:11
*** mchestr has joined #openstack-meeting-323:12
*** Sukhdev has joined #openstack-meeting-323:15
*** dconde has quit IRC23:15
*** sdake_ has joined #openstack-meeting-323:17
*** sdake has quit IRC23:18
*** cloudtrainme has quit IRC23:19
*** bpokorny_ has joined #openstack-meeting-323:21
*** jmckind has quit IRC23:23
*** mchestr has quit IRC23:23
*** mchestr has joined #openstack-meeting-323:23
*** jmckind has joined #openstack-meeting-323:24
*** bpokorny has quit IRC23:25
*** esp_ has joined #openstack-meeting-323:34
*** rhochmuth has quit IRC23:35
*** rbak has quit IRC23:35
*** fitoduarte has joined #openstack-meeting-323:37
*** sdake_ has quit IRC23:40
*** sdake has joined #openstack-meeting-323:40
*** bklei has joined #openstack-meeting-323:42
*** dconde has joined #openstack-meeting-323:44
*** jmckind has quit IRC23:47
*** bpokorny_ has quit IRC23:47
*** bpokorny has joined #openstack-meeting-323:48
*** adduarte has joined #openstack-meeting-323:48
*** dimtruck is now known as zz_dimtruck23:48
*** yushiro has joined #openstack-meeting-323:49
*** yushiro has left #openstack-meeting-323:49
*** kebray has joined #openstack-meeting-323:50
*** kebray_ has joined #openstack-meeting-323:51
*** fitoduarte has quit IRC23:51
*** kebray has quit IRC23:54
*** shwetaap has joined #openstack-meeting-323:55
*** rbrndt has quit IRC23:56
*** shwetaap has quit IRC23:59

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