Wednesday, 2016-05-04

*** pvaneck has quit IRC00:11
*** markvoelker has joined #openstack-meeting-300:14
*** egallen has quit IRC00:15
*** bpokorny has quit IRC00:18
*** ivar-lazzaro has joined #openstack-meeting-300:20
*** ddieterly has joined #openstack-meeting-300:22
*** ivar-lazzaro has quit IRC00:25
*** banix has joined #openstack-meeting-300:25
*** mtanino has quit IRC00:28
*** baoli has joined #openstack-meeting-300:34
*** baoli has quit IRC00:36
*** baoli has joined #openstack-meeting-300:36
*** yamahata has joined #openstack-meeting-300:39
*** mageshgv has joined #openstack-meeting-300:40
*** toddjohn_ has joined #openstack-meeting-300:42
*** toddjohn_ has quit IRC00:47
*** mageshgv has quit IRC00:54
*** baoli has quit IRC00:59
*** hoangcx has joined #openstack-meeting-301:03
*** hoangcx has left #openstack-meeting-301:04
*** baoli has joined #openstack-meeting-301:04
*** zz_dimtruck is now known as dimtruck01:10
*** armax_ has joined #openstack-meeting-301:11
*** armax has quit IRC01:12
*** armax_ is now known as armax01:12
*** sdake has quit IRC01:13
*** ivar-lazzaro has joined #openstack-meeting-301:14
*** armax has quit IRC01:14
*** vkmc is now known as Guest987401:20
*** stanzgy has joined #openstack-meeting-301:20
*** yamamoto has quit IRC01:21
*** Guest9874 is now known as cmkv01:22
*** cmkv is now known as violenciarivas01:22
*** fitoduarte has quit IRC01:23
*** violenciarivas is now known as vkmc01:23
*** zhurong has joined #openstack-meeting-301:23
*** armax has joined #openstack-meeting-301:26
*** baoli has quit IRC01:27
*** pgadiya has joined #openstack-meeting-301:31
*** yamamoto has joined #openstack-meeting-301:36
*** ddieterly is now known as ddieterly[away]01:38
*** iyamahat has quit IRC01:38
*** yamahata has quit IRC01:38
*** yamamoto has quit IRC01:41
*** yamamoto has joined #openstack-meeting-301:41
*** yamamoto has quit IRC01:42
*** vishwanathj has quit IRC01:48
*** ivar-lazzaro has quit IRC01:53
*** ivar-lazzaro has joined #openstack-meeting-301:55
*** pgadiya has quit IRC01:57
*** Poornima has joined #openstack-meeting-301:57
*** pgadiya has joined #openstack-meeting-302:05
*** ivar-lazzaro has quit IRC02:05
*** woodster_ has quit IRC02:08
*** ddieterly[away] has quit IRC02:11
*** yamahata has joined #openstack-meeting-302:13
*** jaypipes has quit IRC02:40
*** yamamoto has joined #openstack-meeting-302:43
*** markvoelker has quit IRC02:52
*** yamamoto has quit IRC02:54
*** banix has quit IRC03:02
*** Poornima has quit IRC03:13
*** pgadiya has quit IRC03:14
*** Poornima has joined #openstack-meeting-303:16
*** baoli has joined #openstack-meeting-303:31
*** baoli has quit IRC03:37
*** fitoduarte has joined #openstack-meeting-303:38
*** markvoelker has joined #openstack-meeting-303:52
*** yamamoto has joined #openstack-meeting-303:57
*** markvoelker has quit IRC03:57
*** e0ne has joined #openstack-meeting-303:59
*** e0ne has quit IRC04:01
*** e0ne has joined #openstack-meeting-304:02
*** pgadiya has joined #openstack-meeting-304:04
*** e0ne has quit IRC04:05
*** pt_15 has quit IRC04:06
*** yamamoto has quit IRC04:09
*** sverma has joined #openstack-meeting-304:11
*** yamamoto has joined #openstack-meeting-304:24
*** mageshgv has joined #openstack-meeting-304:26
*** yamamoto has quit IRC04:26
*** yamamoto has joined #openstack-meeting-304:30
*** vtech has quit IRC04:35
*** vtech has joined #openstack-meeting-304:36
*** yamamoto has quit IRC04:36
*** dimtruck is now known as zz_dimtruck04:43
*** amit213 has quit IRC04:44
*** toddjohn_ has joined #openstack-meeting-304:48
*** JoshNang has quit IRC04:50
*** toddjohn_ has quit IRC04:53
*** mageshgv has quit IRC04:56
*** vtech has quit IRC05:03
*** vtech has joined #openstack-meeting-305:05
*** mageshgv has joined #openstack-meeting-305:17
*** numans has joined #openstack-meeting-305:20
*** mageshgv has quit IRC05:23
*** kzaitsev_mb has joined #openstack-meeting-305:31
*** numans has quit IRC05:36
*** numans has joined #openstack-meeting-305:37
*** yamamoto has joined #openstack-meeting-305:37
*** hoangcx has joined #openstack-meeting-305:38
*** hoangcx has left #openstack-meeting-305:38
*** yamamoto has quit IRC05:45
*** rmoe_ has quit IRC05:58
*** rmoe has joined #openstack-meeting-305:59
*** nelsnelson has joined #openstack-meeting-306:03
*** nelsnels_ has quit IRC06:04
*** kzaitsev_mb has quit IRC06:04
*** david-lyle has quit IRC06:05
*** jrist has quit IRC06:06
*** salv-orlando has joined #openstack-meeting-306:07
*** kzaitsev_mb has joined #openstack-meeting-306:09
*** cartik has joined #openstack-meeting-306:09
*** ccamacho has joined #openstack-meeting-306:22
*** kzaitsev_mb has quit IRC06:29
*** cartik has quit IRC06:31
*** vtech has quit IRC06:35
*** salv-orlando has quit IRC06:36
*** eliqiao has quit IRC06:38
*** eliqiao has joined #openstack-meeting-306:38
*** vgridnev has joined #openstack-meeting-306:40
*** lpetrut has joined #openstack-meeting-306:40
*** e0ne has joined #openstack-meeting-306:41
*** anilvenkata has joined #openstack-meeting-306:44
*** markvoelker has joined #openstack-meeting-306:54
*** vtech has joined #openstack-meeting-306:59
*** vtech_ has joined #openstack-meeting-306:59
*** vtech has quit IRC06:59
*** markvoelker has quit IRC07:00
*** hdaniel has joined #openstack-meeting-307:06
*** matrohon has joined #openstack-meeting-307:14
*** egallen has joined #openstack-meeting-307:17
*** rossella_s has joined #openstack-meeting-307:18
*** jrist has joined #openstack-meeting-307:20
*** liangbo has joined #openstack-meeting-307:27
*** salv-orlando has joined #openstack-meeting-307:36
*** jrist has quit IRC07:38
*** lpetrut has quit IRC07:40
*** jschwarz has joined #openstack-meeting-307:41
*** salv-orlando has quit IRC07:41
*** gugl has quit IRC07:42
*** toabctl has quit IRC07:48
*** adi has joined #openstack-meeting-307:50
*** robcresswell has joined #openstack-meeting-307:53
*** lpetrut has joined #openstack-meeting-307:54
*** ttrifonov has quit IRC07:54
*** jlanoux has joined #openstack-meeting-307:55
*** ttrifonov has joined #openstack-meeting-307:55
*** kzaitsev_mb has joined #openstack-meeting-307:58
*** r1chardj0n3s has joined #openstack-meeting-307:58
*** lpetrut has quit IRC07:58
robcresswell#startmeeting horizon08:00
openstackMeeting started Wed May  4 08:00:20 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: horizon)"08:00
openstackThe meeting name has been set to 'horizon'08:00
r1chardj0n3so/08:00
robcresswellWow, quiet.08:01
r1chardj0n3swell, agreement will come more easily in this meeting :-)08:02
r1chardj0n3sso, what big-ticket decisions should we make?08:02
robcresswellI'll run through the notices for logs/lurkers anyway08:02
robcresswell#topic Notices08:02
*** openstack changes topic to "Notices (Meeting topic: horizon)"08:02
robcresswellI'm planning the midcycle, there'll be a form of some sort out later today(doodle, probably)08:03
robcresswellIf anyone wants to volunteer to host or suggest a location, now is the time.08:03
robcresswell#info Midcycle planning - suggested dates will be sent out soon. Potential hosts should also speak up :)08:04
robcresswellFor those not at the summit, the etherpads and their notes can be found here:08:04
robcresswell#link https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#Horizon08:05
*** stendulker has joined #openstack-meeting-308:05
robcresswell#info I've brought back the weekly bug report, which is linked in the horizon irc topic.08:06
robcresswell#link https://wiki.openstack.org/wiki/Horizon/WeeklyBugReport08:06
robcresswellThat's all for notices I think.08:06
robcresswellThe only agenda item needs more input, but will mentioned it quickly.08:07
robcresswellwill mention*08:07
robcresswell#topic Earlier feature freeze08:07
*** openstack changes topic to "Earlier feature freeze (Meeting topic: horizon)"08:07
robcresswell#link http://lists.openstack.org/pipermail/openstack-dev/2016-April/093525.html08:08
r1chardj0n3scurses, the archive doesn't follow that discussion well - I guess the message id got lost on the third message08:09
robcresswellIf you follow the email chain, you'll see a proposed earlier FF (1 week). Another suggestion is to freeze some aspects, like the horizon lib08:09
robcresswellAh, it doesnt08:09
robcresswellAs it happens, the first two are the valuable ones.08:09
robcresswellThe request and the releases meeting reference.08:09
r1chardj0n3syep08:10
*** yamahata has quit IRC08:11
robcresswell#info Proposed earlier feature freeze (R-6). Should we scope to entire codebase, or just horizon/ ?08:11
r1chardj0n3sthat's an interesting proposition!08:11
*** mbound has joined #openstack-meeting-308:11
*** matrohon has quit IRC08:11
r1chardj0n3sI heard someone say that plugins often extend openstack_dashboard panels - it'd be good to get more info on that08:12
robcresswellIt was mentioned a lot this cycle, the pain we're causing plugins.08:12
r1chardj0n3sbut freezing horizon/ earlier seems reasonable08:12
robcresswellWell for the all the internal Cisco work its almost exclusively extend o_d.08:12
robcresswellBecause we add steps to Routers or Networks etc, or new fields in details pages.08:12
r1chardj0n3sright, but hopefully the mechanisms to extend those things are coded in horizon/08:13
robcresswellThe issue is with the content changing late in the game, breaks things. Because you're still consuming a lot of the code in o_d08:14
robcresswelleven if the base classes are defined elsewhere08:15
r1chardj0n3sright08:15
*** thatsdone has joined #openstack-meeting-308:15
robcresswellAnyway, shifting a week earlier at least gives plugins a bit of breathing room.08:16
r1chardj0n3sagreed08:16
robcresswellI'll be working on adding liaison roles for the active plugins too, so we can keep in contact better08:17
robcresswellI'll bring up this discussion later and then post to the mailer.08:17
robcresswellThat's everything on the agenda, so I think you can have your evening back r1chardj0n3s :)08:18
r1chardj0n3sthanks robcresswell :-)08:18
robcresswell#endmeeting08:18
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:18
openstackMeeting ended Wed May  4 08:18:40 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:18
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-05-04-08.00.html08:18
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-05-04-08.00.txt08:18
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-05-04-08.00.log.html08:18
*** r1chardj0n3s has left #openstack-meeting-308:19
*** robcresswell has left #openstack-meeting-308:20
*** thatsdone has quit IRC08:26
*** jrist has joined #openstack-meeting-308:33
*** salv-orlando has joined #openstack-meeting-308:38
*** salv-orlando has quit IRC08:42
*** yamahata has joined #openstack-meeting-308:46
*** itxaka has joined #openstack-meeting-308:47
*** markvoelker has joined #openstack-meeting-308:50
*** neiljerram has joined #openstack-meeting-308:51
*** markvoelker has quit IRC08:55
*** thatsdone has joined #openstack-meeting-308:56
*** liangbo has quit IRC08:56
*** ifat_afek_ has joined #openstack-meeting-308:57
*** thatsdone has quit IRC08:59
*** idan_hefetz has joined #openstack-meeting-309:00
ifat_afek_#startmeeting vitrage09:00
openstackMeeting started Wed May  4 09:00:51 2016 UTC and is due to finish in 60 minutes.  The chair is ifat_afek_. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: vitrage)"09:00
openstackThe meeting name has been set to 'vitrage'09:00
idan_hefetzHi!!09:01
ifat_afek_he everyone :-)09:01
ifat_afek_Hi09:01
*** ohad has joined #openstack-meeting-309:01
*** thatsdone has joined #openstack-meeting-309:02
*** elisha_r has joined #openstack-meeting-309:02
elisha_rhey09:02
*** alexey_weyl has joined #openstack-meeting-309:02
alexey_weylHello guys ;)09:02
*** lhartal has joined #openstack-meeting-309:02
*** thatsdone has quit IRC09:02
*** iyamahat has joined #openstack-meeting-309:03
lhartalhi all.. long time :)09:03
ohadhi everyone09:04
*** eyalb has joined #openstack-meeting-309:04
eyalbhi09:04
ifat_afek_Our agenda today will be slightly different:09:05
ifat_afek_* Austin recap, by alexey_weyl and Ohad09:05
ifat_afek_* Newton release planning09:05
ifat_afek_Before we begin – we are going to move Vitrage IRC meeting one hour earlier, to 8:00 UTC. It will be on a different channel. We will send an update email with the final details.09:06
ifat_afek_#topic Austin recap09:06
*** openstack changes topic to "Austin recap (Meeting topic: vitrage)"09:06
*** doffek has joined #openstack-meeting-309:06
doffekhi09:06
ohadupdate from Austin:09:07
ohadGreat week for Vitrage! we introduced Vitrage to the OpenStack community and we got very positive feedback. thanks for everyone for the hard work before the summit, everything worked perfect and very stable.09:07
*** abalutoiu has joined #openstack-meeting-309:08
ohadActivities:09:08
ohad1. sessions: we had 2 sessions:09:09
ohad(a) Project Vitrage How to Organize, Analyze and Visualize your OpenStack Cloud I presented Vitrage and Alexey did a great live demo including switch failure coming from Nagios and CPU failure from AODH.of course both use cases included raising deduced alarms, deduced states and showing root cause analysis.09:10
ohad#link https://www.youtube.com/watch?v=9Qw5coTLgMo09:10
*** zhurong has quit IRC09:10
ohad(b) On the Path to Telco Cloud Openness: Nokia CloudBand Vitrage & OPNFV Doctor collaboration Gerald.K from Doctor OPNFV project presented Doctor requirements for fault management and I presented Vitrage09:10
ohad#link https://www.youtube.com/watch?v=ey68KNKXc5c09:11
ohad2. Vitrage Booth: we had a booth in the market place. we did a lot of live demos (3-5 demos every hour!) and again we got very good feedback.09:11
*** zhurong has joined #openstack-meeting-309:13
*** zhurong has quit IRC09:13
ifat_afek_I think ohad was disconnected...09:14
*** emalin has joined #openstack-meeting-309:14
emalinhi09:15
*** cartik has joined #openstack-meeting-309:15
*** ohad_ has joined #openstack-meeting-309:15
ohad_3. Meetings:09:15
ohad_(a) design session with AODH09:16
*** ohad has quit IRC09:16
ohad_alexey_weyl: can update on our meeting with AODH?09:16
alexey_weylYes, of course09:16
*** ohad_ has quit IRC09:17
alexey_weylFirst of all, we can see here the summary of the design session with AODH in the etherpad09:17
alexey_weylhttps://etherpad.openstack.org/p/newton-telemetry-vitrage09:17
alexey_weyl#link https://etherpad.openstack.org/p/newton-telemetry-vitrage09:17
alexey_weylA quick update about all the details09:17
*** ohad has joined #openstack-meeting-309:17
alexey_weyl1. We have talked with the team about adding external notifications from aodh09:18
alexey_weylThey agreed that such a feature needs to be in AODH, and they might even have that, they only need to understand how to configure it09:18
alexey_weyl2. Alarm name uniqueness - In aodh 2 alarms with the same name can't be defined. They said that this was a Wrong API feature, and that we can send them a patch to change it09:20
alexey_weyl3. New alarm type - We have showed to aodh that we need a new alarm type in aodh ("custom alarm"), so Vitrage will be able to push new alarms to aodh09:21
alexey_weylwhich aren't event or threshold09:21
alexey_weylthey agreed as well that we should have such an alarm, and that we should contribute it to AODH09:21
alexey_weylIn addition, we have explained the team about Vitrage and showed the a demo of 2 use cases of Nagios and aodh alarms09:22
alexey_weylThat's it for now09:22
ohadsorry, I had connectivity issue09:22
ohadthanks09:23
ohad(b) Doctor OPNFV project - we have discussion to kick off preparations for the joint booth demo planned for OPNFV summit in Berlin in June.09:23
ohad(c) Monasca - discussion on possible integration for Newton. Monasca can be additional data source for Vitrage. we will continue to work together on this.09:25
ohad(d) Congress - discussion on possible integration for Newton.09:25
alexey_weylI will add some more09:25
alexey_weylWe also had a meeting with the OPNFV \ NFV team in Red Hat09:26
alexey_weylIt was a good meeting, we showed and explained them about Vitrage, and they were really excited about that09:26
alexey_weylHad very good feedbacks as well09:26
ifat_afek_ohad, alexey_weyl: sounds great! thanks for the update09:27
ifat_afek_#topic Newton release planning09:27
*** openstack changes topic to "Newton release planning (Meeting topic: vitrage)"09:27
ifat_afek_Since there was no Vitrage design session in Austin, we are going to use the next one-two meetings for the planning. I opened an etherpad for this purpose:09:27
ifat_afek_#link https://etherpad.openstack.org/p/vitrage-newton-planning09:28
*** yamamoto has joined #openstack-meeting-309:28
ifat_afek_Also, everyone is welcome to add blueprints in our lanuchpad:09:28
ifat_afek_#link https://blueprints.launchpad.net/vitrage09:28
ifat_afek_go ahead and add stuff :-) I wrote just a few09:29
alexey_weyli will add another task:09:29
alexey_weylMulti-tenancy support - Admin adds templates, tenants can have a view only of tenant scope09:29
alexey_weylanother one: Overlapping Templates Support (critical usability improvement)09:30
eyalbI want to update that we pushed code to fix python 3.4 support09:30
eyalbboth vitrage and vitrage client09:31
ohadI added puppet installation09:33
alexey_weylHeat plugin for Vitrage09:33
*** sdague has joined #openstack-meeting-309:33
*** nadav_yakar has joined #openstack-meeting-309:34
*** yamamoto has quit IRC09:34
emalinI would add support of multiple transformers to one datasource09:34
emalinI mean requirement for support of multiple transformers to one datasource09:34
*** mbound has quit IRC09:35
ifat_afek_emalin: sure, you can edit our etherpad directly. I sent a link earlier09:35
ifat_afek_https://etherpad.openstack.org/p/vitrage-newton-planning09:35
*** nadav_yakar has left #openstack-meeting-309:36
*** lpetrut has joined #openstack-meeting-309:38
*** salv-orlando has joined #openstack-meeting-309:38
emalinifat_afek_ 10x09:39
alexey_weylLooks good :)09:39
ohadit's a good start, let's continue to fill it and agree on the plan for Newton in the next meeting09:39
*** emalin has quit IRC09:41
*** emalin has joined #openstack-meeting-309:42
elisha_rComing along nicely - nice and colorful etherpad :)09:42
ifat_afek_lots of work :-) Newton release will be interesting09:43
*** salv-orlando has quit IRC09:43
ifat_afek_cool, so let's take the time to think about it, and continue the discussion next time. I'll send a link to openstack ML, so other people might add their ideas09:44
ifat_afek_#topic Open Discussion09:44
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"09:44
*** emalin_ has joined #openstack-meeting-309:44
*** yamamoto has joined #openstack-meeting-309:44
ifat_afek_anyone wants to raise anything?09:44
ifat_afek_if not - then I have an issue09:45
ifat_afek_we should consider when would be a good time to apply to the TC and ask them to accept Vitrage as an official project09:45
ifat_afek_your thoughts?09:45
ifat_afek_I feel we are ready :-)09:45
alexey_weylSounds great :) I think we are on the right path :)09:46
ohad+109:46
ohadwe are more than ready09:46
elisha_r+109:46
eyalb+10009:46
ifat_afek_ok, if you are all for it, then I'll check the exact procedure and update you next week09:47
ifat_afek_any other discussions?09:47
*** emalin has quit IRC09:47
ifat_afek_so I guess we are done. goodbye everybody09:48
eyalbbye09:48
*** toddjohn_ has joined #openstack-meeting-309:48
*** eyalb has quit IRC09:48
ifat_afek_#endmeeting09:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:48
openstackMeeting ended Wed May  4 09:48:55 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-05-04-09.00.html09:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-05-04-09.00.txt09:48
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-05-04-09.00.log.html09:49
*** liangbo has joined #openstack-meeting-309:49
*** ohad has quit IRC09:50
*** yamamoto has quit IRC09:50
*** mbound has joined #openstack-meeting-309:51
*** toddjohn_ has quit IRC09:53
*** alexey_weyl has quit IRC09:54
*** flwang has quit IRC09:54
*** vdrok_ is now known as vdrok09:55
*** stanzgy_ has joined #openstack-meeting-309:55
*** stanzgy has quit IRC09:58
*** liangbo has quit IRC09:58
*** ifat_afek_ has quit IRC10:01
*** jrist has quit IRC10:02
*** lhartal has quit IRC10:04
*** elisha_r has quit IRC10:06
*** e0ne has quit IRC10:06
*** e0ne has joined #openstack-meeting-310:06
*** flwang has joined #openstack-meeting-310:08
*** tmazur has joined #openstack-meeting-310:13
*** emalin_ has quit IRC10:16
*** yamamoto has joined #openstack-meeting-310:21
*** alexey_weyl has joined #openstack-meeting-310:21
*** alexey_weyl has quit IRC10:22
*** doffek has left #openstack-meeting-310:35
*** salv-orlando has joined #openstack-meeting-310:40
*** jrist has joined #openstack-meeting-310:45
*** salv-orlando has quit IRC10:45
*** stendulker has quit IRC10:52
*** toddjohn_ has joined #openstack-meeting-310:56
*** baoli has joined #openstack-meeting-310:57
*** baoli has quit IRC10:57
*** baoli has joined #openstack-meeting-310:57
*** david-lyle has joined #openstack-meeting-310:58
*** baoli has quit IRC10:58
*** rtheis has joined #openstack-meeting-311:00
*** adi has quit IRC11:01
*** toddjohn_ has quit IRC11:01
*** abalutoiu has quit IRC11:03
*** ifat_afek has joined #openstack-meeting-311:05
*** stanzgy_ has quit IRC11:06
*** ifat_afek has left #openstack-meeting-311:13
*** belmoreira has joined #openstack-meeting-311:15
*** ccamacho is now known as ccamacho|include11:15
*** ccamacho|include is now known as ccamacho|getting11:16
*** ccamacho|getting is now known as ccamacho|coffee11:16
*** cartik has quit IRC11:18
*** jayahn has joined #openstack-meeting-311:21
*** yamamoto has quit IRC11:22
*** yamamoto has joined #openstack-meeting-311:25
*** vtech_ has quit IRC11:27
*** vtech has joined #openstack-meeting-311:28
*** tmazur has quit IRC11:31
*** banix has joined #openstack-meeting-311:33
*** tmazur has joined #openstack-meeting-311:34
*** salv-orlando has joined #openstack-meeting-311:40
*** mbound has quit IRC11:42
*** banix has quit IRC11:45
*** salv-orlando has quit IRC11:46
*** jayahn has quit IRC11:48
*** iyamahat has quit IRC11:54
*** yamahata has quit IRC11:54
*** itxaka is now known as itxaka|food12:00
*** ccamacho|coffee is now known as ccamacho12:03
*** markvoelker has joined #openstack-meeting-312:04
*** e0ne has quit IRC12:05
*** matrohon has joined #openstack-meeting-312:10
*** jaypipes has joined #openstack-meeting-312:11
*** davidlenwell has quit IRC12:13
*** davidlenwell has joined #openstack-meeting-312:15
*** mbound has joined #openstack-meeting-312:16
*** e0ne has joined #openstack-meeting-312:22
*** idan_hefetz has quit IRC12:23
*** doug-fish has joined #openstack-meeting-312:27
*** egallen has quit IRC12:28
*** yamamoto has quit IRC12:30
*** yamamoto has joined #openstack-meeting-312:31
*** pgadiya has quit IRC12:32
*** sankarshan_away is now known as sankarshan12:33
*** sankarshan has quit IRC12:35
*** sankarshan has joined #openstack-meeting-312:35
*** abalutoiu has joined #openstack-meeting-312:38
*** baoli has joined #openstack-meeting-312:38
*** baoli_ has joined #openstack-meeting-312:40
*** salv-orlando has joined #openstack-meeting-312:41
*** baoli has quit IRC12:43
*** pgadiya has joined #openstack-meeting-312:44
*** fitoduarte has quit IRC12:45
*** salv-orlando has quit IRC12:46
*** julim has joined #openstack-meeting-312:47
*** egallen has joined #openstack-meeting-312:54
*** andymaier has joined #openstack-meeting-312:56
*** sagar_nikam has joined #openstack-meeting-312:56
lpetrutHi guys13:00
abalutoiuHi13:00
sagar_nikamHi13:01
lpetrut#startmeeting hyper-v13:01
openstackMeeting started Wed May  4 13:01:31 2016 UTC and is due to finish in 60 minutes.  The chair is lpetrut. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: hyper-v)"13:01
openstackThe meeting name has been set to 'hyper_v'13:01
lpetrut#topic Openstack summit aftermath13:02
*** openstack changes topic to "Openstack summit aftermath (Meeting topic: hyper-v)"13:02
*** pt_15 has joined #openstack-meeting-313:03
lpetrutso, we had some really productive meetings with the freezer, monasca, magnum and designate guys13:03
sagar_nikamlpetrut: that's nice13:03
*** ddieterly has joined #openstack-meeting-313:04
lpetrutwe held the winstackers session as well, but unfortunately none of your guys made it to the session13:04
lpetruthere's a link to the etherpad: https://etherpad.openstack.org/p/newton-winstackers-design-session13:04
lpetrutthe topics mentioned here are roughly pointing out what we are planning to do for Newton13:05
*** pgadiya has quit IRC13:05
lpetrut#topic Shielded VMs13:05
*** openstack changes topic to "Shielded VMs (Meeting topic: hyper-v)"13:05
sagar_nikamlpetrut: had a question on summit meetings13:06
lpetrutsure13:06
sagar_nikamfrom the etherpad, you gave, we will have lot of nice support in Newton13:07
sagar_nikamwhat are the plans for monasca , freezer and designate13:07
domi007hi all13:07
sagar_nikami see only magnum in the etherpad13:07
lpetrutHi domi13:07
lpetrut#topic freezer13:07
*** openstack changes topic to "freezer (Meeting topic: hyper-v)"13:07
lpetrutso, we talked with the guys, and first, we are planning to refactor the existing Windows related bits13:08
sagar_nikamok, to use pyMI ?13:08
lpetrutthis will go in os-win13:08
sagar_nikamok13:08
lpetrutactually, they support older Windows versions such as Windows 7, Windows Server 2008, etc. and we'll have to use the old wmi lib in that case13:09
*** salv-orlando has joined #openstack-meeting-313:09
lpetrutthis also means that we won't be able to drop the pywin32 lib in this case13:09
lpetrut*dependency13:09
sagar_nikamas part of newton, are we planning feature parity with linux in freezer or only important use cases ?13:09
*** krotscheck_dcm is now known as krotscheck13:10
lpetrutso, they were already leveraging VSS, we are planning to improve this, and use the Hyper-V VSS provider as well13:11
lpetrutwe may also provide an MSI for freezer13:11
sagar_nikamok13:11
domi007sounds cool13:12
sagar_nikamlpetrut: let me know if your team needs any info from freezer core team, i can try to reach them13:13
sagar_nikamor for reviews as well13:13
lpetrutsagar_nikam: sure13:13
sagar_nikamthese changes are planned in newton ?13:13
*** salv-orlando has quit IRC13:13
lpetrutyep, I think we'll get everything in during Newton. At the moment, freezer is going through a refactoring, but we'll get the specs and os-win side code in ASAP13:14
*** itxaka|food is now known as itxaka13:14
sagar_nikamok13:14
lpetrutat some point, we'll need to have a CI as well13:15
sagar_nikamok13:15
lpetrutok, next topic13:16
sagar_nikammonasca ?13:16
lpetrut#topic monasca13:16
*** openstack changes topic to "monasca (Meeting topic: hyper-v)"13:16
*** mageshgv has joined #openstack-meeting-313:16
lpetrutensuring Windows support for Monasca seems pretty straight forward, leveraging stuff that we already had for Ceilometer13:17
sagar_nikamok, thats good13:18
sagar_nikamthere was one issue we had seen13:18
lpetrutcbelu sent a patch updating the existing Monasca windows agent to use os-win: https://review.openstack.org/#/c/311925/13:18
*** coolsvap has quit IRC13:18
sagar_nikamthe existing agent does not start on windows13:18
sagar_nikami mean monasca agent13:19
*** armax has quit IRC13:19
sagar_nikamthe patch above is in os-win, can you post the monasca patch as well13:20
*** armax has joined #openstack-meeting-313:20
lpetrutnot sure about the status of this agent, but I think that the patch Claudiu submitted may fix this issue13:20
sagar_nikamok13:20
lpetrut#topic magnum13:22
*** openstack changes topic to "magnum (Meeting topic: hyper-v)"13:22
lpetrutClaudiu Belu has spoke with dims, and it seems like we should make sure that kubernetes or docker swarm work on Windows13:23
sagar_nikammonasca support also planned in newton >13:23
lpetrutyep13:23
sagar_nikamok13:23
sagar_nikamWIN 2016 has support for docker13:23
*** abalutoiu has quit IRC13:24
sagar_nikamatleast TP413:24
sagar_nikamhad it13:24
lpetrutyep13:24
domi007looks promisimg13:24
sagar_nikamis that sufficient or we also need kubernetes ?13:24
sagar_nikamfor magnum support13:24
*** fitoduarte has joined #openstack-meeting-313:25
*** abalutoiu has joined #openstack-meeting-313:25
lpetrutwe'll also need kubernetes13:26
*** tonytan4ever has joined #openstack-meeting-313:26
sagar_nikamlpetrut: both docker-swarm and kubernetes needed for it to make to magnum  ?13:27
lpetrutI think one of them is enough for now13:28
sagar_nikamok13:28
*** geseib has joined #openstack-meeting-313:29
sagar_nikamsupport for windows in magnum depends on WIN 2016 release date ?13:29
sagar_nikamif WIN 2016 does not get released by newton, what is our plan ?13:30
lpetrutI think we can have the code in regardless of the WS 2016 release date13:30
sagar_nikamok cool13:30
domi007do we have any other topics?13:33
lpetrut#topic designate13:33
*** openstack changes topic to "designate (Meeting topic: hyper-v)"13:33
lpetrutso, adding Windows support over here seems to be pretty straight forward, as Designate will do zone transfers to manage records13:34
sagar_nikami think designate already has some windows support, not sure how much though13:34
*** vhoward has joined #openstack-meeting-313:35
*** egallen has quit IRC13:35
lpetrutnot really sure about the current status, but I'm sure we'll focus on it during Newton13:36
lpetrutso, going back to shielded vms13:36
lpetrut#topic Shielded VMs13:37
*** openstack changes topic to "Shielded VMs (Meeting topic: hyper-v)"13:37
lpetrutas TP5 is out, Iulia managed to push the updated code13:37
lpetruthttps://review.openstack.org/#/c/283564/ - os-win13:37
lpetruthttps://review.openstack.org/#/c/283567/ - compute-hyperv13:37
sagar_nikamok13:37
lpetrutthere will also be a tool, easing the way in which pdk files are generated13:37
*** lblanchard has joined #openstack-meeting-313:37
sagar_nikamplan to upstream it ? in newton ?13:37
lpetrutyep, hopefully13:38
sagar_nikamok13:38
*** fwdit has joined #openstack-meeting-313:38
lpetrutany other topics you guys would like to discuss?13:39
domi007yes, I tried to ceate a haproxy + freerdp setup13:39
sagar_nikamin newton, we will support cluster driver, FC, monasca, freezer, designate and magnum13:40
sagar_nikamlots of new features13:40
sagar_nikamnice progress13:40
domi007and freerdp dies because of haproxy's monitoring requests13:40
lpetrutthe cluster driver is already supported in mitaka, but only by the compute-hyperv driver (not the in-tree one)13:40
domi007I think I commented on an issue dealing with a similar error13:40
lpetrutdomi007: did you get in touch with our guy working on FreeRDP, Cosmin Muntean?13:41
sagar_nikamfreerdp - i have observed one issue, sometimes, keystrokes dont work in the console, only clicks work13:41
sagar_nikamafter restart of freerdp service, keystrokes work again13:42
domi007sagar_nikam: did you click in the grey bar before that?13:42
*** abalutoiu_ has joined #openstack-meeting-313:42
domi007lpetrut: let me get the github issue and see13:42
sagar_nikamdomi007: no, i was able to type earlier some commands, and then i find that keystrokes fail13:43
sagar_nikamhave seen in 2-3 times13:43
lpetrutby what I heard, there were some race conditions, not sure if those were fixed by now. Anyway, as soon as you find an issue, please file it on ask.cloudbase.it or the github repo and somebody will be on it ASAP13:44
sagar_nikamdomi007: using ha-proxy, with freerdp- how is your experience ?13:44
domi007lpetrut: is his github name c64cosmin?13:45
*** Poornima has quit IRC13:45
domi007he commented on the issue13:45
lpetrutyep13:45
*** yamamoto has quit IRC13:45
domi007sagar_nikam: I wanted to test it out but I hit the issue mentioned above13:46
sagar_nikamdomi007: can you give me the link ?13:46
sagar_nikamfor the issue13:46
domi007lpetrut: okay, he promised a new version 7 days ago13:46
domi007so I guess he is working on it13:46
*** jayahn has joined #openstack-meeting-313:46
*** d0ugal has quit IRC13:46
*** d0ugal has joined #openstack-meeting-313:47
domi007sagar_nikam: https://github.com/FreeRDP/FreeRDP-WebConnect/issues/12713:47
lpetrutgot it, I'll try to sync with him. Since we had a lot of talk around FreeRDP during the recent meetings, maybe he'll be able to join as well13:47
domi007great. it seems like a good PoC software but lacks in some robustness13:48
*** sdake has joined #openstack-meeting-313:48
domi007but it's great he is fixing it13:48
sagar_nikamlpetrut: how does freerdp scale ?13:48
*** sdake has quit IRC13:48
sagar_nikamif we install it one machine with good RAM and CPU, how many RDP consoles can it support ?13:49
sagar_nikami mean RDP consoles from horizon UI13:49
lpetrutnot sure ATM, but I guess it would make sense to do some stress testing and see what can be improved13:50
sagar_nikamok13:51
domi007that'd be great :)13:51
sagar_nikamdomi007: are you planning stress testing of freerdp ?13:51
domi007sagar_nikam: no, we don't really have resources for that. The only stress test I did was trying to use haproxy with it but that killed it fast :)13:53
sagar_nikamok13:53
sagar_nikami am trying to use NLB cluster for FreeRDP13:54
sagar_nikaminstead of ha-proxy13:54
*** mbound has quit IRC13:54
domi007in other news we are testing ovs 2.5 with Liberty...sadly a Mitaka patch needed to cheery picked into Liberty, now we are testing if it works with that13:54
sagar_nikamproviding the NLB cluster IP in nova.conf13:55
domi007sagar_nikam: that shouldn't make much difference, what are your results?13:55
sagar_nikamjust starting,13:55
*** mbound has joined #openstack-meeting-313:55
sagar_nikamshould have the results in next meeting hopefully13:55
domi007sagar_nikam: Great!13:56
*** sigmavirus24_awa is now known as sigmavirus2413:56
domi007my experience was that it died so fast i wasn't able to see it working at all :) hope it's better for you13:56
*** jmckind has joined #openstack-meeting-313:57
sagar_nikamstandalone freerdp, not usin NLB cluster, worked for me, but i did not try keep the console open for long13:58
sagar_nikami may hit the issue you are mentioning if i keep the console open for long and try some operations13:58
lpetrutlooks like we have only a couple of minutes left, anything else?13:59
domi007I don't have anything :)13:59
*** toddjohn_ has joined #openstack-meeting-313:59
lpetrutok, thanks guys13:59
sagar_nikamnothing much from my side, i hope all the patches/features we are planning in newton gets merged13:59
sagar_nikamfast13:59
lpetrut#endmeeting13:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:59
openstackMeeting ended Wed May  4 13:59:58 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-05-04-13.01.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-05-04-13.01.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-05-04-13.01.log.html14:00
ajoqos folks around?14:00
ajoI'm looped in in a meeting I cannot leave yet14:00
ajoin in -> in :)14:00
*** bklei has joined #openstack-meeting-314:00
*** jtomasek has quit IRC14:02
*** abalutoiu has quit IRC14:03
*** iyamahat has joined #openstack-meeting-314:04
*** jtomasek has joined #openstack-meeting-314:04
*** sdake has joined #openstack-meeting-314:06
*** mbound has quit IRC14:08
*** salv-orlando has joined #openstack-meeting-314:10
*** rbak has joined #openstack-meeting-314:13
*** anilvenkata has quit IRC14:14
*** salv-orlando has quit IRC14:15
*** absubram has joined #openstack-meeting-314:16
*** yamahata has joined #openstack-meeting-314:20
*** salv-orlando has joined #openstack-meeting-314:24
*** fwdit has quit IRC14:25
*** zz_dimtruck is now known as dimtruck14:27
*** fitoduarte has quit IRC14:28
*** mtanino has joined #openstack-meeting-314:28
*** salv-orlando has quit IRC14:29
*** mbound has joined #openstack-meeting-314:29
*** vtech has quit IRC14:30
*** ddieterly is now known as ddieterly[away]14:31
*** julim has quit IRC14:32
*** yamamoto has joined #openstack-meeting-314:32
*** yamamoto has quit IRC14:32
*** Swami has joined #openstack-meeting-314:33
*** yamamoto has joined #openstack-meeting-314:33
*** mbound has quit IRC14:34
*** julim has joined #openstack-meeting-314:34
*** sagar_nikam has quit IRC14:37
*** irenab_ has joined #openstack-meeting-314:38
*** ddieterly[away] is now known as ddieterly14:39
*** irenab has quit IRC14:40
*** irenab_ is now known as irenab14:40
*** pcarver has joined #openstack-meeting-314:43
*** rhochmuth has joined #openstack-meeting-314:46
*** e0ne has quit IRC14:50
*** yamahata has quit IRC14:52
*** yamahata has joined #openstack-meeting-314:53
*** mbound has joined #openstack-meeting-314:53
*** salv-orlando has joined #openstack-meeting-314:54
*** jmckind_ has joined #openstack-meeting-314:55
*** vtech has joined #openstack-meeting-314:56
*** jmckind has quit IRC14:58
*** salv-orlando has quit IRC14:59
*** fabiog has joined #openstack-meeting-314:59
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed May  4 15:00:02 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
rhochmutho/15:00
bkleio/15:00
fabiogo/15:00
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:00
*** mhoppal has joined #openstack-meeting-315:00
rhochmuthhi everyone15:00
mhoppalhello15:00
bkleihi15:00
rhochmuthit looks like we have a full agenda15:00
jayahnhi15:00
*** witek has joined #openstack-meeting-315:01
rbako/15:01
rhochmuthhi jayahn15:01
witekhello15:01
jayahngood to see you here :)15:01
rhochmuthis everyone recovered from last week15:01
rhochmuthi'm not15:01
witek:)15:01
rhochmuthso, there is an agenda that i posted the link for up above15:02
rhochmuththe first topic is mic-cycle planning15:02
rhochmuth#topic mid-cycle15:02
*** openstack changes topic to "mid-cycle (Meeting topic: monasca)"15:02
witekwe would be interested in hosting mid-cycle in Munich15:02
witekat the end of July15:03
rhochmuthi put in a travel request with my mgmt15:03
rhochmuthbut, haven't heard back yet15:03
rhochmuthi only asked last night15:03
*** emagana has joined #openstack-meeting-315:03
fabiogI can do it in Munich only 07/27-2915:03
bkleii still need to get permission15:03
rhochmuthhopefully, i'll know more in a couple of days15:04
rhochmuthso, July 27, 28 and 2915:04
bkleiwill others be able to travel to munich?15:04
rhochmuthwho cares15:04
bklei:)15:04
fabiogrhochmuth: don't be mean15:04
*** yamamoto has quit IRC15:04
jayahni will not be able to travel to there.. almost for sure.15:04
rhochmuthsorry, sometimes my fingers type on there own15:05
fabiogalternatively Cisco could host it in SJC July 19 to 2115:05
rhochmuthso, we'll need to get a head-count on who can travel15:05
rhochmuthand see if this makes sense15:05
witekwe can set a doodle for that15:05
rhochmuthlet's try to get travel requests done by next week15:05
rhochmuthok, that sounds good too15:06
rhochmuthjayahn, i don't recognoize your irc15:06
rhochmuthcan you introduce yourself15:06
jayahnah. yeap.15:06
jayahnthis is Jaesuk Ahn from skt.15:06
jayahnfrom Korea, and it is midnight here. :)15:07
rhochmuthohh, got it15:07
rhochmuththanks for attending15:07
jayahnno problem.15:07
rhochmuthwe are also talking about a new time slot for meetings15:07
rhochmuthso, witek, you are going to create a doodle15:08
rhochmuththat will be great15:08
witekyes, for mid-cycle15:08
rhochmuthi think i'm available for travel anytime15:08
rhochmuthjust don't know about travel budget15:08
witek#action Witek sets doodle for mid-cycle15:08
rhochmuthok, let's sync-up next week on this topic and see if we can do a mid-cycle15:09
jayahnfor meeting time, midnight is not that bad for me. we can keep the current time.15:09
*** jkeen has joined #openstack-meeting-315:09
fabiogI got the doodle up15:10
*** cbellucci has joined #openstack-meeting-315:10
witek:)15:10
fabiogwitek: sorry I was doing it without paying attention to the chat15:10
fabioghttp://doodle.com/poll/x6bf8ev6wvenfkdy15:10
rhochmuthfabiog is a doodle master15:10
witeknp15:10
*** vgridnev has quit IRC15:10
fabiogrhochmuth: I should change my biz title into that :-)15:10
*** vgridnev has joined #openstack-meeting-315:11
*** vgridnev has quit IRC15:11
rhochmuthFabiog, Doodle Master Extrodianaire15:11
rhochmuthat your service15:11
rhochmuthLet's move on15:11
rhochmuth#topic stable branch15:11
*** openstack changes topic to "stable branch (Meeting topic: monasca)"15:11
rhochmuthhttps://review.openstack.org/#/c/306303/15:12
witekyes, we have that obvious bug in monasca-ui15:12
witekin my opinion we should mergre into stable15:12
*** a_ has joined #openstack-meeting-315:12
bkleii'm not sure about that -- i think we use /static at twc15:13
witekhm15:14
bkleiwill confirm and add a comment to review15:14
witekOK, thanks15:14
*** JOlsen has joined #openstack-meeting-315:14
*** sverma has quit IRC15:15
*** sverma has joined #openstack-meeting-315:15
*** a_ has quit IRC15:15
rhochmuththanks bklei15:15
bkleicould you set STATIC_URL to / and have it work witek?15:15
rhochmuth#topic reviews15:15
*** openstack changes topic to "reviews (Meeting topic: monasca)"15:15
witekbut this would change the location of other static resources, right?15:16
bkleiyeah -- i guess so15:16
*** armax has quit IRC15:17
*** stephen-ma has joined #openstack-meeting-315:17
*** absubram has quit IRC15:17
bkleiwe can move on - will confirm if this patch would work for us15:17
rhochmuthso there is revice https://review.openstack.org/#/c/307963/15:17
rhochmuthfix metric-list limits15:18
bkleitwc REALLY wants this15:18
*** spzala has joined #openstack-meeting-315:18
bkleilooks like it's in good shape?15:18
*** lpetrut has quit IRC15:18
rhochmuthok, i'll review today, and probably end up merging15:18
*** absubram has joined #openstack-meeting-315:18
bkleiawesome15:19
*** absubram has quit IRC15:19
rhochmuthwitek, are you ok with this one15:19
*** Swami_ has joined #openstack-meeting-315:19
witekI haven't reviewed :(15:19
*** vhoward has quit IRC15:19
rhochmuthit is basically a bug fix on metrics list15:19
rhochmuthSo, there is, https://review.openstack.org/#/c/289675/15:20
rhochmuthi started reviewing this yesterday15:20
rhochmuthbklei, it looks like you've +1'd that one15:20
rhochmuthhave you done any performance testing at twc15:21
bkleijust functional testing, no perf tests yet15:21
rhochmuthalso, to see the benefits of this change, you'll need to modify grafana 215:21
rhochmuthor rbak will15:21
bkleiyeah -- rbak is eager to do that :)15:21
rhochmuthok, assuming i get time today, i'll do a review and merge15:22
rhochmuththis shouldn't impact anyone15:22
bkleigreat -- yeah, shouldn't break any existing code path15:22
rhochmuththe new capability is only enable if the group_by is specify as a qwuery param15:22
*** Swami has quit IRC15:22
rhochmuthso, this is low-risk15:22
*** lpetrut has joined #openstack-meeting-315:23
rhochmuthi'm assuming it will be merged today15:23
*** bpokorny has joined #openstack-meeting-315:23
*** slogan_ has joined #openstack-meeting-315:23
rhochmuthhttps://review.openstack.org/#/c/306621/15:23
bkleithat's me15:23
bkleii think i've rolled in feedback to date15:23
rhochmuthwell, you didn't get my feedback15:24
rhochmuth:-)15:24
bkleiany objection to this given the larger conversation with the neutron ptl?15:24
bklei:)15:24
rhochmuthi'll start reviewing this one too15:24
rhochmuthwe didnt' discuss this with armando15:24
rhochmuthbut, we could add him to the review15:24
bkleicool.  i'm guessing if we get neutron to start pushing data to monasca, it will give us more than this.  but this is the bare minimum our customers are asking for15:25
bkleisure, will add him15:25
bkleibut i'm guessing, based on the conversations with him -- real code is years away :)15:25
bkleiis it armando dominguez?15:25
rhochmuthArmando Migliaccio15:26
bkleithx15:26
rhochmuthhe was at the 4th session last Wednesday15:27
bkleiadded him15:27
rhochmuthdid you meet him15:27
bkleii was in that session, but didn't talk with him directly15:27
*** armax has joined #openstack-meeting-315:27
bkleii did talk with maryam tahhan -- she was thinking about doing something similar to my patch, so i added her15:27
rhochmuthi'll add some folks from the hpe neutron team as well15:27
bkleicool15:27
rhochmuthlike ed bak, ryan's dad15:28
bklei+115:28
*** fitoduarte has joined #openstack-meeting-315:28
slogan_small world15:28
rhochmuthhi syd15:28
slogan_morning15:28
slogan_sick as a dog, caught something on the flight back15:28
rhochmuthyes, ed and ryan might be the first father son team in openstack15:28
slogan_that's awesome15:28
rhochmuthwe might have an entire generation of openstackers15:29
rhochmuthnext15:29
rhochmuthhttps://review.openstack.org/#/c/286281/15:29
rhochmuththe infamous vertica hint15:29
rhochmuthok, will review15:29
bklei:) that's me too15:29
bkleithx. turned out to be pretty small change15:30
bkleiand keeps existing behavior, unless the cfg setting is there15:30
rhochmuthbtw, what happened with removing the temp tables15:30
rhochmuthisn't there code that needs to be submitted for that one too15:30
bkleiyes, i'm on the hook for that15:31
bkleihope to get to that next week15:31
rhochmuthok, sounds good15:31
rhochmuthare you using that change in prodiuction already?15:31
bkleii'd tested it, but needed cleanup.  it works though15:31
bkleino -- not using the change yet15:32
rhochmuthok, will wait for your review15:32
bkleiso far, we haven't carried anything local15:32
bkleicool15:32
rhochmuthwe're going to be picking up some of these changes too15:32
bkleiyeah -- that one in particular should really help vertica15:32
bkleiKV -- we'll see15:32
rhochmuthhttps://review.openstack.org/#/c/251674/15:33
rhochmuthhttps://review.openstack.org/#/c/28500015:33
bkleithat one and the next go together15:33
rhochmuthJoe Keen is working on that15:33
bkleiyeah -- until this gets fixed, the rally tests we're trying to push for monasca are on hold15:33
rhochmuthAhhh, I see15:34
bkleipython client needs to be in global reqs for rally tests to work with monasca15:34
rhochmuthSo, I'm assumign Joe will try and get this resolved fairly soon15:34
bkleiawesome15:34
*** absubram has joined #openstack-meeting-315:34
jkeenbklei, do you know how much of Monasca needs to be in the projects.txt for your tests to work?15:34
rhochmuthshoudl probably reach out to him if it starts getting delayed again15:34
*** belmoreira has quit IRC15:34
bkleijkeen -- not sure, i can connect you with yan, who knows more than me (via email)15:35
jkeenThat would be great.15:35
bkleithx15:36
rhochmuthso while we have joe and michael i wanted to let folks know about periodic notifications15:36
rhochmuth#topic periodic notifications15:37
*** openstack changes topic to "periodic notifications (Meeting topic: monasca)"15:37
rhochmuthjoe, can you post link to blueprint?15:37
*** armax has quit IRC15:38
*** armax has joined #openstack-meeting-315:38
mhoppalhttps://blueprints.launchpad.net/monasca/+spec/heat-integration15:39
rhochmuthhttps://review.openstack.org/#/c/296813/15:39
mhoppalbasically we are adding in the ability to send a notfiication over and over at a given period until the state of the alarm it is associated with changes15:40
rhochmuthhttps://review.openstack.org/#/c/310534/15:40
rhochmuthhttps://review.openstack.org/#/c/308502/15:40
mhoppalwe are only allowing this on webhooks, we are doing this for heat autoscaling15:40
bkleiso we're saying 0 or 1 -- but should it be 0 or n?15:40
mhoppalfor now 0 or 115:40
jkeen0 or 1 makes the problem much easier for now.15:40
mhoppalbut going forward we left it open to add more intervals15:40
jkeenWe can expand that later to a larger predefined set of intervals.15:40
*** sdake_ has joined #openstack-meeting-315:40
mhoppalpretty easy to add more intervals15:40
bkleiok, and heat works with 1 minute re-alarms?15:40
rhochmuthdo we want units in minutes or seconds15:41
bkleilike -- is that what ceilometer does?15:41
jkeenYes, heat requested that timing.15:41
bkleiperfect15:41
rhochmuthso, i have a couple of comments i'll add to the reviews15:42
rhochmuththis does involve a schema change to mysql15:42
rhochmuthpostres, …15:42
rhochmuthright?15:42
mhoppalyes and also adding another kafka topic15:42
bkleioooh, we'll need to track that in our puppet module15:43
*** sdake has quit IRC15:43
rhochmuthyup15:43
bkleicould you add the topic details to the blueprint?15:43
bkleior is it in the docs in one of your reviews15:43
*** jmckind has joined #openstack-meeting-315:43
*** salv-orlando has joined #openstack-meeting-315:44
jkeenI can add more information to the blueprint15:44
bkleigracias15:44
rhochmuthbasically schema changes for databases and kafka changes15:44
bkleiok, hopefully we'll have an upgrade path?15:45
rhochmuthwhat's an upgrade path?15:45
witekbklei: schema update script?15:45
bkleiupgrading the mysql schema15:45
bkleiyeah15:45
*** cbouch has joined #openstack-meeting-315:45
*** jschwarz has quit IRC15:45
bklei(we can't drop the db and start over)15:46
rhochmuthwe don't do db migrations, if that is what you mean15:46
bkleiyup15:46
rhochmuthi think it is just the addition of a column15:46
*** AlanClark has joined #openstack-meeting-315:46
*** sdake_ has quit IRC15:46
bkleiok, so an alter table command15:46
rhochmuthhttps://review.openstack.org/#/c/308502/13/devstack/files/schema/mon_mysql.sql15:46
*** mhoppal_ has joined #openstack-meeting-315:46
rhochmuthcurrently called periodic_interval at the link above15:46
bkleinot too bad, we can migrate that ourselves15:47
*** mhoppal has quit IRC15:47
rhochmuthyes, just alter table15:47
*** jmckind_ has quit IRC15:47
*** geseib has quit IRC15:47
rhochmuthpossible name change on the column based on feedback15:47
*** ccamacho is now known as ccamacho|away15:47
*** geseib has joined #openstack-meeting-315:47
bkleiok, we'll just need to remember to add the column when we pull that in15:48
bkleithx15:48
*** Sukhdev has joined #openstack-meeting-315:48
rhochmuthok, will close on that topic then and look for feedback on reviews15:48
rhochmuthi'm guessing this is a week or two from merging15:48
*** chandanc has joined #openstack-meeting-315:49
*** MarkAtwood has joined #openstack-meeting-315:49
*** matrohon has quit IRC15:49
rhochmuthon a side-note, we are looking into dropping the mysql from the api, and just have sqla15:49
*** e0ne has joined #openstack-meeting-315:49
rhochmuthalso, looking into the notification engine15:50
rhochmuth#topic vitrage15:51
*** openstack changes topic to "vitrage (Meeting topic: monasca)"15:51
rhochmuthso we had some interesting discussions with vitrage at the summit15:51
rhochmuththey would like to integrate with monasca15:51
rhochmuthi posted some requirements that they listed15:51
slogan_where?15:51
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:51
slogan_ah, ok15:52
rhochmuthi don;'t think we'll have time to discuss today unfortunately15:52
rhochmuthbut, i wanted to tee that one up15:52
*** andymaier has quit IRC15:52
slogan_the alarm CRUD operations seems like good things to have15:53
rhochmuthyeah, i think that makes sense, but i think it is more complicated than oru early discussions led us to believe15:53
rhochmuthso, we'll need to have some design sessions on this one15:54
rhochmuthon this topic15:54
rhochmuthwitek: does everythign make sense for the sproadic metrics and the latched alarms15:54
*** sankarshan is now known as sankarshan_away15:55
*** jlanoux has quit IRC15:55
witekyes, Tomasz rewrites his change in monasca-thresh15:55
rhochmuthok, hopefully we got it this time around15:55
witekhe has put what he's done sofar to gerrit15:56
witekcomments are wellcome :)15:56
rhochmuthok, i'll start taking a look15:57
rhochmuthand i'll ping craig15:57
rhochmuthso, we are down to two minutes15:57
rhochmuthand we didnt' cover everything15:57
*** banix has joined #openstack-meeting-315:57
rhochmuthalso, next week the transform engine will be avaialble for review15:58
witekcool15:58
rhochmuthmaybe we need two meetings15:58
rhochmutha week15:58
jayahncool15:58
*** kzaitsev_mb has quit IRC15:58
bklei:(15:58
rhochmuththere is a blueprint on the transform engine15:58
rhochmuthbut, the actual design is still in progress of getting posted to the monasca wiki at15:59
*** salv-orlando has quit IRC15:59
rhochmuthhttps://wiki.openstack.org/wiki/Monasca#Transform_and_Aggregation_Engine15:59
*** kzaitsev_mb has joined #openstack-meeting-315:59
rhochmuthActually, it looks like it is all there15:59
rhochmuthso, please start taking a look15:59
rhochmuth they just published that last night15:59
*** catherineD|2 has joined #openstack-meeting-316:00
rhochmuthwe've run out of time again16:00
witekthank you Roland16:00
*** cjvolzka has joined #openstack-meeting-316:00
rhochmuthi need to close the meeting16:00
jayahnthanks16:00
slogan_thanks Roland16:00
rhochmuthbye everyone16:00
bkleicya16:00
rhochmuth#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed May  4 16:00:52 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
witekbye16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-05-04-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-05-04-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-05-04-15.00.log.html16:00
*** salv-orlando has joined #openstack-meeting-316:00
*** bklei has quit IRC16:00
markvoelker#startmeeting defcore16:01
openstackMeeting started Wed May  4 16:01:01 2016 UTC and is due to finish in 60 minutes.  The chair is markvoelker. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: defcore)"16:01
openstackThe meeting name has been set to 'defcore'16:01
markvoelker#chair hogepodge16:01
openstackCurrent chairs: hogepodge markvoelker16:01
markvoelkero/16:01
hogepodgeo/16:01
*** jkeen has quit IRC16:01
markvoelker#info Meeting Agenda: https://etherpad.openstack.org/p/DefCorePostAustin.116:01
catherineD|2o/16:01
*** tmazur has quit IRC16:01
*** stephen-ma has quit IRC16:01
markvoelkerSmall crowd today...everyone still hung over from Austin? =p16:01
docaedoo/16:02
*** amotoki has joined #openstack-meeting-316:02
catherineD|2yea16:02
*** lpetrut has quit IRC16:02
*** witek has left #openstack-meeting-316:02
docaedoI'm still so deeply buried :)16:02
*** jayahn has quit IRC16:02
markvoelker#info Co-chair hiatuses (hiatusi?)16:02
*** salv-orlando has quit IRC16:03
*** tmazur has joined #openstack-meeting-316:03
markvoelkerFYI, Egle is going to be away for a couple of weeks while welcoming a new addition to her family.  I'll be away the next two weeks due to business travel.16:03
markvoelkerSo, in the meantime, email is probably the best way to get a hold of us. =)16:03
hogepodgeI'll be running the meetings, but I imagine during that time we'll put major decisions on hold. :-D16:03
markvoelkerhogepodge has graciously volunteered to run the meeting next week and the week after.16:03
markvoelkerWith that, let's dive into today's (probably short) agenda....16:04
markvoelker#topic Cycle Naming16:04
*** openstack changes topic to "Cycle Naming (Meeting topic: defcore)"16:04
*** woodster_ has joined #openstack-meeting-316:04
*** slogan_ has quit IRC16:04
markvoelkerIn today's etherpad you'll find the list of candidate names we received at the Austin summit for the next DefCore cycle.16:04
*** JOlsen has quit IRC16:05
*** cbellucci has quit IRC16:05
markvoelkerAs you're all aware, there are only two hard problems in computer science: cache invalidation, naming things, and off by one errors. =)16:05
*** yamamoto has joined #openstack-meeting-316:05
*** fabiog has quit IRC16:05
markvoelkerThe naming is fairly inconsequential to me personally, but I don't think we have enough quorum today for a vote, so I'll propose that I send out out Doodle poll today to the alias with voting to conclude Friday.16:06
markvoelkerAny objections?16:06
hogepodgenope16:06
*** mhoppal_ has quit IRC16:06
*** toddjohn_ has quit IRC16:07
markvoelker#action markvoelker to send out a doodle poll for naming the DefCore cycle, voting to conclude Friday16:07
markvoelkerOK, moving on...most of the rest of the agenda today is a quick rundown of AI's from Austin so folks know what they're working on16:07
hogepodgeadd suggestions to the list now if there's a name you like better16:07
markvoelker#topic Gate Fixes16:07
*** openstack changes topic to "Gate Fixes (Meeting topic: defcore)"16:07
markvoelkerSeveral AI's here.  hogepodge, anything you want to say about the JSON schema patch?16:08
hogepodgeI've written a schema and have tox code in place to check it16:08
hogepodgeI need to refactor the tox a bit, and would like a sanity check of the schema. Once we merge it we can update the gate to make it non-voting, and once we're happy with that we can make it voting.16:09
catherineD|2so we will stop usong the rst schema version ?16:09
hogepodgeI generated some of the schema, the rewrote it by hand.16:09
hogepodgecatherineD|2: yes? Should we bump the version to 1.5 to keep the historic, since there will be changes to the guidelines (minor for consistency)16:10
catherineD|2I think so that would be better16:10
markvoelkerRight, generally the idea is we've had our schemas documented in the doc/source/schema folder for a while, but haven't been validating them at the gate16:10
hogepodgeok, I'll send the updates today16:10
markvoelker(and have missed several violations)16:11
markvoelkerSo hopefully this should fix that.  Long overdue, IMHO, so thanks for working on it hogepodge. =)16:11
hogepodgeyup, and the new formal schema did a really good job of picking up minor violations16:11
hogepodgeit was fun16:11
catherineD|2RefStack relies on the schema to render Guidlines16:12
*** gema has joined #openstack-meeting-316:12
markvoelkercatherineDl2: so hopefully this should prevent us from breaking you more often. =)16:12
catherineD|2we will prepare to use the new json format schema .. I think it is better16:12
markvoelker++16:13
markvoelkerOk, next item in this topic is doc generation.  hogepodge, that's you again.  Anything you need clarified?16:13
catherineD|2hogepodge: give us a heads up before merging this patch ...16:13
hogepodgenope, I just put it there to reinforce that it's on my agenda. I'll speak with the docs team about how to move forward.16:13
markvoelkerJust one note: our generated docs currently show all the process docs (2015A, B, 2016A).  I'm not sure that's useful.16:14
*** hdaniel has quit IRC16:14
markvoelkerWe should probably show the one that's actually being followed and not the others.16:14
hogepodge+116:14
catherineD|2+116:14
markvoelkerhttp://docs-draft.openstack.org/65/311265/3/check/gate-defcore-docs/9ee574a//doc/build/html/ < an example16:14
*** yamamoto has quit IRC16:14
markvoelkerWe might want to rework that page a bit to highlight Guidelines that are currently used for logo programs too I suppose16:15
hogepodge+116:15
markvoelkerAnyhow, we can take up stuff like that via gerrit, just a couple of things to think about. =)16:16
markvoelkerOk, next item is mine: check next.json16:16
markvoelkerI'll have to go back to the Austin pad to clarify, but I think this one was to clean up some minor schema violations and make sure achievements are synced.16:17
hogepodgemarkvoelker: this seems to overlap under the schema work I'm doing? That will add formal checks for next.json16:17
hogepodgemarkvoelker: ah, I see16:18
markvoelkerhogepodge: exactly what I was going to say =)16:18
*** numans has quit IRC16:18
markvoelkerSo, I'll leave the schema checks to your patch so we don't duplicate effort16:18
hogepodgethe script to check achievements will be important. I'm sure there's a lot of drift between scoring and guideline16:18
hogepodgeit would be nice if the guideline was the source of truth rather than the scoring document16:18
markvoelkerQuite possibly, yes.  I have an AI to work on the scoring script too a few bullets down, so I'll take this up there.16:19
hogepodge(but I imagine the scoring document is the source of truth right now)16:19
VanLWhere is the scoring doc currently?16:19
*** rhagarty_ has quit IRC16:19
markvoelkerVanL: https://github.com/openstack/defcore/blob/master/working_materials/scoring.txt16:19
*** rhagarty has joined #openstack-meeting-316:19
VanLmarkvoelker: Thnx16:19
markvoelkerVanL: you may recall that some folks asked for a spreadsheet-friendly version of that...the tabulate_scores.py script in the same directory will also generate a CSV for you if you like16:20
VanLOk. I remember when it moved off the googlesheet, but lost track after that.16:21
markvoelkerOk,last item on this topic: hogepodge had an AI to clean out the guideline directories.16:21
markvoelkerhogepodge: any questions on that one?16:21
* markvoelker hears none, so onward...16:22
markvoelker#topic Testing fixes/additions16:23
*** openstack changes topic to "Testing fixes/additions (Meeting topic: defcore)"16:23
catherineD|2did we skip this topic Patch for Compute Flag Gap in 2015.07/16:23
markvoelkercatherineDl2: oops, yes...sorry, looking at wrong pad16:23
*** mbound has quit IRC16:23
*** sdake has joined #openstack-meeting-316:24
markvoelker#topic Patch for Compute Flag Gap 2015.0716:24
*** openstack changes topic to "Patch for Compute Flag Gap 2015.07 (Meeting topic: defcore)"16:24
catherineD|2I happen to have question about this topic :-)16:24
markvoelkercatherineDl2: go for it16:24
*** mickeys has joined #openstack-meeting-316:24
catherineD|2do we automatically carry the flag test over to the new Guideline?16:25
markvoelkercatherineDl2: generally, no.16:25
catherineD|2do we have process for flag tests carry over ?16:25
markvoelkerThe idea was generally that we'd review those flags with each new Guideline (usually a thing that whoever is playing point for that project works on)16:25
VanLcatherineD|2: To carry over the flag, or carry over the test?16:25
catherineD|2carry over the flag16:26
markvoelkerAnd of course folks can always request flags once they run into problems during the vendor testing period that starts at each Summit (see timeline in etherpad)16:26
* gema sits at the back of the room, quietly16:26
markvoelkerI'm expecting to see some incoming soon, personally (since I know we have some folks with testing in flight). =)16:27
markvoelkercatherineDl2: make sense?16:27
hogepodgeI'd like us to actively review flags and determine which need to be carried over, and which should be dropped.16:27
catherineD|2markvoelker: yup thx16:27
catherineD|2hogepodge: ++16:27
markvoelkerhogepodge: it does seem like an area we could tighten up process around16:27
hogepodgebut dropping all means none slip through the cracks, but it leads to inconsistencies like with have with 2015.0716:28
catherineD|2hogepodge: I think so16:28
markvoelkerhogepodge: I had a request to write up a "how to" for scoring anyway...perhaps I should incorporate this into that and put up something for review?16:28
hogepodgemarkvoelker: sure16:28
markvoelkerOk, easy enough.16:29
catherineD|2also with the new "test list" feature added to RefStack .. do we still need to keep the 201x.xx directoroes?16:29
markvoelker#action markvoelker Write up flag inspection in forthcoming Scoring Guide16:29
catherineD|2directories16:30
markvoelkercatherineDl2: hogepodge has an AI from above to remove them.=)16:30
catherineD|2ok16:30
*** sverma has quit IRC16:30
markvoelkeranything else on this topic?16:31
catherineD|2nope16:31
markvoelker#topic Regrouping an rescoring of Capabilities for 2016.0816:31
*** openstack changes topic to "Regrouping an rescoring of Capabilities for 2016.08 (Meeting topic: defcore)"16:31
markvoelkerDuring discussion in Austin, we noted that the way we group Capabilities is a little inconsistent today16:31
markvoelker(ok, a lot inconsistent)16:31
markvoelkerFor example: in some cases we have CRUD operations as a single thing, other places not.16:32
markvoelkerIt would be nice to clean those up and be more consistent.16:32
catherineD|2I think we need to have a few working sessions for regrouping then rescoring16:32
markvoelkercatherineDl2: probably16:32
*** abalutoiu has joined #openstack-meeting-316:33
markvoelkerThe general feeling in the room seemed to be (correct me if I'm mis-remembering) that generally grouping CRUD operations together was good16:33
catherineD|2may need to set criteria for regrouping16:33
markvoelkerBut there may be a few cases where it's not entirely feasible (those should generally be the exception though, not the rule)16:33
hogepodge+116:33
luzC+116:34
VanL-116:34
VanLThat was the problem that lead to the original splitting apart16:34
VanLWe had "Compute", with a bunch of random tests under it16:35
VanLThe issue was that this capability gave very little visibility into what that meant16:35
*** abalutoiu_ has quit IRC16:35
VanLThe entire genesis of the move from v1 of the json to v2 was to give more visibility into the capabilities16:36
*** mickeys has quit IRC16:36
markvoelkerVanL: right, in this case we're talking about CRUD on a single primitive.  So, for example: CRUD on routers is one capability.  CRUD on networks is one capability.  CRUD on subnets is one capability.16:36
*** qwebirc58042 has joined #openstack-meeting-316:36
VanLWe did that at first by just leveraging the names rather than looking at the tests16:36
markvoelkerNot: CRUD on all things compute-related is one capability.16:36
VanLI still think that capabilities should continue to be fine-grained16:37
*** qwebirc58042 has quit IRC16:37
*** vhoward has joined #openstack-meeting-316:37
VanLSHould there be cleanup on the tests? Sure, let's make sure the correspondence is there16:37
VanLBut we have been down this road, and it ended up being confusing16:38
gemaI think from the beginning that the capabilities should reflect API calls, not tests, but many operations are not CRUD16:38
markvoelkerVanL: it's a valid opinion. =)  The AI owners on this are hogepodge, dwalleck, and catherineDl2.  May I suggest that you work with them on an initial proposal and we'll take up the discussion in gerrit?16:38
VanLSure16:39
markvoelkerexcellent16:39
hogepodgeSo we have a choice of moving in two directions, more fine grained and more grouped. I propose that we send up a patch for both?16:39
*** flwang has quit IRC16:39
markvoelkerOk, anything further on this topic right now?16:39
hogepodgeIt would be nice to see how they compare.16:39
VanLhogepodge: The patches?16:40
markvoelkerhogepodge: sure, sounds reasonable.  I'll leave the mechanics to you guys.16:40
hogepodgeyes, to see the impact of grouping vs not grouping16:40
gemaVanL: I can help16:40
gemaVanL: I don't think grouping is the solution either16:40
VanLgema: Great16:41
*** mickeys has joined #openstack-meeting-316:41
*** toddjohn_ has joined #openstack-meeting-316:41
markvoelkerCool, sounds like you guys have a path forward. =)  I'll look forward to seeing some patches to review.16:41
markvoelker#topic Test Fixes16:42
*** openstack changes topic to "Test Fixes (Meeting topic: defcore)"16:42
markvoelkerIn the last scoring cycle we identified a few things that needed tests written or tests refactored16:42
markvoelkerI think I have most of the AI's on this one right now...16:42
markvoelkerNeutron and Glance don't have tests for GET / (version discovery) which is a Capability we've included for Nova and KEystone16:43
markvoelkerI spoke with both of those groups about this at the Summit, and wrote up a quick POC for Neutron on the flight now16:43
markvoelkers/now/home/16:43
markvoelkerIt's winding it's way through review and needs additional work, but it's progress.16:43
markvoelkerOnce that one settles out it should be trivial to do likewise for Glance16:43
markvoelkerWe also identified some tests that use admin credentials16:44
markvoelkerMostly these are for capabilities that are normally exposed to end users, so it's a test issue.16:44
markvoelkerI'm planning to work on the Neutron tests to see if we can refactor out the unnecessary admin credential usage16:44
*** toddjohn_ has quit IRC16:45
*** toddjohn_ has joined #openstack-meeting-316:45
hogepodgeI can take that AI, along with anyone else who might want to work on it.16:45
*** kzaitsev_mb has quit IRC16:45
markvoelkerI think we still need someone to work on the volume-v2-transfer and volume-v2-qos tests though (if refactoring is possible there)16:45
hogepodgeOr, we can work on it together.16:45
markvoelkerhogepodge: sure, I won't say no to help. =)16:45
catherineD|2so for the admin tests we do not want to remove or flag the tests until there are fixes ...  how do the users know that they fail these test because of admin credential .... just do not want to see them spend time in debugging things that we have identified.16:45
*** e0ne has quit IRC16:46
markvoelkerI think they have a common root problem though, so perhaps you want to attack the volumes stuff first?16:46
hogepodgemarkvoelker: this is where launchpad (a later item in the agenda) can help. We can create tickets with the basic information to reference back to16:46
markvoelkerhogepodge: ++16:46
hogepodgemarkvoelker: sure. If it's anything like the multi-tenant issue, it should be really easy to fix.16:46
markvoelkercatherineDl2: if there are admin tests in an existing Board-approved Guideline, I'm fine with flagging them16:46
hogepodgeprobably a subclass with a different client16:46
*** e0ne has joined #openstack-meeting-316:47
markvoelkerIn this case though, the Neutron tests at least are new entries for required status in next.json16:47
markvoelkerSo I'ld like to try to get those tests refactored before this goes up the Board for approval16:47
catherineD|2especially for the tests in https://review.openstack.org/#/c/299491/  .. .it took me a while to identify the failure causes16:47
*** kzaitsev_mb has joined #openstack-meeting-316:47
catherineD|2markvoelker: do we flag tests in the advisory section?16:47
catherineD|2or just remove?16:48
markvoelkercatherineDl2: if we think they can be refactored, I'd just flag them.  If we remove them then they'll have to go through a whole new advisory cycle which seems unnecessary if it's just a test issue16:48
*** e0ne has left #openstack-meeting-316:48
catherineD|2those are the tests in the advisory section in  2016.0116:48
hogepodgecatherineD|2: I think it's situation dependent.16:48
markvoelkerAnd when flagging them I'd note the Launchpad bug ID that says we're working on the refactor =)16:49
catherineD|2ok I will send a patch to flag them  in 2016.0116:49
markvoelkerhogepodge: right.  If we don't think the tests can reasonably be refactored, I'd be fine with dropping them.16:49
*** Swami_ has quit IRC16:49
markvoelkerOk, anything further here?16:50
markvoelker#topic Proposed 2.0 schema16:51
*** openstack changes topic to "Proposed 2.0 schema (Meeting topic: defcore)"16:51
markvoelker#link https://review.openstack.org/#/c/310621/16:51
markvoelkerI'm not sure if there's much to say about this one right now other than "please review and discuss in gerrit".  Anyone have stuff to discuss about it here in the meeting?16:51
* markvoelker is looking at the clock16:52
markvoelkerOk then:16:52
markvoelker#action everyone please review https://review.openstack.org/#/c/310621/16:53
markvoelker#topic Fill Out Issues In Launchpad16:53
*** openstack changes topic to "Fill Out Issues In Launchpad (Meeting topic: defcore)"16:53
markvoelkerI took an AI to start working on adding stuff to LP, which I intend to start sifting through this afternoon.16:53
catherineD|2Just one announcement ... RefStack IRC meeting is moving from Monday to Tuesday at the same time (19 UTC)16:53
markvoelkerI think the stuff we covered today is mostly a good start, but if I miss something then feel free to add it yourself16:54
markvoelker(or bug me)16:54
markvoelkercatherineDl2: duly noted, thanks!16:54
hogepodge(pun intended?)16:54
markvoelkerhogepodge: but of course =p16:54
markvoelkerI don't think I need any additional clarification on this AI, so move on?16:55
*** sdake has quit IRC16:55
*** ddieterly is now known as ddieterly[away]16:55
*** emagana has quit IRC16:55
markvoelker#topic Test Spec16:56
*** openstack changes topic to "Test Spec (Meeting topic: defcore)"16:56
markvoelkerThere was a bit of discussion in a couple of different sessions at the summit about some of what's in the etherpad for the test spec16:56
markvoelker(I think some additional notes have been added)16:56
gemashall we give it another week and then get a gerrit commit together?16:57
markvoelkerGenerally, I think we came to the conclusion that we have enough to shift this over to gerrit and start +1/-1 discussion of it so we can bring up the individual points of debate more clearly16:57
gemasounds good16:57
markvoelkergema: I'll leave the timeline up to you...I'm fine with waiting a week if you think there's more stuff to land in the pad yet. =)16:57
gemamarkvoelker: I may need a week to collect all the information and distill it16:58
markvoelkergema: no problem16:58
gemamarkvoelker: will get a commit in16:58
gemahogepodge: make sure all your thoughts are in there somewhere16:58
*** emagana has joined #openstack-meeting-316:58
hogepodge+116:58
markvoelkerTwo minute warning...anything else on this?16:59
markvoelker#topic Interop issues report16:59
*** openstack changes topic to "Interop issues report (Meeting topic: defcore)"16:59
*** flwang has joined #openstack-meeting-316:59
markvoelkerNothing much to say here other than: probably in the same boat.  REady to start moving to gerrit, and we have a little time so I'll probably concentrate on test-fixing and other AI's first16:59
markvoelkerBe sure to put your thoughts in the pad if you haven't already17:00
markvoelkerAnd we're out of time17:00
markvoelkerThanks folks!  Over to #openstack-defcore17:00
markvoelker#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Wed May  4 17:00:26 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-05-04-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-05-04-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-05-04-16.01.log.html17:00
VanLFor those still here: Elena Andromeda Sigler born at 11:00 am. 03May 2016. 6 lb 14 oz. 20.5 inches17:02
*** emagana has quit IRC17:03
*** ddieterly[away] is now known as ddieterly17:03
*** emagana has joined #openstack-meeting-317:04
*** vijendar has joined #openstack-meeting-317:05
*** lpetrut has joined #openstack-meeting-317:07
*** rtheis_ has joined #openstack-meeting-317:09
*** jmckind has quit IRC17:09
*** rtheis has quit IRC17:12
*** kzaitsev_mb has quit IRC17:12
*** Swami has joined #openstack-meeting-317:12
*** cjvolzka has left #openstack-meeting-317:12
*** salv-orlando has joined #openstack-meeting-317:12
*** toddjohn_ has quit IRC17:14
*** jed56 has quit IRC17:24
*** coolsvap has joined #openstack-meeting-317:25
*** tmazur has quit IRC17:26
*** ddieterly is now known as ddieterly[away]17:29
*** spzala has quit IRC17:30
*** spzala has joined #openstack-meeting-317:30
*** itxaka has quit IRC17:31
*** AlanClark has quit IRC17:31
*** spzala has quit IRC17:31
*** spzala has joined #openstack-meeting-317:32
*** toddjohn_ has joined #openstack-meeting-317:34
*** tonytan4ever has quit IRC17:34
*** Sukhdev has quit IRC17:42
*** pvaneck has joined #openstack-meeting-317:44
*** ivar-lazzaro has joined #openstack-meeting-317:45
*** tonytan4ever has joined #openstack-meeting-317:45
*** ivar-lazzaro has quit IRC17:46
*** TravT has joined #openstack-meeting-317:49
*** padkrish has joined #openstack-meeting-317:52
*** ivar-lazzaro has joined #openstack-meeting-317:56
*** emagana has quit IRC17:59
*** salv-orlando has quit IRC18:01
*** emagana has joined #openstack-meeting-318:02
*** sambetts is now known as sambetts|afk18:03
*** emagana has quit IRC18:07
*** mickeys has quit IRC18:11
*** mickeys has joined #openstack-meeting-318:12
*** mickeys has quit IRC18:12
*** mickeys has joined #openstack-meeting-318:12
*** SridarK has joined #openstack-meeting-318:13
*** shwetaap has joined #openstack-meeting-318:15
*** ivar-lazzaro has quit IRC18:20
*** badveli has joined #openstack-meeting-318:22
*** rstarmer has joined #openstack-meeting-318:23
*** kzaitsev_mb has joined #openstack-meeting-318:27
SridarKHi FWaaS folks18:30
padkrishhi sridar18:30
njohnstonhello18:30
*** nelsnels_ has joined #openstack-meeting-318:30
padkrishhello everyone18:30
chandancHello18:30
*** nelsnelson has quit IRC18:30
badvelihello all18:30
mfranc213hello18:30
*** emagana has joined #openstack-meeting-318:30
mfranc213it's nice to see everyone :)18:30
SridarKmfranc213: +118:31
SridarK#startmeeting Networking FWaaS18:31
openstackMeeting started Wed May  4 18:31:08 2016 UTC and is due to finish in 60 minutes.  The chair is SridarK. Information about MeetBot at http://wiki.debian.org/MeetBot.18:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:31
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:31
openstackThe meeting name has been set to 'networking_fwaas'18:31
SridarK#chair xgerman18:31
openstackCurrent chairs: SridarK xgerman18:31
*** adduarte has joined #openstack-meeting-318:31
mickeysHi18:31
xgermanHi18:32
njohnston#info According to the ical file from eavesdrop, we are actually in an even week, so today's meeting should be at 8pm, FYI.18:32
njohnstonI suggest we make normalizing the meeting schedule a topic for the meeting. :-)18:32
shwetaapHi18:32
SridarKnjohnston: sigh ok - since we are in an odd week18:32
SridarKmy bad18:32
xgermannjohnston +118:32
SridarKhence i sent the email out18:33
*** fitoduarte has quit IRC18:33
*** abalutoiu has quit IRC18:33
njohnstonI didn't look at my calendar until the last second.18:33
mfranc213yes, that was very helpful for me Sridar.18:33
SridarKnjohnston: ok lets do that as a topic18:33
SridarKnjohnston: apologies18:33
njohnstonNo, I think it's good, I would be at a family function at 8pm :-)18:33
SridarKserendipity :-)18:34
SridarK#topic Summit, v2 priorities18:34
*** openstack changes topic to "Summit, v2 priorities (Meeting topic: Networking FWaaS)"18:34
SridarKFirstly for the record - thanks all for the great discussion on Fri18:34
njohnston+118:35
chandanc+118:35
mfranc213+118:35
padkrish+118:35
SridarKwe can continue to use the etherpad18:35
SridarK#link https://etherpad.openstack.org/p/neutron-fwaas-austin18:35
*** toddjohn_ has quit IRC18:36
SridarKAre there any blocking issues that we need to discuss and work to resolution18:36
njohnstonThere is the issue I emailed out, the issue with oslo.service18:37
SridarKi spent some time with chandanc and Sarath o the gerrit workflow18:37
mfranc213yes, i looked at the oslo.service thing but not long enough to figure it out unfortunately.18:37
chandancThanks for the help with gerrit18:37
SridarKyes clearly there is an issue - i was able to see that as well - we can try to do some digging in parallel to see what is going on18:38
*** ddieterly[away] is now known as ddieterly18:38
*** jmckind has joined #openstack-meeting-318:38
njohnstonAnd if I hack in a fix for that, by adding an argument, then I get to a further issue where it looks like a multiple inheritance issue supplying parameters to an __init__() method18:38
mfranc213fwiw, the symptomology is simliar to this: http://freshfoo.com/blog/object__init__takes_no_parameters18:38
*** catherineD|2 has left #openstack-meeting-318:39
mfranc213and actually it appears that the initial bug, the one that nate put a hack into fix, is the same problem as what appears after the hack :)18:39
mfranc213that's how it appears to me, anyway.18:39
mfranc213this issue is deep in the weeds, as far as i can tell.  an interesting problem.18:40
njohnstonHere's what I am seeing on the __init__ issue: http://paste.openstack.org/show/496130/18:40
mfranc213(what nate has just posted is what is seen after the hack is put in place)18:40
njohnstonYes, the first line tries to explain that18:41
mfranc213ahh, yes, sorry nate18:41
njohnstonI'm not sure who to reach out to in order to see if we're using oslo.service incorrectly.  Perhaps dims?18:41
SridarKyes i am puzzled - i will dig more too18:42
xgermanjosh harlow - he is the oslo PTL18:42
*** sdake has joined #openstack-meeting-318:42
xgermanharlowja18:42
njohnstonExcellent.  I will put together a better presentation of the issue and contact him.  Thanks xgerman!18:42
xgermanyeah, tell him I send you :-)18:42
SridarK:-)18:43
*** jmckind has quit IRC18:43
njohnston:-)18:43
mfranc213one thing i wanted to do was to see how other callers handle that __init__ in oslo_service.  will try to get to that today.  think that reaching out to others is good, too.18:43
SridarKok lets continue on this18:43
SridarKmfranc213: my thought too - i am sure this is a common pattern18:43
mfranc213yeah, should be18:43
njohnstonOther than that I have gotten a start on accounting for all the db objects in the db patch, and trying to make sure that (other than the aforementioned problem) it passes tox.18:44
*** sdake has quit IRC18:44
xgermansorry, guys gotta run today early… should be better next week when I am back home...18:45
SridarKother than some methods related to rules, u will need to add for the other resources18:45
SridarKxgerman: no worries18:45
njohnstonSure, feel free to leave feedback on the PS18:45
*** sdake has joined #openstack-meeting-318:46
njohnstonthat's probably the best way to keep me honest on it :-)18:46
mfranc213there are orm questions that nate and i will be discussing also.18:46
SridarKwe can target some very basic sketchy plumbing with the extensions - db - plugin patches in abt 2 weeks18:46
mfranc213perfect18:46
SridarKdoes that seem reasonable ?18:46
mfranc213it does to me, yes18:46
mfranc213sorry, just speaking regarding the db piece18:47
SridarKmfranc213: yes no worries18:47
*** MarkAtwood has quit IRC18:47
SridarKjust drawing a line in the sand18:47
*** vijendar has left #openstack-meeting-318:47
*** padkrish has quit IRC18:48
njohnstonsounds good18:48
*** vgridnev has joined #openstack-meeting-318:48
mfranc213Sridark: one thing that would be very helpful for me at this stage is TODO item 1 on https://etherpad.openstack.org/p/neutron-fwaas-austin ??18:48
mfranc213not sure why i have ?? there.  pretend they're not there.18:48
*** padkrish has joined #openstack-meeting-318:48
SridarKok i will do that18:48
mfranc213thank you SridarK!18:48
SridarKPerhaps shwetaap can use the same model and resubmit a patchset for the extension18:49
SridarKsame approach as njohnston and mfranc213 for db patch18:50
*** bpokorny_ has joined #openstack-meeting-318:50
mfranc213SridarK: i'm sorry, can you say more about what you mean here?18:50
SridarKi think the ext patch does have most have the pieces in place18:50
mfranc213ah18:50
*** vishwanathj has joined #openstack-meeting-318:50
shwetaapsounds good .. i will do that18:51
*** bpokorny_ has quit IRC18:51
*** salv-orlando has joined #openstack-meeting-318:51
SridarKshwetaap: can u pls run thru the patch to see what could be missing and then either submit another patch or restart the old one18:51
*** bpokorny_ has joined #openstack-meeting-318:51
SridarKmfranc213: sorry - all i meant is if we want to resurrect the old patch or submit a new one as u guys did for db18:52
shwetaapsure will do18:52
SridarKeither is fine - leave it to the new owners18:52
mfranc213SridarK: ahh, i see.18:52
njohnstonshwetaap: When you do testing, just ignore py27 and py34, they will always fail until we get the oslo.service issue fixed.18:53
*** adduarte has quit IRC18:53
SridarKOn the agent piece - yushiro is back next week - perhaps then padkrish - u guys can sync as well18:54
*** bpokorny has quit IRC18:54
mfranc213once the oslo issue is fixed, we will want the team to know about it.  what is the best way to do that?  apologies if i've asked this already.  is it by email?18:54
*** adduarte has joined #openstack-meeting-318:54
shwetaapnjohnston: thanks will keep that in mind18:54
padkrish#sridark# sure, i will also sync up with german regarding the existing patch18:54
SridarKmfranc213: sure that will be easy18:54
mfranc213SridarK: ack18:54
SridarKmickeys: things u want to bring up on the iptables front ?18:55
*** toddjohn_ has joined #openstack-meeting-318:55
mickeysI have not made any progress. I need to start on the patch to add a common unwrapped chain.18:55
*** salv-orlando has quit IRC18:56
chandancI have been setting up the dev env , downloaded the current patch18:56
SridarKmickeys: ok18:56
*** salv-orlando has joined #openstack-meeting-318:56
SridarKchandanc: ok18:56
chandancwill ping mickey with questions18:56
SridarKchandanc: if u need to sync with mickeys while in the same time zone18:57
SridarKother things regarding v2 that anyone wants to bring up ?18:58
chandancsure sridark, may be by tomorrow i will have a better view18:58
SridarKchandanc: ok perfect18:58
njohnstonnothing else to bring up, but I feel like we have gotten a decent start.18:58
mfranc213+118:58
SridarK+118:58
njohnstononce we have the oslo.service issue figured out we should probably put that fix out in a separate patch so we can fast-track merging it18:59
mfranc213+118:59
SridarKnjohnston: yes - pls add xgerman and me to the review - in case we miss it18:59
njohnstonI've also started looking at all the neutron-lib deprecations, that looks like it will probably not be difficult to fix.18:59
njohnstonSridarK: Will do.18:59
mickeysRegarding 264488, I still feel that position does not belong in rule. We wanted to be able to reference a rule from multiple different policies. IMO this should be abandoned.19:00
SridarKnjohnston: yes we can prioritize as we see fit once we get some traction on the v2 patches19:01
SridarKmickeys: yes agreed19:02
*** emagana has quit IRC19:02
njohnstonmickeys: From a DB schema perspective, 'position' is a field in the firewall_policy_rule_associations table, so it is an attribute per association, not globally for the rule.19:02
njohnstonAt least, that is what the spec laid out, so that's what I am working towards for the DB19:02
SridarKnjohnston: having it in the association table enables the reuse19:03
SridarKso yes19:03
mickeysnjohnston: The proposed change is in the REST API section. It should remain in the DB association table.19:03
chandancyes19:03
SridarKok lets move on19:05
njohnstonBut according to that change 'position' only indicates the position within the associated policy, making it a policy-specific bit of data for that rule.19:05
SridarK#topic other reviews19:05
*** openstack changes topic to "other reviews (Meeting topic: Networking FWaaS)"19:05
njohnstonOK, leaving that for later19:06
chandancshould the rule position not be part of the policy API ?19:06
chandancsure, lets move on19:06
SridarKok lets pick it up in open discussion19:06
SridarKwe have the observer hierarchy patch out19:07
SridarK#link https://review.openstack.org/#/c/278863/19:07
*** salv-orlando has quit IRC19:07
SridarKthis is also plagued by the UT issue19:07
SridarKi think the patch does what is intended - i am trying to test this as well19:08
SridarKi have been talking to the submitter - he going thru some testing and possibly add some more on the UT19:08
SridarKrequest folks to get some eyes on this as well19:08
*** salv-orlando has joined #openstack-meeting-319:08
mfranc213i will take a look19:09
SridarKwith this in - will enable us to remove some fwaas stuff from L3Agent19:09
SridarKthx19:09
njohnston+1 for removing fwaas stuff from L3Agent19:09
SridarKany other reviews that folks want to bring up ?19:09
*** piet has joined #openstack-meeting-319:10
*** rockyg has joined #openstack-meeting-319:10
SridarKbadveli: could u pls also take a look19:10
SridarKok lets move on19:11
SridarK#topic FWaaS weekly meeting time19:12
*** openstack changes topic to "FWaaS weekly meeting time (Meeting topic: Networking FWaaS)"19:12
badveliyes19:12
badveli i will take a look sridhark19:12
njohnstonI think there was consensus for a single meeting time19:12
mfranc213+119:12
SridarKi realize with some new contributors from the India and Japan we will struggle to find a time that works fantastically for all19:13
*** salv-orlando has quit IRC19:13
SridarKi am fine with the single time too - will certainly avoid a snafu like today :-)19:13
SridarKpossible lets throw some times out over email - so we ensure that active contributors are able to find some common ground19:14
chandanc+119:14
njohnstonThe best guess I can come up with is 9:00am EST == 10:00pm in Japan, 6:30pm in New Delhi19:15
njohnstonBut I shall be as flexible as I can. :-)19:15
chandancWe can consider the discussion we had during summit19:15
mfranc213= 6 am PST19:16
SridarKi start my day early - so i can make that work - but 6am Pacific could abe a challenge for some19:16
SridarKyushiro is out this week - so lets start the discussion first thing next week19:16
njohnstonSounds good.19:17
*** tonytan4ever has quit IRC19:17
mfranc213so the delta between earliest and latest is, ignoring daylight savings, 8 hours.19:17
mickeysThat is two hours earlier than I normally wake up19:17
chandancsure, better to propose in mail thread, 6:30 pm India is mostly way back from Office. Can we push by 30 mins19:17
mfranc213if we push pacific time up, japan suffers...19:17
mickeysI thought night time US, morning India and Japan might work better19:17
SridarKlets see what is upper boundary for yushiro19:18
*** emagana has joined #openstack-meeting-319:18
SridarKand if we do evening what is the upper boundary for Eastern time zone19:18
SridarKso we can do this over email19:18
mickeysWhen DST ends, it becomes one hour earlier19:18
mickeysin the US19:18
chandancsure19:18
mfranc213i think 11-ish ?19:18
njohnstonmidnight EST == 1:00pm tokyo == 9:30am new delhi == 9:00pm san jose19:19
mfranc213speaking just for myself.19:19
njohnstonI would be fine with midnight19:19
SridarKok may be we have a formula there which we can tweak so it is not too late for Eastern and make it work for all19:20
njohnstonI am also happy to have the opportunity to provide for our esteemed colleagues in Asia the flexibility they have so often given us.19:20
*** ivar-lazzaro has joined #openstack-meeting-319:20
mfranc213yes, perhaps something like 10:30 pm EST == 11:30am tokyo == 8am new delhi == 7:30pm san jose19:21
mfranc213i will be flexible too.  +1 for what njohnston just said19:21
SridarKok good - lets take it to email then first thing next week19:22
njohnston+119:22
chandanc+119:22
SridarK#topic Open Discussion19:22
*** openstack changes topic to "Open Discussion (Meeting topic: Networking FWaaS)"19:22
mickeysRegarding 264488, the API rules table is not in the context of a policy. The DB association table is in the context of a policy, so position there makes sense and is a good thing. In the API, the position is specified through the ordered list of rules in the policy table.19:22
njohnstonLooking forward: I am somewhat unfamiliar with how all this code works in practice; is there anything that is a pre-requisite for our testing fwaas in the lab to make sure the code hangs together, once we get to that point?19:23
SridarKnjohnston: something as basic as a single node devstack env is good19:24
mfranc213mickeys: would you be able to add your suggestions and concerns as comments to https://review.openstack.org/#/c/264488/ itself?19:24
njohnstonSridarK: Very good.  I know we had to be much more involved when working on QoS DSCP because we weren't satisfied until we had tcpdumps showing the traffic was behaving as configured.19:25
SridarKi have been using that to test out what ever we have albeit with some hacks19:25
*** sdake has quit IRC19:25
*** ivar-lazzaro has quit IRC19:25
mfranc213SridarK: do you generally pull from master for all other OS components?19:25
SridarKi usually have a rule with an obscure port number - so i can quickly grep for that on the iptables to see if it made it all the way19:25
*** sdake has joined #openstack-meeting-319:26
SridarKmfranc213: yes19:26
mfranc213ack19:26
chandancmickey: agree, with the ordered list of rule in policy we should already have the position. right ?19:26
njohnstonSridarK: Is the devstack directives necessary to set up fwaas documented?  Could you share your local.conf with us?19:26
SridarKnjohnston: ok surely will do that19:26
SridarKq-fwaas - will set up the service plugin19:27
mickeysmfranc213: I have put comments in 264488 in the past, for example Jan 15 8:19am comment19:27
mfranc213mickeys: thank you.19:27
padkrishjust q-fwaas and ofcourse l3-agent in local.conf is all that's needed, i guess19:27
mfranc213mickeys: do you feel your comments in the PS are exhaustive?19:27
SridarKpadkrish: yes19:27
mickeysmfranc213: Do you think I should add another comment expanding on this, along the lines of the comments I made above?19:28
njohnstonpadkrish and SridarK: does it matter at all what ML2 driver is in use?19:28
SridarK2 min warning19:28
mfranc213mickeys: i think that would help me, yes.19:28
SridarKnjohnston: it should not19:29
padkrishnjohnston# good question, my default settings are always ovs as ML2 driver19:29
njohnstonSridarK: Excellent.  That is what I thought, but I am checking my assumptions.19:29
SridarKnjohnston: do u use linux bridge ?19:29
*** mbound has joined #openstack-meeting-319:29
njohnstonSridarK: I typically use OVS but I have had trouble in func tests where both OVS and LB were tested scenarios.19:29
SridarK+1 to padkrish - i use ovs usually too19:29
*** salv-orlando has joined #openstack-meeting-319:30
SridarKnjohnston: ok19:30
SridarKok folks times up19:30
mfranc213two things: 1) i've been adding TODOs to https://etherpad.openstack.org/p/neutron-fwaas-austin19:30
SridarKthanks all19:30
mfranc213, and 2) is there anyone else here who is having difficulty editing https://wiki.openstack.org/wiki/Neutron/FWaaS/NewtonPlan (as i am)?19:30
njohnstonthanks all!  good meeting!19:30
mickeysThere is a bit of additional code in iptables when using OVS, but it should not make a significant difference. I never did figure out how conntrack zones are assigned in case of LB, should probably get back to that.19:30
padkrishthanks19:30
SridarKmfranc213: lets pick it up later19:30
mfranc213thank you19:30
mfranc213bye all19:30
SridarK#endmeeting19:30
badvelibye all19:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:31
openstackMeeting ended Wed May  4 19:30:59 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2016/networking_fwaas.2016-05-04-18.31.html19:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2016/networking_fwaas.2016-05-04-18.31.txt19:31
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2016/networking_fwaas.2016-05-04-18.31.log.html19:31
*** vhoward has quit IRC19:36
*** mickeys has quit IRC19:38
*** tonytan4ever has joined #openstack-meeting-319:38
*** badveli has quit IRC19:39
*** baoli_ has quit IRC19:39
*** mickeys has joined #openstack-meeting-319:39
*** geseib has quit IRC19:39
*** geseib has joined #openstack-meeting-319:39
*** SridarK has quit IRC19:39
*** ddieterly is now known as ddieterly[away]19:40
*** rossella_s has quit IRC19:40
*** rossella_s has joined #openstack-meeting-319:41
*** padkrish has quit IRC19:41
*** TravT has quit IRC19:42
*** pkarikh_ has joined #openstack-meeting-319:43
*** mickeys has quit IRC19:43
*** piet has quit IRC19:44
*** kzaitsev_mb has quit IRC19:45
*** mkovacik has quit IRC19:46
*** piet has joined #openstack-meeting-319:49
*** emagana has quit IRC19:54
*** chandanc has quit IRC19:56
*** emagana has joined #openstack-meeting-319:56
*** iyamahat has quit IRC19:57
*** yamahata has quit IRC19:58
*** tyr_ has joined #openstack-meeting-319:58
*** hurgleburgler has joined #openstack-meeting-320:00
*** salv-orlando has quit IRC20:00
*** robcresswell has joined #openstack-meeting-320:00
*** TravT has joined #openstack-meeting-320:01
robcresswell#startmeeting horizondrivers20:01
openstackMeeting started Wed May  4 20:01:09 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
hurgleburgler(◠‿◠✿)ノ20:01
*** openstack changes topic to " (Meeting topic: horizondrivers)"20:01
openstackThe meeting name has been set to 'horizondrivers'20:01
david-lyleo/20:01
pkarikh_hi!20:01
bpokorny_o/20:01
TravTo20:01
*** emagana has quit IRC20:01
tyr_o/20:01
*** emagana has joined #openstack-meeting-320:02
robcresswellHi everyone20:02
robcresswellThere's a couple things to discuss before looking at blueprints20:02
robcresswell#topic Notices20:02
*** openstack changes topic to "Notices (Meeting topic: horizondrivers)"20:02
*** toddjohn_ has quit IRC20:03
*** ddieterly[away] is now known as ddieterly20:03
robcresswellI'm planning the midcycle with some Cisco folk, will send out a list of potential dates this week. If anyone else would also like to volunteer to host, let me know.20:03
robcresswellOptions are always good :)20:03
TravTwe can always host in fort collins.20:03
TravTjust as an option20:04
david-lyleI can do Santa Clara or Hillsboro20:04
david-lyle*can offer20:04
robcresswellha, I read that as "I will only go to these two locations"20:05
robcresswellGreat, thanks. Will add that to the email.20:05
david-lyleif I'm not hosting, I'm not coming :P20:05
hurgleburglerLOL20:05
robcresswellSo for those who missed the summit, the etherpads are here:20:05
robcresswell#link https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#Horizon20:05
robcresswellThe priorities and feedback ones are especially import IMO.20:05
robcresswellI'd recommend reading through the notes.20:06
robcresswellI've also brought back the weekly bug report idea and linked it in the Horizon IRC room topic20:06
robcresswell#link https://wiki.openstack.org/wiki/Horizon/WeeklyBugReport20:07
*** sdague has quit IRC20:07
*** bpokorny_ has quit IRC20:07
robcresswellIf you only get time to do a handful of reviews each week, pick up those patches first so we can move quickly on them.20:07
*** bpokorny has joined #openstack-meeting-320:07
robcresswellAnyone can add to it, and I'll be curating it too so it doesnt turn into Launchpad No.220:07
robcresswellre: launchpad, a lot of bugs have relevant tags now, such as a service name, or a particular focus like ux or angular.20:08
robcresswellSo if you have some particular knowledge that will help you filter better :)20:08
*** piet has quit IRC20:08
TravTyes, those tags are helpful20:09
TravTi looked through the angular ones yesterday.20:09
TravTfound one with a review up and reviewed it20:09
robcresswellSounds good20:09
robcresswell#topic Earlier feature freeze20:10
*** openstack changes topic to "Earlier feature freeze (Meeting topic: horizondrivers)"20:10
robcresswell#link http://lists.openstack.org/pipermail/openstack-dev/2016-April/093525.html20:10
*** rhochmuth has quit IRC20:10
robcresswellThe chain seems to have got lost, but that email and the first reply are the ones with the majority of the discussion anyway.20:10
robcresswellIt's been a fairly common theme that we're making too many breaking changes too late, and given the growing plugin architecture we should consider FF a week earlier.20:11
*** salv-orlando has joined #openstack-meeting-320:11
robcresswellThis would likely be R-6 instead of R-5, just to give others a week to fix things.20:12
TravTso, frameworky things vs core services in horizon may need to be treated differently20:12
robcresswellYeah, the main discussion is how we want to scope this20:12
*** toddjohn_ has joined #openstack-meeting-320:12
robcresswellWe could restrict horizon/ for example20:12
TravTe.g. cinder panel vs reusable widget20:13
robcresswellYep20:13
robcresswellLong term we may pursue a more official split repo, but its not a priority for now.20:13
robcresswellThoughts/20:14
robcresswell?*20:14
*** sdague has joined #openstack-meeting-320:14
david-lylere: FF or scope of the FF?20:14
david-lyleFF: good20:15
david-lyleFF scope: broad20:15
david-lyleif we want core things in late, let's make explicit exceptions20:16
robcresswellMy internet gave up for a moment there.20:17
TravTwell, we got it all figured out.20:17
TravTso what's next?20:17
*** toddjoh__ has joined #openstack-meeting-320:17
TravT;)20:17
*** toddjohn_ has quit IRC20:18
david-lylerobcresswell: is your modem plugged in?20:19
*** r1chardj0n3s has joined #openstack-meeting-320:19
robcresswellRight, I caught up20:19
*** iyamahat has joined #openstack-meeting-320:20
robcresswelldavid-lyle: "broad" meaning you'd like to FF on horizon and o_d?20:20
david-lyleyes20:21
david-lylethere is an exception process20:21
david-lylelet's use it20:21
david-lyleif necessary20:21
robcresswellYep20:21
robcresswellThere are not a lot of opinions in this room today. Guess everyone used them all up at the summit :)20:22
robcresswell#topic Blueprint review20:22
r1chardj0n3so/20:22
*** openstack changes topic to "Blueprint review (Meeting topic: horizondrivers)"20:22
*** cbouch has quit IRC20:22
TravTrobcresswell: if you want to move FFE process up a week, I'm okay with that20:22
robcresswellYeah, lets do it. Should help the plugins.20:23
hurgleburgleryeah, me too20:23
robcresswellon to blueprints.20:23
david-lylerobcresswell: it will make your life easier lining up with global expectations20:23
robcresswellThis was carried over from the previous meeting:20:23
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/hierarchical-projects20:23
r1chardj0n3sare heirarchical projects still a thing?20:24
david-lyler1chardj0n3s: yes and no20:24
david-lyleyes in keystone, no beyond20:25
david-lyleno quota support20:25
r1chardj0n3sright :-)20:25
robcresswellIt looks like kenji was trying to resurrect it20:25
david-lylemy previous stance was to wait for someone, anyone else to support it first20:25
david-lyleit's a UX quagmire20:26
TravTevery time i got pulled into those discussions, i left confused20:27
*** fawadkhaliq has joined #openstack-meeting-320:27
david-lylethe role inheritance alone will make you want to run20:27
robcresswellYeah I'm just scanning the linked blueprints20:27
david-lyleI honest hoped the thing would die20:27
robcresswellhaha20:27
robcresswellI don't see any reason to actively block it, but it doesn't seem like there's a big need for it.20:28
*** banix has quit IRC20:28
david-lyleand with quota completely blocked it my be asphyxiated yet20:28
*** toddjoh__ has quit IRC20:28
robcresswellWhat was the issue there?20:28
david-lylethe changes to certain views will be considerable20:28
robcresswellWell, I'm adequately scared.20:29
david-lylethe issue was things move slowly, quota can't be updated to support hierarchies because existing quota is flawed, adding more complexity to something already broken won't fix it20:30
david-lyleso quota was to be fixed first then hierarchy20:30
TravTrobcresswell: my confusion was probably more of a lack of ability to really focus on it.  so don't be scared just by my statements.20:30
robcresswellGotcha. I wasn't aware of the quota - hierarchy link.20:30
robcresswellTravT: Ha, I was just amused by two people immediately reacting with "oh no"20:31
david-lyleall identity views get really complicated20:31
david-lyleproject selection gets complicated20:31
david-lylehierarchy navigation isn't even a thing yet20:31
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/hierarchical-projects Left blocked, comments inline20:31
*** toddjohn_ has joined #openstack-meeting-320:32
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/angular-registry20:32
robcresswellSo this has been properly split into its own blueprint20:33
*** tonytan4ever has quit IRC20:33
robcresswellWe've already talked about moving forward with it, but wanted to highlight that it now has its own content20:33
robcresswellRather than the ever-growing angular-images bp :)20:33
r1chardj0n3s\o/ for the split20:34
TravTi think much of the content there could be pulled over into a documentation patch as well.20:34
r1chardj0n3snice idea20:34
robcresswellThat'd be good20:35
*** salv-orlando has quit IRC20:35
robcresswellDoes anyone have any blueprints they'd like to raise? Otherwise I'll just start picking from the pile.20:35
*** shwetaap has quit IRC20:36
*** shwetaap has joined #openstack-meeting-320:37
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/automated-test-coverage-reports20:37
robcresswellWe already have coverage running, so we can remove this afaik.20:37
*** toddjoh__ has joined #openstack-meeting-320:38
david-lyleyeah remove20:38
*** toddjohn_ has quit IRC20:38
*** yamahata has joined #openstack-meeting-320:38
*** toddjohn_ has joined #openstack-meeting-320:39
robcresswellStruggling to find many new blueprints, so we can end the meeting early if there are no more to add.20:40
robcresswell#endmeeting20:41
david-lyleis this superseeded https://blueprints.launchpad.net/horizon/+spec/volumes-selenium?20:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:41
openstackMeeting ended Wed May  4 20:41:46 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-05-04-20.01.html20:41
robcresswellThanks all20:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-05-04-20.01.txt20:41
openstackLog:            http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-05-04-20.01.log.html20:41
*** r1chardj0n3s has left #openstack-meeting-320:42
*** TravT has left #openstack-meeting-320:42
*** pkarikh_ has quit IRC20:42
*** robcresswell has left #openstack-meeting-320:42
*** toddjoh__ has quit IRC20:43
*** hurgleburgler has left #openstack-meeting-320:43
*** toddjohn_ has quit IRC20:44
*** salv-orlando has joined #openstack-meeting-320:44
*** ivar-lazzaro has joined #openstack-meeting-320:46
*** fawadk has joined #openstack-meeting-320:47
*** bpokorny has quit IRC20:47
*** doug-fis_ has joined #openstack-meeting-320:48
*** fawadkhaliq has quit IRC20:50
*** doug-fish has quit IRC20:50
*** ivar-lazzaro has quit IRC20:50
*** doug-fish has joined #openstack-meeting-320:51
*** Sukhdev has joined #openstack-meeting-320:52
*** doug-fi__ has joined #openstack-meeting-320:52
*** doug-fis_ has quit IRC20:52
*** Sukhdev has quit IRC20:54
*** doug-fish has quit IRC20:55
*** auggy has joined #openstack-meeting-320:56
*** jaypipes has quit IRC20:56
*** doug-fi__ has quit IRC20:57
*** toddjohn_ has joined #openstack-meeting-320:57
*** alaski has joined #openstack-meeting-320:58
*** ctrath has joined #openstack-meeting-320:58
*** ccarmack has joined #openstack-meeting-320:59
*** mriedem has joined #openstack-meeting-320:59
*** julim has quit IRC20:59
alaski#startmeeting nova_cells21:00
openstackMeeting started Wed May  4 21:00:06 2016 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
bauzasgo go go21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: nova_cells)"21:00
openstackThe meeting name has been set to 'nova_cells'21:00
melwitto/21:00
bauzas\o21:00
mriedemo/21:00
ccarmackhi21:00
*** rlrossit has joined #openstack-meeting-321:00
dansmith*/21:00
dansmith^ head in a fog, but waving21:00
doffmo/21:00
rlrossito/21:00
ctratho/21:00
alaskiI haven't had time to think about a proper agenda yet so we'll speed through21:00
dansmithgood man21:00
bauzas<321:00
alaski#topic Open Reviews21:01
*** openstack changes topic to "Open Reviews (Meeting topic: nova_cells)"21:01
alaskihttps://etherpad.openstack.org/p/newton-nova-priorities-tracking21:01
alaskitake a peek, review a patch21:01
*** julim has joined #openstack-meeting-321:01
alaski#topic Open Discussion21:01
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"21:01
dansmithwoot21:01
dansmithI'm working through the keypairs -> API DB patches right now21:01
doffmI need to update the nova priorities etherpad. There is a new keypairs spec, and the miscellaneous is gone.21:01
alaskiokay21:02
alaskiI was going to ask if there are more specs planned, I assumed yes21:02
bauzascell0 patches seem in a good shape21:02
doffmI also need to write an instance groups spec, but haven't started.21:02
ccarmackI was going to start on quotas, but I gather the spec is obsolete ;-)21:02
melwittI'm to leave the mq patch as-is, right? i.e. we're deciding on the get_cell_client lookup CellMapping thing later?21:02
alaskimelwitt: yeah, let's merge what's there and then update21:02
alaskiIMO21:02
doffmccarmack: Well, its not obsolte, but yes. Need to update with stuff we talked about at summit.21:02
melwittmriedem suggested a spec might be needed for the oslo.messaging "make a transport url" function. so I can write that21:03
*** TravT has joined #openstack-meeting-321:03
ccarmackdoffm: anyway, I can start on the the implementation21:03
*** njohnsto_ has joined #openstack-meeting-321:03
alaskimelwitt: cool21:04
mriedemi'm woefully behind on reviewing any cells v2 things21:04
mriedemi don't know if an oslo spec is needed or not21:04
alaskidoffm: are any of the specs not in need of updates, i.e. ready for review?21:04
doffmUmmm, aggregates got pushed this morning.21:04
doffmhttps://review.openstack.org/#/c/288084/21:04
alaskiokay21:04
alaskijust marked it on the etherpad to distinguish from those needing updates from summit discussions21:05
melwittmriedem: I'll ask in the oslo channel if a spec is wanted21:05
doffmKeypairs is new this morning. https://review.openstack.org/#/c/312619/ No reviews yet.21:05
mriedemi'll try to get back on those this week21:06
mriedemaggregates and keypairs21:06
alaskiI plan to look tomorrow21:06
mriedemby try i mean, doffm is free to bug me to review them incessantly21:06
alaskiI'm really trying to get oslo.policy stuff in order by the end of the week to get fully back to cells next week21:07
bauzasI have a long week-end but I should be up for reviews next week21:07
*** mickeys has joined #openstack-meeting-321:07
alaskiit sounds like there's enough work to go around for the moment. I will try to be more organized for next weeks meeting.21:08
alaskianything else to touch on today?21:08
rlrossitwhat's the status of melwitt's MQ patch?21:08
rlrossithave we bikeshedded on that enough?21:08
melwittthe spec needs to be approved first, post summit21:09
*** mickeys_ has joined #openstack-meeting-321:09
alaskiI would like to merge as is, but yeah need the spec first21:09
rlrossitmissed that. But yeah I'm fine with it as-is21:09
*** banix has joined #openstack-meeting-321:10
alaskicool21:10
*** lblanchard has quit IRC21:11
alaskiunless there's last second dissent that's it for this week21:11
rlrossitmriedem: https://review.openstack.org/#/c/298551/21:11
alaskieverybody can get back to being jetlagged or going on vacation21:11
bauzas\o/21:11
mriedemtoo many gd specs21:11
alaskimriedem: yep :) they're all in the etherpad though21:11
ctrathhttp://grammarist.com/usage/shedded/21:11
alaskithanks all!21:11
alaski#endmeeting21:11
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:11
openstackMeeting ended Wed May  4 21:11:58 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:11
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-05-04-21.00.html21:12
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-05-04-21.00.txt21:12
*** mriedem has left #openstack-meeting-321:12
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-05-04-21.00.log.html21:12
*** TravT has left #openstack-meeting-321:12
*** ddieterly is now known as ddieterly[away]21:12
*** rlrossit has left #openstack-meeting-321:12
*** ccarmack has left #openstack-meeting-321:12
*** ctrath has left #openstack-meeting-321:12
*** mickeys has quit IRC21:12
*** mbound has quit IRC21:13
*** ddieterly[away] is now known as ddieterly21:14
*** auggy has left #openstack-meeting-321:14
*** neiljerram has quit IRC21:18
*** Sukhdev has joined #openstack-meeting-321:19
*** tyr_ has quit IRC21:21
*** piet has joined #openstack-meeting-321:21
*** bpokorny has joined #openstack-meeting-321:22
*** rstarmer has quit IRC21:23
*** toddjohn_ has quit IRC21:24
*** ddieterly is now known as ddieterly[away]21:27
*** rtheis_ has quit IRC21:28
*** toddjohn_ has joined #openstack-meeting-321:32
*** toddjohn_ has quit IRC21:33
*** alaski has left #openstack-meeting-321:35
*** vgridnev has quit IRC21:40
*** bauzas is now known as bauzas_off21:50
*** ddieterly[away] is now known as ddieterly21:50
*** sdague has quit IRC21:51
*** Sukhdev has quit IRC21:52
*** Sukhdev has joined #openstack-meeting-321:52
*** rockyg has quit IRC21:56
*** mageshgv has quit IRC21:57
* tellesnobrega is away: I'm busy21:57
*** njohnsto_ has quit IRC21:58
*** Sukhdev has quit IRC22:04
*** rockyg has joined #openstack-meeting-322:04
*** julim has quit IRC22:06
*** ddieterly is now known as ddieterly[away]22:07
*** vishwanathj has quit IRC22:10
*** mickeys_ has quit IRC22:12
*** mickeys has joined #openstack-meeting-322:13
*** ccamacho|away has quit IRC22:13
*** mickeys has quit IRC22:14
*** mickeys has joined #openstack-meeting-322:15
*** absubram has quit IRC22:15
*** ccamacho has joined #openstack-meeting-322:15
*** dimtruck is now known as zz_dimtruck22:19
*** sigmavirus24 is now known as sigmavirus24_awa22:21
*** baoli has joined #openstack-meeting-322:24
*** baoli_ has joined #openstack-meeting-322:25
*** shwetaap has quit IRC22:25
*** piet has quit IRC22:28
*** baoli has quit IRC22:29
*** iyamahat has quit IRC22:31
*** toddjohn_ has joined #openstack-meeting-322:33
*** ddieterly[away] is now known as ddieterly22:34
*** ddieterly has quit IRC22:35
*** lpetrut has quit IRC22:36
*** toddjohn_ has quit IRC22:46
*** mbound has joined #openstack-meeting-322:46
*** adduarte has quit IRC22:53
*** adduarte has joined #openstack-meeting-322:54
*** banix has quit IRC22:54
*** toddjohn_ has joined #openstack-meeting-323:00
*** iyamahat has joined #openstack-meeting-323:01
*** rbak has quit IRC23:02
*** baoli_ has quit IRC23:05
*** baoli has joined #openstack-meeting-323:08
*** ddieterly has joined #openstack-meeting-323:10
*** Sukhdev has joined #openstack-meeting-323:13
*** banix has joined #openstack-meeting-323:15
*** bapalm_ has quit IRC23:30
*** tellesnobrega is now known as tellesnobrega_af23:35
*** toddjohn_ has quit IRC23:36
*** sdake has quit IRC23:37
*** salv-orlando has quit IRC23:39
*** ddieterly is now known as ddieterly[away]23:40
*** ddieterly[away] is now known as ddieterly23:42
*** banix has quit IRC23:44
*** Swami has quit IRC23:47
*** piet has joined #openstack-meeting-323:48
*** mbound has quit IRC23:48
*** fawadkhaliq has joined #openstack-meeting-323:50
*** amit213 has joined #openstack-meeting-323:51
*** fawadk has quit IRC23:52
*** bpokorny has quit IRC23:58

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