Wednesday, 2016-04-06

*** toddjohn has quit IRC00:00
*** zz_dimtruck is now known as dimtruck00:01
*** marg7175 has joined #openstack-meeting-300:10
*** tqtran has quit IRC00:13
*** ddieterly has joined #openstack-meeting-300:16
*** stanchan has joined #openstack-meeting-300:17
*** yamamoto_ has quit IRC00:18
*** rbak has joined #openstack-meeting-300:25
*** mtanino has quit IRC00:25
*** rbak has quit IRC00:28
*** yamamot__ has joined #openstack-meeting-300:31
*** sdake has joined #openstack-meeting-300:32
*** sdake_ has quit IRC00:34
*** Sukhdev has quit IRC00:35
*** yamamot__ has quit IRC00:35
*** dimtruck is now known as zz_dimtruck00:43
*** zz_dimtruck is now known as dimtruck00:49
*** sdake_ has joined #openstack-meeting-300:51
*** sdake has quit IRC00:51
*** baoli has joined #openstack-meeting-300:52
*** alexpilotti has joined #openstack-meeting-300:56
*** yamamoto has joined #openstack-meeting-301:00
*** alexpilotti has quit IRC01:01
*** rossella_s has quit IRC01:03
*** kzaitsev_mb has joined #openstack-meeting-301:03
*** rossella_s has joined #openstack-meeting-301:03
*** alexpilotti has joined #openstack-meeting-301:04
*** yamamoto has quit IRC01:05
*** zhurong has joined #openstack-meeting-301:06
*** neelashah has joined #openstack-meeting-301:08
*** stanzgy has joined #openstack-meeting-301:08
*** alexpilotti has quit IRC01:09
*** neelashah has quit IRC01:09
*** amotoki has joined #openstack-meeting-301:13
*** amotoki_ has joined #openstack-meeting-301:15
*** yamahata has joined #openstack-meeting-301:15
*** kzaitsev_mb has quit IRC01:16
*** pvaneck has quit IRC01:17
*** Swami has quit IRC01:17
*** amotoki has quit IRC01:18
*** kenji-i has joined #openstack-meeting-301:19
*** baojg has joined #openstack-meeting-301:19
*** bpokorny_ has joined #openstack-meeting-301:20
*** bpokorny has quit IRC01:23
*** bpokorny_ has quit IRC01:24
*** salv-orlando has joined #openstack-meeting-301:32
*** Adri2000_ has quit IRC01:34
*** baojg has quit IRC01:40
*** hoangcx has quit IRC01:46
*** yamamot__ has joined #openstack-meeting-301:46
*** hoangcx has joined #openstack-meeting-301:46
*** Adri2000 has joined #openstack-meeting-301:46
*** marg7175 has quit IRC01:47
*** woodster_ has quit IRC01:47
*** salv-orlando has quit IRC01:47
*** yamamot__ has quit IRC01:51
*** tfukushima has joined #openstack-meeting-301:54
*** sdake has joined #openstack-meeting-301:55
*** hoangcx has left #openstack-meeting-301:56
*** sdake_ has quit IRC01:56
*** JieLi has joined #openstack-meeting-301:56
*** s3wong has quit IRC01:58
*** ddieterly is now known as ddieterly[away]02:15
*** ddieterly[away] is now known as ddieterly02:15
*** ddieterly is now known as ddieterly[away]02:19
*** iyamahat has joined #openstack-meeting-302:21
*** amotoki_ is now known as amotoki02:28
*** marg7175 has joined #openstack-meeting-302:29
*** dimtruck is now known as zz_dimtruck02:29
*** yamamoto has joined #openstack-meeting-302:31
*** banix has joined #openstack-meeting-302:33
*** yamamoto has quit IRC02:35
*** tobe has joined #openstack-meeting-302:42
*** tobe has quit IRC02:42
*** ccamacho has quit IRC02:47
*** ccamacho has joined #openstack-meeting-302:47
*** sdake_ has joined #openstack-meeting-303:01
*** salv-orlando has joined #openstack-meeting-303:03
*** sdake has quit IRC03:04
*** stanchan has quit IRC03:06
*** marg7175 has quit IRC03:08
*** hoangcx has joined #openstack-meeting-303:11
*** hoangcx has left #openstack-meeting-303:12
*** lblanchard has joined #openstack-meeting-303:13
*** salv-orlando has quit IRC03:13
*** JieLi has quit IRC03:14
*** yamamot__ has joined #openstack-meeting-303:16
*** lblanchard has quit IRC03:17
*** ddieterly[away] has quit IRC03:19
*** amotoki has quit IRC03:20
*** yamamot__ has quit IRC03:21
*** JieLi has joined #openstack-meeting-303:26
*** markvoelker has quit IRC03:26
*** amotoki has joined #openstack-meeting-303:30
*** banix has quit IRC03:33
*** hoangcx has joined #openstack-meeting-303:40
*** hoangcx has left #openstack-meeting-303:40
*** baoli has quit IRC03:43
*** tqtran has joined #openstack-meeting-303:49
*** yamamot__ has joined #openstack-meeting-304:01
*** tqtran has quit IRC04:02
*** Poornima has joined #openstack-meeting-304:02
*** hoangcx has joined #openstack-meeting-304:02
*** hoangcx has left #openstack-meeting-304:02
*** yamamot__ has quit IRC04:05
*** numan_ has joined #openstack-meeting-304:11
*** yamamot__ has joined #openstack-meeting-304:17
*** JieLi has quit IRC04:20
*** hoangcx has joined #openstack-meeting-304:21
*** hoangcx has left #openstack-meeting-304:21
*** markvoelker has joined #openstack-meeting-304:26
*** askb has joined #openstack-meeting-304:30
*** salv-orlando has joined #openstack-meeting-304:31
*** markvoelker has quit IRC04:32
*** numan_ has quit IRC04:33
*** mrmartin has joined #openstack-meeting-304:36
*** zhurong has quit IRC04:39
*** iyamahat has quit IRC04:39
*** salv-orlando has quit IRC04:39
*** zhangkepi has joined #openstack-meeting-304:43
*** woodster_ has joined #openstack-meeting-304:44
*** zhurong has joined #openstack-meeting-304:48
*** zhangkepi has quit IRC04:50
*** zhangkepi has joined #openstack-meeting-304:58
*** rmoe_ has quit IRC04:59
*** rmoe has joined #openstack-meeting-304:59
*** zhangkepi has quit IRC04:59
*** zhangkepi has joined #openstack-meeting-305:00
*** armax has quit IRC05:01
*** zhangkepi has quit IRC05:01
*** zhangkepi has joined #openstack-meeting-305:02
*** rossella_s has quit IRC05:03
*** rossella_s has joined #openstack-meeting-305:03
*** zhangkepi has quit IRC05:03
*** Sukhdev has joined #openstack-meeting-305:03
*** zhangkepi has joined #openstack-meeting-305:04
*** zhangkepi has quit IRC05:05
*** tfukushima has quit IRC05:10
*** askb has quit IRC05:22
*** askb has joined #openstack-meeting-305:23
*** krtaylor has quit IRC05:29
*** sekrit has quit IRC05:30
*** mrmartin has quit IRC05:30
*** krtaylor has joined #openstack-meeting-305:31
*** zhangkepi has joined #openstack-meeting-305:34
*** zhangkepi has quit IRC05:35
*** nkrinner has joined #openstack-meeting-305:35
*** zhangkepi has joined #openstack-meeting-305:38
*** hdaniel has joined #openstack-meeting-305:39
*** sdake has joined #openstack-meeting-305:40
*** sdake_ has quit IRC05:42
*** zhangkep_ has joined #openstack-meeting-305:44
*** hdaniel has quit IRC05:45
*** salv-orlando has joined #openstack-meeting-305:46
*** zhangkepi has quit IRC05:47
*** sdake_ has joined #openstack-meeting-305:49
*** sdake has quit IRC05:52
*** anilvenkata has joined #openstack-meeting-305:53
*** mickeys has joined #openstack-meeting-305:55
*** salv-orlando has quit IRC05:55
*** JieLi has joined #openstack-meeting-305:59
*** fawadkhaliq has joined #openstack-meeting-306:02
*** mickeys has quit IRC06:06
*** mickeys has joined #openstack-meeting-306:07
*** Sukhdev has quit IRC06:08
*** NikitaKonovalov_ has joined #openstack-meeting-306:08
*** NikitaKonovalov_ has quit IRC06:10
*** mickeys has quit IRC06:11
*** soichi has joined #openstack-meeting-306:18
*** anil_rao has joined #openstack-meeting-306:19
*** scheuran has joined #openstack-meeting-306:20
*** fawadkhaliq has quit IRC06:20
*** sekrit has joined #openstack-meeting-306:23
*** tfukushima has joined #openstack-meeting-306:24
*** lpetrut has joined #openstack-meeting-306:24
*** kaz has joined #openstack-meeting-306:27
*** markvoelker has joined #openstack-meeting-306:29
anil_rao#startmeeting taas06:29
openstackMeeting started Wed Apr  6 06:29:54 2016 UTC and is due to finish in 60 minutes.  The chair is anil_rao. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.06:29
*** openstack changes topic to " (Meeting topic: taas)"06:29
openstackThe meeting name has been set to 'taas'06:29
*** belmoreira has joined #openstack-meeting-306:30
anil_raoGreat, let's get started.06:30
anil_rao#topic Summit planning schedule finalization , and what are our AI for the summit06:31
*** openstack changes topic to "Summit planning schedule finalization , and what are our AI for the summit (Meeting topic: taas)"06:31
anil_raoDo folks feel we need a separate topic for TaaS06:31
soichiwhat do you say to add TaaS (*aaS) as a topic?06:32
anil_raoI am for it. :-)06:32
soichiokay, thank you.06:33
soichii think we need to join discussion about ovs agent refactoring (e.g. soft restarting)06:33
soichiissue: when ovs agent restarted, taas flows (and flows without cookie) will be removed06:33
anil_raosoichi: Agree. I'll add some entries in there06:33
soichiyes, please06:34
anil_raoLet's move to the next item06:34
*** kazu has joined #openstack-meeting-306:34
anil_rao#topic TaaS Dashboard discussion06:35
*** openstack changes topic to "TaaS Dashboard discussion (Meeting topic: taas)"06:35
*** markvoelker has quit IRC06:35
soichii hope the dashboard works fine on your site06:35
anil_raosoichi,kaz: I will be installing theTaaS dashboard tomorrow.06:35
anil_raoI wanted to first ensure that the neutron client option was working correctly.06:35
soichii see06:36
*** kaz has quit IRC06:36
soichinow we have only 2 weeks or so until summit06:36
soichiso, i'm planing to prepare a back up plan06:36
soichithat is, making a demo video to show how to create a tap-service and a tap-flow from dashboard06:36
anil_raosoichi: I have most of the backend side working already. After I hook up the Dashboard the plan is to record everything on a video.06:37
anil_raoWe will be using two experiments -- 1) data-analytics and 2) security (IDS)06:37
anil_raoThe plan it to drive things via the GUI06:37
soichiit dounds fine06:38
soichidounds -> sounds06:38
anil_raosoichi: I might have some questions for Kaz and you if I run into a problem.06:38
soichiyes, of course06:39
*** zhangkepi has joined #openstack-meeting-306:39
*** zhangkep_ has quit IRC06:39
anil_raoI think the Dashboard will be a big step forward compared to last year's demo. :)06:39
soichithank you06:39
anil_raosoichi, kaz: Anything else you wanted to add/update on the Dashboard?06:40
soichiwe don't have06:40
anil_raoHere is one if you don't mind.06:41
anil_raoMy current DevStack already has the new version of Horizon network topology. I am guessing that after I being in the Kilo commit I should be back to the older format06:41
anil_raoIs that correct?06:41
*** kazu_ has joined #openstack-meeting-306:42
*** kazu has quit IRC06:42
soichiyes, you need to use the commit written in the instcution guide Kaz had sent to you06:43
anil_raoThanks for confirming. Sounds good.06:43
anil_rao#topic Update on TaaS traffic testing06:44
*** openstack changes topic to "Update on TaaS traffic testing (Meeting topic: taas)"06:44
anil_raoHere is a short update on the traffic testing.06:44
anil_raoThe neutron client issue we had seen when the tap-service and tap-flow lists were empty is now gone. Looks like something got fixed in the latest DevStack06:45
*** mrmartin has joined #openstack-meeting-306:46
reedipcliff update06:46
anil_raoSome of reedip's patches are stuck but bringing them in manually fixes the issues they were designed for.06:46
*** woodster_ has quit IRC06:47
anil_raoI haven't tested the update commands, but they will not be necessary for the Summit demo.06:47
anil_raoThe other commands are working correctly, so the neutron client side looks great.06:47
reedipthey need +A now.... most of them are fixed, and the once which are not would have a merge conflict so I am awaiting the merge of current +2 patches06:47
anil_raoreedip: I'll see to that tomorrow morning.06:48
*** kazu_ has quit IRC06:48
anil_raoyamamoto's latest review for removing the network parameter should get in. I'll complete that review too tomorrow.06:48
*** kaz_ has joined #openstack-meeting-306:49
anil_raoThat should make things cleaner w.r.t. to the client usage.06:49
anil_raoOn the agent/driver side we have one problem.06:49
anil_raoUpon start up it seems like the ML2 driver is wiping out the initial TaaS driver flows in br-tun.06:50
*** NikitaKonovalov_ has joined #openstack-meeting-306:50
anil_raoWhen I stop and restart the TaaS driver (manually) the TaaS flows come back.06:50
anil_raoAfter that all is good. Traffic flows as expected when tap-flows are added to a tap-service instance.06:51
yamamot__are you talking about ?06:51
openstackLaunchpad bug 1525775 in neutron "When ovs-agent is restarted flows creatd by other than ovs-agent are deleted." [Undecided,In progress] - Assigned to SUZUKI, Kazuhiro (kaz-k)06:51
anil_raoActually on my system this is noticed right after running
anil_raoI think after the TaaS driver has run its init routine the ML2 driver is cleaning somehing up.06:53
yamamot__depending on the timing, i think it can be right after
anil_raoI want to get the demo setup ready for the Summit first. We can look into this later.06:53
*** mrmartin has quit IRC06:54
reedipyou can restart TaaS in your if you want a true hack06:54
reedipthat ways once is completed and ML2 is almost over, you can restart TaaS service06:54
anil_raoIts not a big deal for the moment, so I'll let it be. After I manually restart the TaaS agent all is fine.06:54
yamamot__reedip: do you think l2 agent extension can be done anytime soon?06:55
reedipyou wont be able to start it via Dashboard :)06:55
reedipyamamot__ I have studied the L2 extension spec06:55
*** zhurong has quit IRC06:55
reedipyamamot__ do you know of any projects which have done similar migrations, I can take some hints from there as well06:56
*** numan_ has joined #openstack-meeting-306:56
anil_raoThe setup I have comprises of the following: 1 controller, 1 network, 2-3 compute06:56
yamamot__i'm not aware of any, besides in-tree one (qos)06:56
anil_raoBoth local and remote port-mirroring is working.06:56
*** zhurong has joined #openstack-meeting-306:57
reedipyamamot__ Ok, let me exp myself, and will ping you and other neutrinoes :)06:57
reedipwhen I get stuck06:57
yamamot__reedip: i _think_ it isn't too difficult.  but let's see. :-)06:57
reedipyamamot__ I cannot say the same, whats easy for you may be an everest for me :)06:58
reedipbut atleast it would help me understand!06:58
*** vgridnev has joined #openstack-meeting-306:59
anil_raoWe have two issues remaining:06:59
*** lijie has joined #openstack-meeting-306:59
yamamot__anil_rao: great to hear it still works regardless of the lack of automated tests06:59
*** JieLi has quit IRC06:59
anil_raoYes, suprising isn't it. I have been testing it through every now and then manually. :)07:00
anil_raoA few remaining issues:07:00
anil_rao1. Interaction with anti-arp spoofing flows in br-int.07:00
anil_raoToward this we can discuss with the OVS agent externsion folks at the summit. I'll add an item to the design summit idea page07:01
anil_rao2. Problem with traffic capture when TaaS agent is running on the network node.07:01
anil_raoThis has to do with the use of vlans by the br-ex bridge.07:02
anil_raoI'll look into this to see and try to find a fix.07:02
*** alexpilotti has joined #openstack-meeting-307:02
yamamot__you might want to avoid br-ex.  eg. use flat provider network instead07:04
anil_raoThat should be it for the traffic update.07:04
anil_raoyamamot_: OK07:05
yamamot__wrt testing, i wrote a small utility and it was convenient for me during developement
*** pcaruana has joined #openstack-meeting-307:06
anil_raoyamamot_: That is nice!07:06
*** ihrachys has joined #openstack-meeting-307:06
reedipyeah, it was a pretty nifty creation07:07
*** alexpilotti has quit IRC07:07
anil_raosoichi,kaz: I'll report back after I have the TaaS Dashboard hooked up. :-)07:08
kaz_Yes, please07:09
anil_rao#topic midonet implementation (crude but working)07:09
*** openstack changes topic to "midonet implementation (crude but working) (Meeting topic: taas)"07:09
yamamot__it's mine07:09
yamamot__just fyi, i have another working implementation of taas api, backed by midonet.07:10
yamamot__see the link on the agenda incase you're interested.07:10
yamamot__that's all.07:10
*** paul-carlton2 has quit IRC07:11
anil_raoyamamot__: What is the difference between the two versions, if I may ask?07:11
*** salv-orlando has joined #openstack-meeting-307:12
yamamot__it's for midonet, which is completely different implementation of l2/l3.07:13
yamamot__i tried to make it semantically equivalent of ovs impl.07:13
yamamot__but there are small differences i guess.07:13
*** liangbo has joined #openstack-meeting-307:14
anil_raoyamamot__: Thanks. Sounds good. Did you find any thing in the TaaS API that could be done differently/better.07:14
yamamot__duplicated tap flows (a question i asked in the previous meeting)07:15
yamamot__midonet impl does just work for those flows07:15
anil_raoI would argue that they are not duplicated flows but different flows with same ports but mapping to different tap-services.07:16
yamamot__so for midonet impl the current taas api is ok.07:16
anil_raoDid I have that right?07:16
*** dedery has joined #openstack-meeting-307:17
yamamot__midonet impl just works even if they are completely same (same source and same dest)07:17
*** dedery has quit IRC07:17
*** dedery has joined #openstack-meeting-307:17
anil_raoWhy would you want same source to same dest done more than once?07:17
yamamot__i don't know.  the current api allows tham and i had no reason to reject them.07:18
yamamot__a difficulty was tapping "position" wrt security groups.07:18
anil_raoHowever, that just consumes extra flows but doesn't provide any other benefit unless I am missing something.07:19
anil_raoI think we should disallow that case.07:19
yamamot__sure, i don't object if you want to reject such flows at api level or impl level.  i just stated a difference between midonet impl and ovs impl.07:20
*** zhangkepi has quit IRC07:20
anil_raoUnderstand and agree.07:20
yamamot__the current tapping position is from the implementation detail of ovs and was not suitable to midonet impl.07:20
anil_raoI think what we should be supporting instead is same source port and multiple tap-service instances. I plan to add that support for OVS.07:21
yamamot__many of work in midonet side was to overcome the difference.07:21
*** zhangkepi has joined #openstack-meeting-307:21
*** ccamacho has quit IRC07:21
yamamot__anil_rao: it works for midonet as well07:22
anil_raoI think we should rethink the tapping position. Any idea if/when Security Groups will come out of the Linux bridge07:22
anil_raoyamamot__: I am glad you have that working. We need that on OVS too. :-)07:23
anil_raoIts good to see another backend implementation for TaaS.07:24
yamamot__anil_rao: i guess it's mostly impossible as far as SG is implemented in LB.  we need flow-based SG.07:24
anil_raoyamamot__: +107:24
yamamot__fortunately flow-based SG is actively being worked on these days07:25
anil_raoyamamot__: That is great! Perhaps we should interact with those folks at the summit.07:25
*** mrmartin has joined #openstack-meeting-307:26
anil_raoLet's move to open discussion07:26
anil_rao#topic Open Discussion07:26
*** openstack changes topic to "Open Discussion (Meeting topic: taas)"07:26
*** lpetrut has quit IRC07:27
anil_raoWhat do folks think about moving the TaaS IRC meeting one hour earlier.07:27
yamamot__fine for me07:27
anil_raoWith the change to summer/daylight time it is quite late here in the US.07:27
soichino problem for me, too07:28
*** mrmartin has quit IRC07:28
anil_raoVinay also prefers it because of their time change (Sweeden)07:28
yamamot__i'm glad we have no daylight saving here :-)07:28
anil_raoyamamot__: :-)07:29
*** vgridnev has quit IRC07:29
anil_raoOK, we are out of time for today. We'll continue next week.07:29
*** openstack changes topic to "OpenStack Meetings ||"07:29
openstackMeeting ended Wed Apr  6 07:29:56 2016 UTC.  Information about MeetBot at . (v 0.1.4)07:29
yamamot__thank you07:29
openstackMinutes (text):
*** anil_rao has quit IRC07:30
*** kaz_ has quit IRC07:30
*** soichi has left #openstack-meeting-307:31
*** jlanoux has joined #openstack-meeting-307:32
*** yamamot__ has quit IRC07:32
*** jschwarz has joined #openstack-meeting-307:32
*** yamamot__ has joined #openstack-meeting-307:34
*** ifat_afek has joined #openstack-meeting-307:35
*** hdaniel has joined #openstack-meeting-307:43
*** mrmartin has joined #openstack-meeting-307:43
*** zhangkepi has quit IRC07:45
*** zhangkepi has joined #openstack-meeting-307:50
*** zhangkepi has quit IRC07:50
*** mbound has joined #openstack-meeting-307:52
*** mrmartin has quit IRC07:53
*** mrmartin has joined #openstack-meeting-307:54
*** mrmartin has quit IRC07:54
*** egallen has joined #openstack-meeting-307:55
*** JeanBriceCombebi has joined #openstack-meeting-307:57
*** kzaitsev_mb has joined #openstack-meeting-307:58
ifat_afek#startmeeting vitrage08:00
openstackMeeting started Wed Apr  6 08:00:20 2016 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: vitrage)"08:00
openstackThe meeting name has been set to 'vitrage'08:00
*** alexey_weyl has joined #openstack-meeting-308:00
ifat_afekHi everyone :-)08:00
*** elisha_r has joined #openstack-meeting-308:00
*** mkoushnir has joined #openstack-meeting-308:01
*** tsufiev has joined #openstack-meeting-308:01
*** eyalb has joined #openstack-meeting-308:02
eyalbhi all08:02
*** tsufiev has left #openstack-meeting-308:02
*** idan_hefetz has joined #openstack-meeting-308:03
ifat_afekNote a change in our agenda – we’ll have a separate topic for Austin preparations.08:05
ifat_afek* Current status08:05
ifat_afek* Austin preparations08:05
ifat_afek* Review action items08:05
ifat_afek* Next steps08:05
ifat_afek* Open Discussion08:05
ifat_afek#topic Current status08:06
*** openstack changes topic to "Current status (Meeting topic: vitrage)"08:06
ifat_afekAodh updates: I didn’t progress with aodh this week. Still have some work to do...08:06
*** lhartal has joined #openstack-meeting-308:07
idan_hefetzsame, here regarding the aodh notifier i didnt have much progress this week08:07
idan_hefetzi will update design changes soon08:07
ifat_afekidan_hefetz: cool08:08
ifat_afekwho else wants to update?08:08
elisha_rI'll give a quick update08:08
*** stanzgy has quit IRC08:08
elisha_rThis week we finally pushed the evaluator documentation to gerrit08:08
elisha_rawaiting review08:09
ifat_afekifat_afek: I'll have a look at it after the meeting08:09
mkoushnirtempest updates: nova alarms test almost finished, rest alarms test in progress, I need help: generate aodh alrms and nagios alarms, Alesha will help me with topology tests08:10
elisha_rthats it from my end.08:10
ifat_afekelisha_r: thanks08:10
ifat_afekmkoushnir: alexey_weyl said he would help. do you need any additional help?08:10
mkoushnirElisha, I need generate several nagios alarms. Can you help me?08:11
mkoushnirHow can help me with aodh alarms?08:11
elisha_rwe might be able to use the mock_synchronizer to generate nagios alarms for now, but I will have to see how this works within the tempest framework to know for sure08:11
*** danoffek has joined #openstack-meeting-308:11
*** eddie_lechtus has joined #openstack-meeting-308:12
danoffekhi guys08:12
mkoushnirOk, Thanks Elisha08:12
ifat_afekmkoushnir: I'll be able to help with aodh, but I didn't finish coding yet. will update you once you can start checking it08:12
*** NikitaKonovalov_ has quit IRC08:13
alexey_weylI am helping Noam to see how we can run tempsest in the zuul gate08:14
alexey_weylwe are looking on examples from other projects, and need to push that change to project-info08:14
alexey_weylBecause it depends on other people, we need to do that as fast as possible to get feedbacks from them about that08:15
ifat_afekalexey_weyl: I agree. and we need the tempest tests in order to become an official openstack project08:15
lhartalI have an update08:17
*** NikitaKonovalov_ has joined #openstack-meeting-308:17
lhartalFrom next week, we are going to have some teminology changes08:17
lhartalwe are no longer going to use the name 'plugin' and 'synchronizers' from now we will use 'data source' and 'driver' respectively08:18
*** NikitaKonovalov_ has quit IRC08:18
lhartaldata source means the source vitrage connect to (nove, cinder, etc.)08:19
lhartaland the driver is actually responsible for the connction itself08:20
lhartalhopefully, I will push the changes by the end of the week (good luck for us :) )08:21
ifat_afekgood luck indeed ;-)08:21
eyalbstill working on neutron plug-in wrote the transformers need to work on the receiving change events from bus08:23
ifat_afekeyalb: cool, thanks08:23
ifat_afekanyone else wants to update?08:23
ifat_afekeddie_lechtus, do you have updates?08:23
ifat_afekok, let's move on08:26
ifat_afek#topic Austin preparations08:26
*** openstack changes topic to "Austin preparations (Meeting topic: vitrage)"08:26
ifat_afekThere will be two Vitrage sessions in Austin:08:26
ifat_afekWe started discussing our goals and preparations for the summit. alexey_weyl, do you want to update?08:27
*** lijie has quit IRC08:28
*** NikitaKonovalov_ has joined #openstack-meeting-308:28
alexey_weylYes, I would love to08:28
alexey_weylWe have talked about the arrangmenets for the Vitrage Booth in the summit08:29
alexey_weylwe are going to have 2 people in every moment there08:29
*** mrmartin has joined #openstack-meeting-308:29
alexey_weylwe have splitted the hours between the people08:29
alexey_weylwe are doing the rehersals for all the people the will be in the booth08:30
alexey_weylIfat, you can continue from here08:30
ifat_afekalexey_weyl: cool08:30
*** markvoelker has joined #openstack-meeting-308:30
ifat_afekI think that in addition you should meet Julien, telemetry PTL, and Roland, Monasca PTL, and discuss the integration of Vitrage with these projects08:31
ifat_afekI already sent emails to the both of them08:31
ifat_afekspecifically with aodh, we have several open issues, and discussing them face to face might help08:32
ifat_afek#topic Review action items08:32
*** openstack changes topic to "Review action items (Meeting topic: vitrage)"08:32
ifat_afek• make sure you have a blueprint for your current task08:32
ifat_afekI believe this is done, some new blueprints were opened by the relevant people08:33
ifat_afek#topic Next Steps08:33
*** openstack changes topic to "Next Steps (Meeting topic: vitrage)"08:33
ifat_afekWe should start thinking about Newton version08:33
ifat_afekCurrently we have very few blueprints in our list, most of them are about to be finished. If you have an idea to be implemented for Newton, feel free to add a blueprint08:33
ifat_afekI asked Maty to create ‘newton’ version in Virtrage launchpad08:33
ifat_afek#action add blueprints for Newton08:34
*** vgridnev has joined #openstack-meeting-308:34
ifat_afek#topic Open Discussion08:34
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"08:34
ifat_afekanything you would like to discuss?08:34
*** markvoelker has quit IRC08:35
*** e0ne has joined #openstack-meeting-308:36
ifat_afekso I guess we are done08:36
ifat_afekgoodbye everybody08:36
alexey_weylbye bye08:36
*** alexey_weyl has quit IRC08:36
*** danoffek has left #openstack-meeting-308:36
lhartalbye :)08:36
*** lhartal has quit IRC08:36
*** elisha_r has quit IRC08:36
*** openstack changes topic to "OpenStack Meetings ||"08:37
openstackMeeting ended Wed Apr  6 08:37:17 2016 UTC.  Information about MeetBot at . (v 0.1.4)08:37
openstackMinutes (text):
*** ifat_afek has left #openstack-meeting-308:38
*** mkoushnir has quit IRC08:38
*** eyalb has quit IRC08:44
*** salv-orlando has quit IRC08:45
*** neiljerram has joined #openstack-meeting-308:51
*** kzaitsev_mb has quit IRC08:51
*** vgridnev has quit IRC08:57
*** e0ne has quit IRC09:00
*** sambetts|afk is now known as sambetts09:00
*** lpetrut has joined #openstack-meeting-309:01
*** rossella_s has quit IRC09:03
*** rossella_s has joined #openstack-meeting-309:03
*** liangbo has quit IRC09:08
*** NikitaKonovalov_ has quit IRC09:08
*** JeanBriceCombebi has quit IRC09:11
*** JeanBriceCombebi has joined #openstack-meeting-309:11
*** salv-orlando has joined #openstack-meeting-309:15
*** NikitaKonovalov_ has joined #openstack-meeting-309:18
*** salv-orlando has quit IRC09:19
*** itxaka has joined #openstack-meeting-309:24
*** tfukushima has quit IRC09:28
*** zhurong has quit IRC09:30
*** vgridnev has joined #openstack-meeting-309:54
*** JeanBriceCombebi has quit IRC09:59
*** yamamot__ has quit IRC10:00
*** salv-orlando has joined #openstack-meeting-310:02
*** sdake_ has quit IRC10:02
*** salv-orlando has quit IRC10:03
*** salv-orlando has joined #openstack-meeting-310:03
*** yamamot__ has joined #openstack-meeting-310:03
*** NikitaKonovalov_ has quit IRC10:04
*** NikitaKonovalov_ has joined #openstack-meeting-310:04
*** JeanBriceCombebi has joined #openstack-meeting-310:04
*** e0ne has joined #openstack-meeting-310:06
*** NikitaKonovalov_ has quit IRC10:07
*** yamamot__ has quit IRC10:08
*** ekarlso- has quit IRC10:09
*** sdague has joined #openstack-meeting-310:09
*** kzaitsev_mb has joined #openstack-meeting-310:10
*** stanzgy has joined #openstack-meeting-310:12
*** NikitaKonovalov_ has joined #openstack-meeting-310:16
-openstackstatus- NOTICE: npm lint jobs are failing due to a problem with npm registry. The problem is under investigation, and we will update once the issue is solved.10:18
*** ChanServ changes topic to "npm lint jobs are failing due to a problem with npm registry. The problem is under investigation, and we will update once the issue is solved."10:18
*** salv-orlando has quit IRC10:18
*** hoangcx has joined #openstack-meeting-310:19
*** mrmartin has quit IRC10:20
*** ekarlso has joined #openstack-meeting-310:23
*** mrmartin has joined #openstack-meeting-310:25
*** salv-orlando has joined #openstack-meeting-310:26
*** numan_ has quit IRC10:30
*** salv-orlando has quit IRC10:30
*** markvoelker has joined #openstack-meeting-310:31
*** numan_ has joined #openstack-meeting-310:32
*** numan_ has quit IRC10:33
*** numan_ has joined #openstack-meeting-310:33
*** mrmartin has quit IRC10:34
*** markvoelker has quit IRC10:36
*** numan_ has quit IRC10:43
*** NikitaKonovalov_ has quit IRC10:44
*** salv-orlando has joined #openstack-meeting-310:47
*** alexpilotti has joined #openstack-meeting-310:48
*** salv-orlando has quit IRC10:48
*** numan_ has joined #openstack-meeting-310:55
*** idan_hefetz has quit IRC10:56
*** tqtran has joined #openstack-meeting-310:56
*** salv-orlando has joined #openstack-meeting-310:57
*** salv-orlando has quit IRC10:57
*** salv-orlando has joined #openstack-meeting-310:57
*** salv-orlando has quit IRC10:57
*** salv-orlando has joined #openstack-meeting-310:58
*** salv-orlando has quit IRC10:58
*** JeanBriceCombebi has quit IRC11:00
*** tqtran has quit IRC11:01
*** tellesnobrega is now known as tellesnobrega_af11:04
*** yamamoto_ has joined #openstack-meeting-311:09
*** yamamoto_ has quit IRC11:10
*** yamamoto_ has joined #openstack-meeting-311:10
*** yamamoto_ has quit IRC11:10
*** vtech has joined #openstack-meeting-311:13
*** marg7175 has joined #openstack-meeting-311:17
*** JeanBriceCombebi has joined #openstack-meeting-311:21
*** rtheis has joined #openstack-meeting-311:29
*** amotoki has quit IRC11:30
*** kenji-i has quit IRC11:39
*** yamamoto has joined #openstack-meeting-311:41
*** askb has quit IRC11:47
*** yamamoto has quit IRC11:48
*** tellesnobrega_af is now known as tellesnobrega11:48
*** doug-fish has joined #openstack-meeting-311:50
*** tsufiev has joined #openstack-meeting-311:53
*** robcresswell has joined #openstack-meeting-311:55
*** amotoki has joined #openstack-meeting-311:56
*** mrmartin has joined #openstack-meeting-311:58
*** r1chardj0n3s has joined #openstack-meeting-311:59
robcresswell#startmeeting horizon12:00
openstackMeeting started Wed Apr  6 12:00:48 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: horizon)"12:00
openstackThe meeting name has been set to 'horizon'12:00
amotokihi (but on a train)12:01
robcresswellHi all. Couple of notices first.12:02
*** atuvenie_ has joined #openstack-meeting-312:02
robcresswellI've a patch up to move the 1200 meeting to 800UTC12:02
robcresswellAnd I'll email once that merges12:02
robcresswellShould be by next week, so hopefully thats a little better for those further east :)12:03
*** domi007 has joined #openstack-meeting-312:03
robcresswellNext up is session topics; I've reorganised the etherpad to try and find common topics12:03
-amotoki- is being surprised12:04
robcresswellamotoki: NA attendance in 1200 UTC meeting is low already, and its very difficult  for those around UTC > +7 to attend any meetings currently.12:04
robcresswellHoping to make it more inclusive.12:04
*** abalutoiu has joined #openstack-meeting-312:05
robcresswellSo re: session topics, I'm planning on using the fishbowl for ops and plugin feedback, and the meetup for open discussion/ priorities spillover.12:05
robcresswellWe then have 7 working group sessions, but so far only about 5/6 clear topics it seems.12:05
*** david-lyle_ has joined #openstack-meeting-312:06
itxakarobcresswell, is the plan to broadcast/rocord the sessions still up?12:06
*** cartik has joined #openstack-meeting-312:07
robcresswellPotentially. It seems like adequate h/w may be an issue from previous discussions.12:07
robcresswellAnyway, if you have any other suggestions for topics, please add them as I'll be filling out the sessions topics officially this week.12:08
robcresswellThats it for notices, and the agenda is empty12:09
robcresswell#topic Open Discussion12:09
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"12:09
*** cartik has quit IRC12:10
itxakadjango 1.9 patch, what is missing and how can we move forward with it?12:10
*** salv-orlando has joined #openstack-meeting-312:10
robcresswellAFAIK its done, needs testing and reviews.12:10
robcresswellThere was a -1 which I believe I've fixed12:11
tsufievI'll review it soon, in 1-2 days12:11
robcresswellFor cores in the meeting, it could use attention. We need to move on to 1.10 swiftly.12:11
robcresswellThere is also to solve the logspam.12:12
r1chardj0n3srgr that robcresswell12:12
robcresswelllogspam from 1.9 that is (you'll know what I mean when you test it ;) )12:12
robcresswellthanks r1chardj0n3s12:12
robcresswellBug day cleaned a smooth 100 off the backlog. We're now <250 to triage.12:12
tsufievwhat shall we do about *npm-run* issue?12:13
r1chardj0n3stsufiev: which issue?12:13
robcresswellr1chardj0n3s: Gate is kaput12:13
r1chardj0n3sthe one where it's constantly failing in the gate?12:13
r1chardj0n3sI was about to bring that up :/12:13
*** e0ne has quit IRC12:13
robcresswellSo there is/was an issue against NPM, that has been closed.12:13
r1chardj0n3sI think we really need to start talking npm mirroring with infra12:15
robcresswellActually, looking at logs I've just noticed infra is on it, I guess they saw my message this morning (or someone elses)12:15
*** markvoelker has joined #openstack-meeting-312:15
robcresswellYeah, they changed the Horizon topic to it :)12:16
*** baoli has joined #openstack-meeting-312:16
robcresswellFrom digging through the NPM bug report, its unclear to me exactly how we fix it. Most of the answers seem to be "just upgrade lolz"12:17
*** ttrifonov has quit IRC12:17
robcresswellWhich isn't terribly helpful.12:17
*** e0ne has joined #openstack-meeting-312:17
r1chardj0n3sthat seems to be a common response to node-related issues; it moves quickly :/12:18
robcresswellSometimes bad, sometimes good.12:18
robcresswellI don't really view disabling the tests as a viable option, since it just means we cant merge JS code with our tests down.12:19
r1chardj0n3sindeed, that's a bad solution12:19
robcresswellAnd its just ignoring the issue and hoping it goes away.12:19
tsufievI'm very worried that waiting the problem to solve itself (or for #infra to solve it for us) give us no time to merge Swift UI/Ceph patch prior to M release12:20
robcresswelltsufiev: I spoke with david-lyle yesterday, and he doesnt believe its critical enough for an RC3.12:20
robcresswellMitaka is his call, so you'll need to take it up with him later in the day12:20
robcresswellAs I understand it, Ceph was broken before this anyway, so its not a regression, we just havent fixed it with the new UI.12:21
*** baoli_ has joined #openstack-meeting-312:21
tsufievI can understand that. Well, merging it into stable/mitaka in 1-2 weeks is also okay to me12:21
r1chardj0n3sit's a shame - I didn't even realise that the swift ui could be a ui over ceph12:22
amotokiactually, Mitaka final RC call was last week.... and this week is reserved for release.12:22
r1chardj0n3s(I don't even know what ceph is)12:22
tsufievr1chardj0n3s, I thought about testing it over Ceph during midcycle, but was distracted with something else12:22
robcresswellr1chardj0n3s: Yeah, I only just found this out too.12:22
*** ttrifonov has joined #openstack-meeting-312:23
robcresswellI'll be looking into it over the course of the day anyway tsufiev, we need the gate moving again.12:23
robcresswellr1chardj0n3s: Is the yellow-ey colour on etherpad you? Could you tag your name?12:24
*** pt_15 has joined #openstack-meeting-312:24
r1chardj0n3ssorry, will do12:24
*** baoli has quit IRC12:24
robcresswellJust leave it inline so we can refer to it at the sessions. its good to know who said what.12:25
r1chardj0n3s(I have colour turned off usually)12:25
amotokibtw, is anyone running horizon with python3?12:25
robcresswellamotoki: Not that I'm aware of. I wouldnt expect it to work12:25
robcresswellUTs pass, but thats far from a function guarantee12:25
amotokiwhen reviewing tsufiev's patch, I am not sure we need to take care of python312:26
robcresswellr1chardj0n3s: Ah, I just meant next to the text itself; names arent carried between sessions or when people go offline it seems.12:26
*** salv-orlando has quit IRC12:26
robcresswellThanks r1chardj0n3s12:26
amotokii just would like to share our review policy at the moment.12:27
amotoki"try to keep python3 work as possible but just do our best." right?12:27
tsufievamotoki, my approach here would be to solve problems as they arise... If Horizon doesn't yet guaranteed to work with py3, shy should we worry?12:28
robcresswellamotoki: I'd have to dig through the code.12:28
tsufievbut it's my patch anyways :)12:28
amotokitsufiev: you are working in one of the most tricky areas around py3.12:28
robcresswellThe easiest thing would be to make sure that code is tested and passes in py312:28
robcresswellIf its not tested, thats a valid -1 anyway, and if the test works, I'd expect it to fall over in python 3.12:29
amotokiit is tough area. actually what we haven't understood is what string should be returned.12:29
amotokiContent-Disposition encoding is different from other mime encoding or url encoding.12:30
*** andymaier has joined #openstack-meeting-312:30
amotokirobcresswell: agree with you. it is better to be covered by test12:30
r1chardj0n3sit should definitely be tested, yes12:31
tsufievI would prefer looking at live Horizon on py3 to be 100% sure12:31
robcresswellAaaand -1. Sorry tsufiev :p12:31
robcresswelltsufiev: Need both.12:32
robcresswellTests must pass, but they are not a guarantee of function12:32
* r1chardj0n3s is curious to run Horizon in py3k now :-)12:32
robcresswellI think doug-fish is lurking in the meeting...12:33
doug-fishI've just returned back to work after a few days off. It's surprising how many things happen in 3 days.12:34
robcresswellall the emails12:35
r1chardj0n3sI concur - I took all of last week off12:35
amotokihope you all enjoyed your off :012:35
amotoki** :)12:35
r1chardj0n3syes, actually ;-)12:36
doug-fishyep. same here.12:36
robcresswelldoug-fish, amotoki: now that zanata works for the recent stable, can we backport string fixes?12:37
robcresswellThings like missing translations etc.12:37
amotokirobcresswell: yes, i think so.12:38
robcresswellIts unclear to me if stable-policy overrules us or not12:38
doug-fishyou can certainly change the previous stable release12:38
amotokirobcresswell: what we need to do is to merge pending import patch before releasing stable update.12:38
*** julim has joined #openstack-meeting-312:39
amotokirobcresswell: before migrating zanata, I proposed import patches manually before stable releases.12:39
doug-fishwe did this during stable/liberty in horizon - added almost the entire Italian translation12:39
r1chardj0n3sthere are some issues with some angular-gettext translations that are being looked into also.12:39
robcresswelldoug-fish: What I meant was introducing or fixing new strings12:39
doug-fishoh - introducing new strings12:39
robcresswellFor example, some strings are wrapped with <translate> but not transalting properly12:40
doug-fishthat's less clear12:40
amotokiyes, some <translate> strings are not extracted12:40
robcresswellI don't know if stable-policy prevents us from fixing those issues or not12:40
doug-fishI think the key there has to be that we have no regressions - that is we shouldn't change an existing, successfully translated string12:40
amotokiand some strings are extracted and translated but not displayed.12:40
amotokidoug-fish: agree.12:41
robcresswellYes, amotoki12:41
robcresswellThere are about 20 outstanding i18n bugs, many of which are very trivial.12:41
doug-fishI'd expect fixing untranslatable english only strings would always be acceptable12:41
amotokifor new strings, i think we can fix them because there are no changes.12:41
r1chardj0n3syep, there might be some issues with the message extraction thing we added to babel12:41
r1chardj0n3sit's still being investigated though12:41
robcresswellr1chardj0n3s: It seems to be stumbling over nested HTML12:41
robcresswellLike <span translate>Some text <b> some more text </b></span12:42
robcresswell if anyone is interested12:42
robcresswellI think we can call the meeting there, unless anyone has anything else?12:44
robcresswellAgain, please add discussion points to
*** julim has quit IRC12:45
*** openstack changes topic to "npm lint jobs are failing due to a problem with npm registry. The problem is under investigation, and we will update once the issue is solved."12:45
openstackMeeting ended Wed Apr  6 12:45:47 2016 UTC.  Information about MeetBot at . (v 0.1.4)12:45
openstackMinutes (text):
robcresswellThanks all12:45
*** tsufiev has left #openstack-meeting-312:45
*** amotoki has quit IRC12:46
*** robcresswell has left #openstack-meeting-312:46
*** thiagop has left #openstack-meeting-312:46
*** tellesnobrega is now known as tellesnobrega_af12:57
*** david-lyle_ has quit IRC12:57
*** atuvenie has joined #openstack-meeting-312:58
*** claudiub|2 has joined #openstack-meeting-313:01
alexpilotti#startmeeting hyper-v13:01
openstackMeeting started Wed Apr  6 13:01:46 2016 UTC and is due to finish in 60 minutes.  The chair is alexpilotti. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** sagar_nikam has joined #openstack-meeting-313:01
*** openstack changes topic to " (Meeting topic: hyper-v)"13:01
openstackThe meeting name has been set to 'hyper_v'13:01
*** stanzgy has quit IRC13:02
alexpilottiFocus this week is mostly on releasing Mitaka13:02
*** rossella_s has quit IRC13:03
alexpilottiso we have a bunch of Py3 bugs that came up13:03
alexpilotti#topic Py3 bugs13:03
*** openstack changes topic to "Py3 bugs (Meeting topic: hyper-v)"13:03
*** rossella_s has joined #openstack-meeting-313:03
alexpilotticlaudiub|2: would you like to list the bugs?13:03
alexpilottiwe still need to file them, but if somebody is aiming at running a Py3 compute node, I think it's useful to know they exist13:04
*** banix has joined #openstack-meeting-313:04
claudiub|2sure. i've fixed a couple of bugs on nova master. primarely about attached volumes, configdrive, etc. you can see them at #link
alexpilottianything else to add here?13:05
claudiub|2python 3 is generally slower13:06
claudiub|2so, it should be used only when absolutely necessary. :)13:06
alexpilottiwe need to do some profiling to see why this happens13:06
claudiub|2even when running py3 unit tests in nova gate, they are about 66% slower than py27 tests.13:06
alexpilottiif it's 66.6% slower we can possible do an exorcism on Py313:07
claudiub|2well, i can definetely say that there's something unholy about it. :)13:07
alexpilottithere's a reason why it's the nova-compute daemon13:08
alexpilotti#topic OVS 2.513:09
*** openstack changes topic to "OVS 2.5 (Meeting topic: hyper-v)"13:09
*** salv-orlando has joined #openstack-meeting-313:09
alexpilottiWe have a OVS 2.5 MSI under test13:09
alexpilottisagar_nikam: do you know if sonu or somebody in your team is testing OVS?13:09
sagar_nikami know sonu has it in plans. dont know the exact time13:10
sagar_nikamwhen it will be done13:10
alexpilottisagar_nikam: ok, I dont see him online, can you please let him know about 2.5?13:11
*** Sonu has joined #openstack-meeting-313:11
sagar_nikamsonu: has joined13:11
alexpilottiSonu: hey sonu13:12
sagar_nikamsonu: alexpilotti: wants to know the plans of testing OVS2.513:12
SonuWhat is new with OVS 2.5 for Windows?13:12
SonuI thought we are focused to test OVS 2.613:12
Sonu'cz that comes Microsoft certified. Am I wrong?13:13
*** itoader has joined #openstack-meeting-313:13
alexpilotti2.5 will be certified as well13:13
alexpilottiwe're currently testing it, before sending it to certification13:13
Sonugreat. then we will use OVS 2.5 + WMI security driver13:13
Sonuand it should all work for VXLAN13:14
*** carl_baldwin has quit IRC13:14
alexpilottiso, if you guys could give it a test-ride before we send it to MSFT signature, it'd be great13:14
alexpilottiyes, VXLAN support is there13:14
*** sdake has joined #openstack-meeting-313:15
Sonualexpilotti: Do you test security groups with OVS?13:15
alexpilottiwe will13:16
*** carl_baldwin has joined #openstack-meeting-313:16
alexpilottiunfortunately for now this means networking-hyperv security groups13:16
alexpilottion the good side, conntrack is coming in 2.613:16
SonuI know. But that is ok, since our aim is VXLAN.13:17
alexpilottiVXLAN is also in 2.513:17
alexpilottiactually even in 2.413:17
SonuYes we got that working with 2.413:17
*** salv-orlando has quit IRC13:17
Sonuwith promt help from Alin13:17
alexpilottidi dyou manage to do some more benchmarking on the latest networking-hyperv security groups?13:17
Sonuin progress.13:18
alexpilottiwe're very pleased with the current results (in the limits of the WMI ACL API)13:18
*** zz_dimtruck is now known as dimtruck13:18
SonuWe are running our scale tests with native threads and pyMI and Enahanced RPC support13:18
alexpilottibut I'm curious to hear your results13:18
alexpilottiSonu: perfect, that's also what we are using13:18
*** sdake_ has joined #openstack-meeting-313:19
*** dslevin has quit IRC13:19
alexpilottibased on latest Rally tests, we're even faster than KVM on Hadoop workloads13:19
*** sdake has quit IRC13:19
alexpilottinot by a big margin, just a tad faster :)13:20
alexpilottibut still a huge step forward from the pre-pymi days13:20
alexpilottiwhere we used to be 4x slower :)13:20
alexpilottianywthing else to add on this?13:20
Sonuthanks for efforts.13:21
alexpilottiSonu: thanks, I take is a "nothing to add" :)13:21
alexpilotti#topic ton of new stuff coming in new-ton13:22
*** openstack changes topic to "ton of new stuff coming in new-ton (Meeting topic: hyper-v)"13:22
alexpilottisorry, I couldnt resist13:22
alexpilottiactually there are two main areas on which we will work:13:22
*** iyamahat has joined #openstack-meeting-313:22
*** jpomeroy has joined #openstack-meeting-313:23
alexpilottiMagnum support for Windows containers13:23
*** iyamahat has quit IRC13:23
alexpilottiNew Neutron plugin for the Windows Server 2016 networking stack13:23
*** sdake_ has quit IRC13:24
alexpilottithe new stack is based on it's own controller, using REST API13:24
*** dslevin has joined #openstack-meeting-313:24
SonuOVSDB based?13:24
alexpilottiit has some OVSDB compatibility13:24
*** dslevin has quit IRC13:24
alexpilottibut it's not as complete and hence usable as the full OVS porting13:24
alexpilottiso on the long term our general vision is to have:13:25
sagar_nikamalexpilotti: magnum support is intresting, we would be intrested13:25
alexpilottiOVS for people wanting to have multiple hypervisor types / interop solutions13:26
alexpilottiespecially with OVN, OpendayLight, NSX, etc13:26
alexpilottiand the new Neutron Hyper-V plugin for Hyper-V only scenarios13:26
*** cloudtrainme has joined #openstack-meeting-313:26
*** annegentle has joined #openstack-meeting-313:27
alexpilottigiven the current usage distribution, the former (OVS) will most probably have more traction13:27
alexpilottisagar_nikam: is there any HP core reviewer in Magnum?13:27
*** sdake has joined #openstack-meeting-313:27
*** iyamahat has joined #openstack-meeting-313:27
sagar_nikamalexpilotti: not sure, can check13:28
Sonualexpilloti: while it seems like more flexibility, but won't this be a challenge to maintain two approaches? one native Hyper-V versus OVS based13:28
alexpilottithere's a non trivial amount of work required around the fact that Heat temmplates used by Magnum are very Linux specific13:28
alexpilottiSonu: it's what we are doing already today with networking-hyperv and OVS13:28
alexpilottithis new plugin will become networking-hyperv v213:29
sagar_nikamalexpilotti: any BPs already ready for magnum ?13:30
alexpilottisagar_nikam: not yet, we are planning to discuss this at the summit with the Magnum team and get the BPs up shortly afterwards13:31
alexpilottithis reminds me of the fact that we have a design session at the summit13:31
alexpilotticlaudiub|2: can you post details?13:32
claudiub|2yep. sure. it's on wednesday, from 9:00AM to 9:40AM13:32
claudiub|2let me get the exact details.13:32
sagar_nikamalexpilotti: any plans in magnum hyperv supporting freezer and monasca ?13:33
*** alex_xu has quit IRC13:33
sagar_nikami mean any plans in newton release13:33
alexpilottithat's also on the TODO list13:33
alexpilottiare you guys already using them in production scenarios?13:34
claudiub|2#info Winstackers: Work session: 2016-04-27, 09:00-09:40, Boardroom 40113:34
sagar_nikammonasca PTL is from HPE, i can connect you to him13:34
alexpilottisagar_nikam: that'd be great!13:34
sagar_nikamFreezer and Monasca for KVM is supported in production13:34
alexpilottiif you have some core reviewer in Freezer to introduce us to, that'd be great13:34
sagar_nikamalexpilotti: shall i request for a meeting between Monasca PTL and your team in summit ?13:35
alexpilottiI mean HP core reviewers13:35
alexpilottisagar_nikam: yes please!13:35
*** alex_xu has joined #openstack-meeting-313:35
alexpilottifor Freezer, Hyper-V has a new API, called RCT13:35
sagar_nikamFreezer PTL is also from HPE, if i remember right13:36
*** Poornima has quit IRC13:36
*** ddieterly has joined #openstack-meeting-313:36
sagar_nikami can find it and request for a meeting with your team and Freezer PTL13:36
sagar_nikamalexpilotti: do you need any meetings with cinder team from HPE ?13:37
*** mtanino has joined #openstack-meeting-313:37
*** itoader has quit IRC13:37
*** tellesnobrega_af is now known as tellesnobrega13:37
alexpilottilpetrut: anything on the agenda for Cinder worth requesting a meeting?13:38
*** itoader has joined #openstack-meeting-313:38
alexpilottiit'd be great meeting in person, of course13:38
lpetrutwell, os-brick may be one of the topics13:38
*** matrohon has joined #openstack-meeting-313:39
*** amotoki has joined #openstack-meeting-313:39
sagar_nikamlet me check and try to schedule a meeting between lpetrut: and hpe cinder team13:39
alexpilottisagar_nikam Sonu: are you guys coming to Austin?13:39
sagar_nikamalexpilotti: do you need to meet anybody else from HPE13:39
lpetrutI guess I can talk about os-brick Windows support with Walter Boring at the summit, as far as I know, he's in charge of the project13:40
sagar_nikamnot me. i am not coming to austin. hopefully some other time13:40
alexpilottisagar_nikam: no thanks, I think those are the main areas13:40
sagar_nikamlpetrut: sure i will request for a meeting13:40
Sonualexpilloti: I have one of my team member attend the design session for hyper-v13:41
*** vhoward has joined #openstack-meeting-313:41
sagar_nikamalexpilotti: sure, will try to arrange for those 2 meetings, monasca and freezer13:41
alexpilottiok, for today's topics, we have a new major feature ready for release:13:42
alexpilotti#topic Shielded VMs13:42
*** openstack changes topic to "Shielded VMs (Meeting topic: hyper-v)"13:42
alexpilottiwe will upload the bits soon13:42
*** tonytan4ever has joined #openstack-meeting-313:43
alexpilottibut if you guys plan to test the feature, we can already provide some info13:43
Sonuthats news to us. Any blue print?13:43
*** davidsha has joined #openstack-meeting-313:43
*** atuvenie has quit IRC13:44
alexpilottithere's a vTPM BP, which is the basis for shielded VMs13:44
sagar_nikamalexpilotti: we will get back on shielded VMs13:44
alexpilottijust wanted to make sure it's on your radar13:45
claudiub|2this was the bp that was approved in Liberty: #link
Sonuthanks. I will read through it to understand the case.13:46
alexpilottishielded VM specs:
sagar_nikamalexpilotti: i have a update on SSL/TLS, we can discuss later when we are done with this topic13:46
*** dimtruck is now known as zz_dimtruck13:47
alexpilottisure, I'm done with this13:48
alexpilottialso time is -12'13:48
alexpilotti#topic SSL/TLS13:48
*** openstack changes topic to "SSL/TLS (Meeting topic: hyper-v)"13:48
sagar_nikamalexpilotti: thanks to the notes from alin: i was able to get the glance image download working as part of nova boot13:48
sagar_nikamnext i am hitting a issue in invoking neutron agent13:49
sagar_nikamwil debug further13:49
sagar_nikamin the meanwhile13:49
sagar_nikami have a question13:49
sagar_nikamwe added the crt file in nova .conf13:49
sagar_nikampoint to some location on hyperv host13:49
sagar_nikamthat was a self signed certificate13:50
sagar_nikamhow do we add multiple certificates13:50
sagar_nikamsuppose a customer does not want to use the self signed certs13:50
sagar_nikamand adds his own certificate13:50
sagar_nikampossible multiple certificates13:50
sagar_nikamhow do we handle it13:51
alexpilottimultiple because you have multiple endpoints for the same service?13:51
sagar_nikamsame endpoint for a service13:51
*** numan_ has quit IRC13:51
sagar_nikambut assuming the customer adds his own signed certificate13:52
alexpilottieach service has it's own config, I'd expect13:52
alexpilottiplus, I need to check, but if the cert is signed by a CA, on the client side the CA cert should be enough13:52
sagar_nikamin case of KVM, multiple certs can be added in cert manager13:52
*** matrohon has quit IRC13:53
*** JeanBriceCombebi has quit IRC13:53
alexpilottiprovided that CN matches the hostname13:53
alexpilottione SSL/TLS endpoint = 1 cert13:53
*** matrohon has joined #openstack-meeting-313:53
sagar_nikamwill investigate further and get back13:53
lpetrutwrong window, sorry13:54
alexpilottinp :)13:54
sagar_nikamon freerdp13:54
sagar_nikamhow does it work13:54
sagar_nikamif TLS is enabled ?13:54
sagar_nikamon the network which tenants access horizon13:54
alexpilottisame: wsgate.ini has settings for the certifcate13:54
alexpilottiour MSI generates a self signed one, for ease of use13:55
alexpilottiwhich can be replaced by a CA signed one for most production usages13:55
*** ddieterly is now known as ddieterly[away]13:55
alexpilottiif you just override it, it just works13:55
sagar_nikamthats good13:55
alexpilotti#topic open discussion13:56
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:56
sagar_nikamif the same works for nova, i mean signed certificate from a customer, by just adding in nova.conf, we are good13:56
alexpilottianything else that you guys would like to add before wrapping up?13:57
sagar_nikamnothing from my end13:57
*** JeanBriceCombebi has joined #openstack-meeting-313:57
alexpilottialright, thanks y'all see you next week!13:57
*** openstack changes topic to "npm lint jobs are failing due to a problem with npm registry. The problem is under investigation, and we will update once the issue is solved."13:58
openstackMeeting ended Wed Apr  6 13:58:04 2016 UTC.  Information about MeetBot at . (v 0.1.4)13:58
openstackMinutes (text):
*** atuvenie_ has quit IRC13:58
ajohi :)14:00
ajolet's start14:01
ajo#meeting neutron_qos14:01
ajo#startmeeting neutron_qos14:02
openstackMeeting started Wed Apr  6 14:02:02 2016 UTC and is due to finish in 60 minutes.  The chair is ajo. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:02
openstackThe meeting name has been set to 'neutron_qos'14:02
*** ddieterly[away] is now known as ddieterly14:02
*** claudiub|2 has quit IRC14:02
ajolet's start by open bugs.14:02
ajo#topic bugs14:02
*** openstack changes topic to "bugs (Meeting topic: neutron_qos)"14:02
ajonjohnston was pinging me about one of them14:02
*** abalutoiu has quit IRC14:02
*** moshele has joined #openstack-meeting-314:02
openstackLaunchpad bug 1564820 in neutron "DSCP rules won't get updated on ports" [Medium,In progress] - Assigned to Nate Johnston (nate-johnston)14:03
ajoI need to review the code but anybody feel free to do it, it's probably ready14:03
njohnstonit has one +2 already, so I am hopeful14:03
openstackLaunchpad bug 1563720 in neutron "Bandwidth limiting for linuxbridge agent works for ingress traffic instead of egress" [High,In progress] - Assigned to Slawek Kaplonski (slaweq)14:04
ajoslaweq is working on this other one, I think it's probably ready14:04
ajoeven though I have a -1 set on it14:04
ihrachysajo: is it backportable?14:04
ajoihrachys, yes, made as backportable14:04
ajono db changes, no new config, and it clears any old wrong policy14:05
*** tomasztrebski has joined #openstack-meeting-314:05
ajoon the ports via tc..14:05
ajoI found something interesting, that I saw once in old Centos7 kernels14:05
ihrachysajo: + cleanup14:05
ajopolicing does not work well on ubuntu trusty14:05
ajoI'm investigating if it's a kernel issue, a sysctl issue, a hypervisor level issue, or ... a TCP client issue14:06
ajoso we can document it properly,14:06
ajoyou set for example an egress limit of 1Mbps, 100kbs burst,14:06
ajoand, egress speed never reaches 1Mbps,14:06
ajoit stays low at 100kbps14:07
ajobecause TCP does not adapt properly14:07
ajomy faded memories tell me it's a tcp client issue, because when I saw that long ago with the old centos kernel, I found that connecting via ext net from an OSX, windows, etc... it worked as expected14:07
ajoeven on the same hypervisor14:08
*** mtanino has quit IRC14:08
*** numan_ has joined #openstack-meeting-314:08
ajobut, I'm verifying all the combinations to make sure the feature is robust14:08
openstackLaunchpad bug 1507761 in neutron "qos wrong units in max-burst-kbps option (per-second is wrong)" [Low,In progress] - Assigned to Slawek Kaplonski (slaweq)14:09
ajoslaweq doesn't seem to be around14:09
*** zz_dimtruck is now known as dimtruck14:09
ajothat may need more reviews:14:10
ihrachysajo: ok, I just assume that ^ is backwards compat for API14:10
ajoyes, I have to review again to make sure it is14:10
ihrachysnice on avoiding alembic too14:10
ajowell, api tests may prove it14:10
ihrachysI see we modify api tests14:11
ihrachyswe should leave them as is, and add more scenarios using new name14:11
ihrachysthat would prove we don't break anyone14:11
ajoihrachys: +1, yes, I was expecting what you said14:11
ajohdaniel, ping14:11
ajosorry, I can't jump to RFE's yet :) I was about to do it :)14:12
ajowe also have14:13
openstackLaunchpad bug 1515533 in neutron "QoS policy is not enforced when using a previously used port" [Low,Incomplete]14:13
ajowith this patch:14:13
ajoBhalachandra Banavalikar14:13
ajoanybody knows what his nick is?14:14
*** rpjr has joined #openstack-meeting-314:14
*** toddjohn has joined #openstack-meeting-314:14
ajoI'm not convinced about the fix, I just belive it's masking another error14:14
ajoor there's a corner case I'm not seeing14:14
ajoI left him another message on the review14:15
ajoany other bug to be noted?14:16
njohnstonThere are also a couple of DSCP follow-up changes that don't have corresponding bugs, but they are both waiting to respond to negative feedback.14:16
* ajo reads14:17
ajoahh, I see that Margaret is waiting for a response from me on first one14:17
ajoand davidsha is working on second one14:18
ajo#action ajo help margaret with reviews on
ajoI know ihrachys is working with davidsha on the 2nd one but I'll have a read too14:18
ajoI also see this one abandoned:14:19
openstackLaunchpad bug 1486607 in neutron "tenants seem like they were able to detach admin enforced QoS policies from ports or networks" [Low,Confirmed]14:19
ajoif somebody has time to rebase and take ownership of ^14:19
ajoit's been abandoned for 4 weeks now14:19
ihrachyswhy is it low?14:19
*** rbak has joined #openstack-meeting-314:19
njohnstonyeah, I'll take a look at it14:19
ajoihrachys, commit message is wrong14:20
ajoihrachys, tenants are not able to do it14:20
ihrachysah ok14:20
ihrachysit's API response that is wrong?14:20
ajoihrachys, they just seem to be able to do it, server says OK, but does nothing14:20
ihrachysthen it's Normal I think, not Low14:20
njohnstonI don't have the ability to un-abandon it, I think I need a core for that14:20
ihrachyssince API misbehaves14:20
ajonjohnston: restored14:20
ajothanks a lot14:20
njohnstonsure thing!14:21
ajoihrachys, can you raise the bug prio?14:21
ajosorry, I did it myself14:21
ajostupid thing to ask for, it was just a click ':D14:21
ajook, RFE's14:23
ajoafaik, haim is teaming up with davidsha to look at14:23
ajo#topic RFEs14:23
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"14:23
openstackLaunchpad bug 1527671 in neutron "[RFE] traffic classification in Neutron QoS" [Wishlist,Incomplete]14:23
ihrachysajo: I assume the first step is getting neutron-classifier repo in shape?14:24
ihrachysajo: or do we shortcut?14:24
ajothe traffic classification lib is probably immature yet, so we may need to push it to make sure we can do it14:24
ajoI would not shortcut14:24
ajolet's do things right14:24
*** rhochmuth has joined #openstack-meeting-314:24
ajoif we have to help with that effort, let's do it first14:24
ajoand then we use it for qos14:24
ajoihrachys, does that sound reasonable?, or too ambitious for a goal? :)14:25
ajo(or even too optimistic)14:25
ihrachysI won't have time for that specifically, but I can help somewhat if it's using objects ;)14:25
ihrachysI am fine for the right thing. it may take time14:25
ajoihrachys, we will have to use objects, since we will need to push the rules with traffic classification stuff to agents14:25
ihrachysI am open to review object stuff14:25
ajogood :)14:26
openstackLaunchpad bug 1560961 in neutron "[RFE] Allow instance-ingress bandwidth limiting" [Wishlist,Confirmed] - Assigned to Slawek Kaplonski (slaweq)14:26
ajoslaweq took that one :)14:26
*** mrmartin has quit IRC14:26
ajoand hdaniel may team with him too, OVS and LB low level code for that is ready14:26
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,Confirmed]14:27
ajoI filled that one,14:27
ajoand it's been scoped to only egress traffic to start,14:27
ajosince it's the one that can happen with no integration with external stuff to the hypervisor (gateways, other nodes, etc)14:28
*** itoader has quit IRC14:28
hdanielajo: hi, /me got confused by that daytime savings thing14:28
ajohdaniel, np :)14:28
*** mrmartin has joined #openstack-meeting-314:28
ajofor min_bandwidth in OVS14:28
ajoI had an action pending from last meeting14:28
ajoand it was checking that set_queue openflow action was useful to us14:29
ajoin contrast to action=enqueue:<queue-id>:port14:29
ajowhich had to be only in the output action (final rule)14:29
*** yamamoto has joined #openstack-meeting-314:29
ajoand it was hard to integrate for example with "NORMAL" rules14:29
ajowhere the switch decides the output port based on his arp tables14:29
ajoI checked it,14:30
ajoand it works14:30
ihrachyshaleyb: thanks for caring about stable14:30
*** mrmartin has quit IRC14:30
ihrachyswrong channel14:30
ajoso, it should be rather easy to implement now in OVS / openflow :)14:30
ajoI thank haleyb too :D (lol) :)14:30
* njohnston applauds haleyb14:30
ajowe may need somebody to look at how to implement min bw guarantees in linuxbridge if that's possible14:31
*** matrohon has quit IRC14:31
* haleyb is just doing his job14:31
ajothere's a 2nd step of such RFE (probably needs to be addressed later), which is, integrating with nova scheduling :)14:31
*** Swami has joined #openstack-meeting-314:31
*** witek has joined #openstack-meeting-314:31
ajothey're working on the generic pools , which we may eventually leverage when it's ready14:32
*** Swami_ has joined #openstack-meeting-314:32
ajobut there are still some incognitas14:32
*** Swami_ has quit IRC14:32
*** Swami has quit IRC14:32
ajoI'm talking about:14:32
*** Swami has joined #openstack-meeting-314:32
ajo#action ajo send an email to openstack-dev talking about this topic14:33
*** dedery_ has joined #openstack-meeting-314:33
*** cloudtrainme has quit IRC14:33
ajoWe need to provide feedback to resource-providers-scheduler ... to make sure we find a good method for the nova scheduler14:33
ajoto make interpretations out of our ports & policies14:33
*** nkrinner has quit IRC14:33
ajoto determine the min-bw requirements, necessary for strict min-bw scheduling14:33
*** sagar_nikam has quit IRC14:34
ajoihrachys and I believe the interpretation of such things may not correspond to nova, and may be the thing could be pluggable14:34
ajoso we could provide something to pull the right objects from neutron, and make a good interpretation of the port14:34
ajoanother approach, could be14:34
ajo( ihrachys correct me if I got you wrong, of course, ^ )14:35
ihrachysajo: I will correct you on the email :P14:35
ajolol :)14:35
ihrachysajo: but it seems ok14:35
ajoanother approach to this14:35
*** hosanai has joined #openstack-meeting-314:35
*** flwang1 has quit IRC14:35
ajocould be... neutron makes the interpretation on a "port read" or "port create with a policy"... and returns a field with the min-bw required14:35
ajoso nova does not need to call us back, or get a policy, or anything14:36
ajobut I'm not sure about how restful that is14:36
ajowe may need to discuss such thing with the community, or salvatore (api-wg contact point)14:36
*** vijendar has joined #openstack-meeting-314:37
*** dedery has quit IRC14:37
*** hosanai has quit IRC14:38
ajoanybody wants to mention any of the other RFEs / any update on them?14:39
reedip__Well... want to know the next step14:39
openstackreedip__: Error: Could not gather data from Launchpad for bug #1505627 ( The error has been logged14:40
reedip__Why do weird things happen with me ??14:40
*** sigmavirus24_awa is now known as sigmavirus2414:40
*** bklei has joined #openstack-meeting-314:41
reedip__ajo : spec can be started once confirmation from drivers team is obtained14:41
ajoI'm not sure reedip__ we may need to answer amotoki's question14:41
reedip__that would probably help amotoki's answers as well14:41
ajoI will talk to him about this RFE, and see where we  go14:42
*** sdake_ has joined #openstack-meeting-314:42
*** sdake has quit IRC14:42
ajo#action discuss with amotoki, and provide the high level details14:42
openstackLaunchpad bug 1505627 in neutron "[RFE] QoS Explicit Congestion Notification (ECN) Support" [Wishlist,Confirmed] - Assigned to Reedip (reedip-banerjee)14:42
reedip__ok, then I will go the other way round, answering amotoki's questions first and then progressing forward....14:42
*** sdake_ is now known as sdake14:43
ajosaid that, I'm not sure the high level details were clear after our last conversation14:43
reedip__see... It worked when you typed... Launchpad hates me14:43
ajomay be we could ask them for permission to work on a more detailed spec14:43
ajoso we can clarify top/down of it14:43
reedip__ajo : maybe14:43
ajobug comments become to messy .. ':D14:43
reedip__but they are currently more concerned about high level view14:43
ajoreediip__ of course, that's the first thing that needs to be clear14:44
ajoreedip__ you could provide a use case, of how to setup the rules exactly14:44
ajoand how those would work14:44
reedip__Ok, I will put up my response in the etherpad , along with some possible use cases14:44
amotokisome detail looks good but i could not capture what kind of features are exposed honestly14:44
reedip__amotoki has put up these questions on etherpad as well, so I think we can start modelling it as a spec14:45
ajoreedip__ if you can put on the rfe summary something like the neutron cli rule creations, etc..14:45
ajoand the expected behaviour of the set rules14:45
ajothat may help too14:45
*** JeanBriceCombebi has quit IRC14:45
amotoki(note that meeting bot seems in some trouble during the last week meeting.... no log...)14:46
ajoyikes :/14:46
ajomay be I used a wrong meeting id?14:46
reedip__amotoki: means I need to copy this stuff after the eeting ends14:46
ajoI will check my logs14:46
amotoki(no log around ECN dsicussion)14:46
njohnstonI see logs:
ajo#addchair ihrachys14:47
ajodoes it work like that? :)14:47
ajoI need to leave and I see there could be conversation here about ECN14:47
reedip__njhonston is right.. logs are being generated14:47
*** vijendar has left #openstack-meeting-314:47
*** sdake_ has joined #openstack-meeting-314:48
ajo#chair ihrachys14:48
openstackCurrent chairs: ajo ihrachys14:48
*** sinval-afk has quit IRC14:48
ajo#chair amotoki14:48
openstackCurrent chairs: ajo amotoki ihrachys14:48
ajo#chair njohnston14:48
openstackCurrent chairs: ajo amotoki ihrachys njohnston14:48
reedip__musical chairs...14:48
* njohnston is honored14:48
ajoguys, can you #endmeeting once this is over? :)14:48
amotoki??? what's happening14:48
ajoI need to leave14:48
njohnstonsure thing14:48
ihrachysajo: ? I am not sure what you mean. you leave us in the middle of the thing?14:49
*** Sonu has quit IRC14:49
*** flwang has joined #openstack-meeting-314:49
amotokilog jumps 14:08:24 to 14:24:02 in the meeting log Mar 23...14:49
njohnstonamotoki: That is not the log for today (4/6), that is the log for 3/23.14:49
ihrachysajo: just stop the meeting if we loose a chair. I am not in position to lead it.14:49
*** sinval-afk has joined #openstack-meeting-314:49
njohnstonI can lead it.14:50
amotokiyes. I tried to caputre the discussion mentioned in the rfe bug discussed now.14:50
davidshaamotoki: means that there is about 16 mins of log missing it appears14:50
amotokisorry for disturb. go ahead14:50
reedip__Thankfully I have logs to my disk :)14:50
*** sdake has quit IRC14:51
*** salv-orlando has joined #openstack-meeting-314:51
reedip__anyways, so as discussed with ajo regarding the ECN bug, I will respond to amotoki's questions, present some possible use cases14:51
reedip__and expected behavior14:51
njohnstonAre there any other RFEs to discuss?14:51
reedip__not from my side...14:51
*** sc68cal has joined #openstack-meeting-314:51
*** shinya_kwbt has joined #openstack-meeting-314:51
njohnstonOK, then let's move on to open discussion14:52
njohnston#topic Open Discussion14:52
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"14:52
njohnstonDoes anyone have anything else they would like to discuss?14:52
*** rbrndt_ has joined #openstack-meeting-314:52
reedip__Do we have a session ( fishbowl or other) decided yet ?14:52
reedip__in Austin summit?14:52
reedip__just a query off the top of my head14:52
davidshaline 21, has 3 topics for discussion14:53
reedip__davidsha ; yeah I saw that earlier today :)14:53
njohnstonYes, QoS has an entry in the list, but I haven't seen any announcement from armax on what ideas will be assigned to the available session slots.14:53
njohnstonThat being said, I think there is enough interest in QoS that I feel confident we will get one of the sessions.14:54
reedip__okay ... just what I wanted to know14:54
reedip__nothing else... thanks14:54
*** mtanino has joined #openstack-meeting-314:54
davidshaIs there anyone working on something at the moment that uses Openflows actually? I have an entry for discussing flow management and I'm interested in more use cases.14:55
njohnstondavidsha: Is tmorin working on something in the networking-bgpvpn space?14:55
njohnstonI know he reached out to you.14:55
davidshanjohnston: ya, I was talking to him. he said he'd be interested in coming to it. just trying to deploy bgpvpn atm!14:56
ihrachysdavidsha: sfc?14:56
*** hosanai has joined #openstack-meeting-314:56
njohnstonWell, we are almost out of time, does anyone have anything else they would like to raise?14:57
davidshaihrachys: I was talking to someone from sfc but they may have stepped back from the community, I'll ask some more. there is tap-aas as well but sfc and t-aas haven't implemented the l2-agent api yet14:58
ihrachysdavidsha: that's probably something to consider when (not) keeping them in stadium14:58
njohnston+1 to that14:59
ihrachysdavidsha: they should be expected to consume best practices from core14:59
*** bmotz has joined #openstack-meeting-314:59
*** yamahata has quit IRC14:59
reedip__davidsha : taas  l2-agent api is my AI :)14:59
ihrachysAI == ?14:59
reedip__would be great if you can give some tips14:59
reedip__Action Item14:59
*** tgraichen has joined #openstack-meeting-314:59
reedip__I am helping TaaS...14:59
njohnstonreedip: Excellent!14:59
njohnstonAll right, I have to call time.15:00
*** openstack changes topic to "npm lint jobs are failing due to a problem with npm registry. The problem is under investigation, and we will update once the issue is solved."15:00
njohnstonThanks all.15:00
openstackMeeting ended Wed Apr  6 15:00:11 2016 UTC.  Information about MeetBot at . (v 0.1.4)15:00
openstackMinutes (text):
*** iyamahat has quit IRC15:00
*** Kamil_ has joined #openstack-meeting-315:00
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Apr  6 15:00:30 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at
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
rhochmuthLink to agenda is at,
rhochmuthAgenda for Wednesday April 6, 2016 (15:00 UTC)15:01
rhochmuth1. Replace agent thread pool
rhochmuth2. monasca-transform15:01
rhochmuth3. monasca-analytics15:01
rhochmuth4. Summit scheduling15:01
rhochmuthHi everyone15:01
*** mbound has quit IRC15:01
rhochmuthIt has been a crazy week for mee15:01
*** slogan has joined #openstack-meeting-315:01
*** mbound has joined #openstack-meeting-315:01
*** sigmavirus24 is now known as sigmavirus24_awa15:02
rhochmuthThere is a small agenda today, so it looks like we'll have time for other topics15:02
tomasztrebskieven crazier for me....15:02
*** gema_ has joined #openstack-meeting-315:02
rhochmuthshinya, thank you for fixing the problem with the nodejs install in Grafana last night15:02
*** cartik has joined #openstack-meeting-315:02
shinya_kwbtNot at all15:03
rhochmuthi've merged it and it is in flight15:03
sloganI ended up simply doing a sudo apt-get install nodejs and it all worked, nothing complicated. What was the fix?15:03
*** sigmavirus24_awa is now known as sigmavirus2415:03
rhochmuthi had done something similar myself yesterday, but hadn't posted it yet15:03
rhochmuthThe reivew hasnt' merged yet, but it is at,
*** jobrs has joined #openstack-meeting-315:04
rhochmuthOn a related topic, I tried the Monasca plugin for the Logging API/Service yesterday15:04
rhochmuthThe review is at,
rhochmuthI haven't really looked at the code15:05
rhochmuthjust tried using it along with MOnasca15:05
rhochmuthIt appears to work15:05
rhochmuthAt least Kibana comes up15:05
witeknice to hear! :)15:05
tomasztrebskiI saw you posted a comment about default index, did you manage to resolve that ?15:05
rhochmuthI left a comment15:06
rhochmuthno, i haven't resolved that15:06
rhochmuthif you know the magic, let me know15:06
rhochmuthso, i'm not sure it is working completely, but at least it installs and runs15:06
tomasztrebskiI'll respond to that, it just Kibana does not know what would like to display, so it needs an index name or a pattern to read from15:06
witekthe index pattern should be tennantid-YYYY-MM-DD15:06
*** julim has joined #openstack-meeting-315:06
rhochmuthok, thanks15:06
rhochmuthi'll need to get tsv to start looking into it15:07
rhochmuthit is really cool to see all this stuff, Monasca, Horixon, Grafana and ELK all running in the same DevStack VM15:07
rhochmuthThat is going to make the Bootcamp session on Monasca much more enjoyable15:08
rhochmuthSo, thanks everyone for helping to get that working15:08
*** davidsha has left #openstack-meeting-315:08
rhochmuthI'm assuming it will be used in other sessions too15:08
rhochmuthNow, i need to get the Ceilosca stuff working15:09
*** mbound has quit IRC15:09
rhochmuth#topic Replace agent thread pool
*** openstack changes topic to "Replace agent thread pool (Meeting topic: monasca)"15:09
rbakThat's me15:09
rhochmuththat u15:10
rbakThis patch has been up for a few days and I just wanted to get some eyes on it.15:10
rhochmuthi know some folks on the team here at hpe have started to look at it15:10
rhochmuthbut, i see that they haven't left comments15:10
*** cloudtrainme has joined #openstack-meeting-315:10
rhochmuthwe are pretty busy with a release right now15:10
rhochmuthbut, i'll ping them15:11
rbakAs long as someone's looking at it.15:11
*** absubram has joined #openstack-meeting-315:11
rbakThe agent locking up has been a problem for us for a while15:11
rhochmuthwe were wondering if we wanted to pick it up for the release15:11
rhochmuthhow urgent is tis to resolve on your end15:11
rhochmuthhow soon are you looking to get merged15:12
rbakI'd like to get it as soon as possible.  We're opening our service up to customers so they're going to see the holes in our data where agents locked up.15:12
*** mickeys has joined #openstack-meeting-315:12
rhochmuthhow long have you been testing this change15:12
rbakBut I know it's a big change, so I don't want to rush it if someone isn't comfortable15:13
sloganI started looking at it a day or two ago, but got distracted - but looks good +115:13
rhochmuthwell, i think that was the concern for us15:13
*** JOlsen has joined #openstack-meeting-315:13
rbakI've had it running for a couple days at least with no problems.15:13
rhochmuthcool, that is good info15:13
rhochmuthhave you seen any memory growth15:13
rbakAnd it does recover when checks get stuck.15:14
rhochmuthresource leaks?15:14
rbakNothing I've noticed so far.15:14
rhochmuthok, i'll let joe and other know15:14
*** mickeys has quit IRC15:14
rhochmuthi've added joe to the review and will add some others15:14
rbakI haven't looked recently though, I'll go back and see how the resources are looking.15:14
*** vgridnev has quit IRC15:15
*** mickeys has joined #openstack-meeting-315:15
rbakI don't have anything more on that subject.  I'll post an update on the patch.15:16
rhochmuth#topic monasca-transform15:16
*** openstack changes topic to "monasca-transform (Meeting topic: monasca)"15:16
*** belmoreira has quit IRC15:17
rhochmuthSo, I've posted a review at,, for monasca-transform15:17
rhochmuthThe monasca-transform project is a new component in Monasca that15:17
rhochmuthwill aggregate and transform metrics. For example, it will consume15:17
rhochmuthmetrics for Swift from the Monasca metrics topic and count the total15:17
rhochmuthnumber of times a container or object is accessed and group them by15:17
rhochmuthproject. Then it will publish the aggregated metric to the Kafka15:17
rhochmuthmetrics topic where the rest of the existing Monasca components15:17
rhochmuthwill be used to store, alarm and notify.15:17
rhochmuthThis component has been in the architecture diagram for a long time, and we've talked about it in the past15:17
*** vgridnev has joined #openstack-meeting-315:17
rhochmuthBut, it looks like we're going to get some resources fomr HPE to work on this15:18
rhochmuthI would like to get this reviewed next week15:18
rhochmuthIf that is OK with everyone15:18
rhochmuthBasically, go over uses cases, architecture, design, …15:19
rhochmuthThe goal is to complete this component by the Newton release or sooner15:19
*** mickeys has quit IRC15:19
tomasztrebskiis it this one -> ?15:19
*** annegentle has quit IRC15:19
rhochmuthNo, that was targeted at events15:20
rhochmuthThis is for metrics15:20
rhochmuthTotally new repo15:20
rhochmuthwill be created15:20
sloganthe use cases would be interesting to read15:20
sloganwhere can we find more info?15:20
rhochmuthIt is being created and will publish and review next week15:20
*** bpokorny has joined #openstack-meeting-315:20
rhochmuthThey've created proto code15:21
*** annegentle has joined #openstack-meeting-315:21
rhochmuthSo, are folks OK covering this next week, or shoudl we arrange another time-slot15:21
rhochmuthit might take a while to get through the entire topic15:22
*** salv-orlando has quit IRC15:22
witeksome document would be nice15:22
rhochmuthok, it is on the way15:23
rhochmuthhopefully, others will want to work on this too15:23
rhochmuthwhat does that mean?15:23
tomasztrebskinothing bad, I would want to see how this one work and fits in everything else :D15:24
rhochmuthyes, that is the plan15:24
rhochmuth#topic monasca-analytics15:25
*** openstack changes topic to "monasca-analytics (Meeting topic: monasca)"15:25
rhochmuthSo, I'll also be submitting a request for a new repo for the alarm clustering and anomaly detection work that we've been starting to discuss again15:25
hosanainice :-)15:26
rhochmuthAs soon as I get monasca-transform done, i'll submite monasca-analytics15:26
rhochmuthwhich shoudl go smooth15:26
rhochmuthhosanai, sorry about the delay15:26
hosanairhochmuth: np!15:26
rhochmuthbut, i'm getting to it15:26
*** armax has joined #openstack-meeting-315:27
rhochmuthat some point, we can also do a similar review, but much less is known about this area right now15:27
rhochmuthmaterials are being created, but it is much more complicated15:27
rhochmuthcurretly, hosanai, a small team in hpe, and me are interested in this area15:28
rhochmuthso, look for that15:28
sloganwhat is alarm clustering?15:28
rhochmuthi just didnt' want to surprise anyone15:28
rhochmuthhosanai, do you want to explain?15:28
sloganI we talking k-means type of thing?15:28
tomasztrebskimaybe once you have all these materials available (use cases, documentation of some sort), you could post a mail via mailing list to notify everyone, just when it is ready15:28
rhochmuthsure tomasz, will do15:29
sloganthat would be good15:29
*** sdake has joined #openstack-meeting-315:29
sloganI'm so focused on the lowest level, I need to surface and see the bigger picture15:29
hosanaiok, my typing speed is not enough15:29
rhochmuthhosanai, can you explain alarm clustering, or do you want me to describe?15:29
hosanairhochmuth: could you explain it?15:30
*** sdake_ has quit IRC15:30
rhochmuthcurrently, many alarms can occur simultaneousely15:30
*** bpokorny has quit IRC15:30
rhochmuthFor example, if a system goes down15:31
rhochmuthall the alarms on that system, will fire15:31
rhochmuthThe idea is to cluster alarms temporally and based on other features of the metrics/alarms15:31
rhochmuthto reduce the number of alarms and reduce alarm fatigue15:32
rhochmuthSo, instead of 100s of alarms, you would get a few.15:32
sloganI see, so, selected attributes and ranges define membership in a cluster15:32
*** moshele has quit IRC15:32
sloganyou get told about the cluster, and can peel the onion for details later15:32
rhochmuthK-means woudl be one way to do the clustering15:33
rhochmuthbut, i don't think that is what is planned right now15:33
sloganSOM :-)15:33
rhochmuthTHere are two companies that do this that i'm aware of15:33
rhochmuthBig Pandas15:33
*** moshele has joined #openstack-meeting-315:33
rhochmuth#topic Summit scheduling15:34
*** openstack changes topic to "Summit scheduling (Meeting topic: monasca)"15:34
*** annegentle has quit IRC15:34
rhochmuthCurrently, we have five sesions at the design summit for Monasca related discussions15:34
rhochmuthAll are Wednesday from 9:00 - around 1:0015:34
rhochmuthThere is a stop for lunch15:35
*** moshele has quit IRC15:35
*** annegentle has joined #openstack-meeting-315:35
slogan40 minute or so sessions I guess15:35
rhochmuthThe first session will be general overview, planning and roadmap15:35
rhochmuthThe second session will be more deetailed discussions on specific features, siuch as multiplke metrics, non-periodic metrics, periodic notifications, retention periods, …15:36
rhochmuthThird session will be logging API/service15:36
*** ddieterly is now known as ddieterly[away]15:36
rhochmuthFourth session will be Networking/Neutron/Broadview15:36
rhochmuthFifth session is still available15:37
rhochmuthSorry, should have said that is my proposal, at this point15:37
rhochmuthNothing has been defined and set in stone15:37
rhochmuthSo, I'm wondering if that sounds reasonable15:37
rhochmuthI know a lot of folks won't be there15:38
witeksounds good for me15:38
slogansounds reasonable, I'm more likely to get travel permission if it becomes set in stone.15:38
rhochmuthI'll check with Armando on the Networking/Neutron discussion15:38
slogan(that sigh is with my side, not you)15:38
*** dwalleck has joined #openstack-meeting-315:39
rhochmuthBut, i think it is all set15:39
rhochmuthi'll confirm15:39
sloganI'll go ahead and tell my manager I have to be there, you can back me up if needed15:39
sloganwe need this discussion to happen15:39
rhochmuthi think you should attend all the Neutron sessions, which there are a lot of, and thety don't overlap with Monasca15:40
*** sdake_ has joined #openstack-meeting-315:40
*** ddieterly[away] is now known as ddieterly15:40
rhochmuthInterfacing with that team would be great15:40
*** cloudtrainme has quit IRC15:40
*** Swami_ has joined #openstack-meeting-315:41
slogantotally agree15:41
*** armax_ has joined #openstack-meeting-315:41
rhochmuthso, unless i hear otherwise, that is the working plan at the moment15:42
*** armax has quit IRC15:42
*** armax_ is now known as armax15:42
rhochmuthhosanai, i was wondering about using the fifth slot for anomaly/analytics related discussions15:42
rhochmuthi'm just not sure who else is interested in that topic15:42
*** banix has quit IRC15:42
rhochmuthi am up for discussions while you are there15:43
*** julim has quit IRC15:43
*** sdake has quit IRC15:43
hosanairhochmuth: that is the point. i'm availeble in there15:43
*** cloudtrainme has joined #openstack-meeting-315:43
*** banix has joined #openstack-meeting-315:44
hosanaiif we have 5th slot and get more attention for it. we can have the slot. maybe...15:44
*** bpokorny has joined #openstack-meeting-315:44
rhochmuthi agree,15:44
rhochmuthbut usually, you need the interest first, before scheduling the session15:45
*** Swami has quit IRC15:45
rhochmuthi could leave the session open, with analytics as one of the topics to discuss in more detail15:45
rhochmuthdependent on interest15:46
*** dedery has joined #openstack-meeting-315:46
hosanaisounds nice!15:46
rhochmuthso, that sounds like a reasonable plan15:46
*** rpjr has quit IRC15:46
rhochmuthi'll leave it an open session with some suggested potential topics dependent on interest15:46
rhochmuthand we can refine while we are there15:47
*** cartik has quit IRC15:47
rhochmuthsound good?15:47
rhochmuthSo, we've got around 10 minutes left15:48
rhochmuthi'll just open it up for discussion15:48
rhochmuth#topic general discussion15:48
*** openstack changes topic to "general discussion (Meeting topic: monasca)"15:48
*** numan_ has quit IRC15:48
tomasztrebskiI wanted to clarify this change =>
witekit would be great if Craig could have a look at our monasca-thresh chage15:49
tomasztrebskiand that too15:49
*** dedery_ has quit IRC15:49
*** yamahata has joined #openstack-meeting-315:49
rhochmuthcraig has been extremely busy on a release, so his reviews have been a bit delayed15:50
rhochmuthas have mine15:50
rhochmuthso, i'm hoping he'll start to free up here today/tomorrow15:50
*** rpjr_ has joined #openstack-meeting-315:50
*** andymaier has quit IRC15:50
rhochmuthi'll ping him too15:50
*** dedery has quit IRC15:50
witekthank you15:50
*** dedery has joined #openstack-meeting-315:51
*** Sukhdev_ has joined #openstack-meeting-315:51
rhochmuthso, are there other topics15:52
tomasztrebskiI've posted a link above to switch to different partitioner in Kafka15:52
tomasztrebskisince current one is deprecated due to certain bug (#374) in python-kafka15:52
*** salv-orlando has joined #openstack-meeting-315:53
rhochmuththat looks interesting15:53
*** tgraichen has quit IRC15:53
rhochmuthjoe, will want to take a look at that15:53
sloganrhochmuth: I ust got my travel approved, definitely there15:53
*** tonytan4ever has quit IRC15:54
rhochmuththanks slogan15:54
*** dedery_ has joined #openstack-meeting-315:54
rhochmuthmaybe it was my comments in this irc session?15:54
*** tonytan4ever has joined #openstack-meeting-315:54
sloganI pasted them in the e-mail, yes15:54
*** dwalleck has quit IRC15:54
rhochmuthAlso, I wanted to point out this review again,
rhochmuthRyan Brandt has been working on that one, and I beleive he thinks it is ready to go15:55
*** dwalleck has joined #openstack-meeting-315:55
rhochmuthSupport for both InfluxDB and Vertica are complete15:55
*** dedery has quit IRC15:55
rhochmuthAlthough, the review is in merge conflict right now15:55
*** salv-orlando has quit IRC15:56
*** catherineD has joined #openstack-meeting-315:56
*** Rockyg has joined #openstack-meeting-315:56
rhochmuthOn another note, just want to mention that we are not proceeding with Cassandra support at this point15:57
*** rbak_ has joined #openstack-meeting-315:57
rhochmuthWe will take a wait and see approach, and revisit based on customer interest15:57
rhochmuthit is a lot of work15:57
*** salv-orlando has joined #openstack-meeting-315:58
rhochmuthinfluxdb satisfies the open-source requirement15:58
witekthanks for info15:58
rhochmuthif anyone else wnat to work on, we would be completely opne to the submission15:58
rhochmuthso, we're not going to prevent development in this area15:59
*** yamahata has quit IRC15:59
rhochmuthwe're just not going to be able to staff it right now15:59
shinya_kwbtI want to try15:59
*** yamahata has joined #openstack-meeting-315:59
rhochmuthshinya: you want to try cassandr?15:59
*** rbak has quit IRC15:59
rhochmuthok, i need to end the meeting?16:00
shinya_kwbtYes But I don't know cassandra so I must study hard16:00
rhochmuthok, sounds good16:00
rhochmuththere were some reviews that were in progress16:00
rhochmuthgot to go now16:00
hosanaithanks& bye16:00
rhochmuth#endmeeting monasca16:00
*** openstack changes topic to "npm lint jobs are failing due to a problem with npm registry. The problem is under investigation, and we will update once the issue is solved."16:00
openstackMeeting ended Wed Apr  6 16:00:54 2016 UTC.  Information about MeetBot at . (v 0.1.4)16:00
openstackMinutes (text):
markvoelker#startmeeting defcore16:01
*** hosanai has left #openstack-meeting-316:01
openstackMeeting started Wed Apr  6 16:01:04 2016 UTC and is due to finish in 60 minutes.  The chair is markvoelker. Information about MeetBot at
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
*** bklei has quit IRC16:01
markvoelker#chair eglute16:01
openstackCurrent chairs: eglute hogepodge markvoelker16:01
dwallecko/ (in another meeting, but here!)16:01
*** Kamil_ has quit IRC16:01
markvoelker#link Today's Agenda16:01
*** kzaitsev_mb has quit IRC16:02
*** gema_ is now known as gema16:02
*** iyamahat has joined #openstack-meeting-316:02
markvoelkerPlease take a quick look through the agenda and make sure we're not missing anything folks16:02
markvoelker#topic Straw Man Proposal for DefCore Owning DefCore Tests in Tempest16:03
*** openstack changes topic to "Straw Man Proposal for DefCore Owning DefCore Tests in Tempest (Meeting topic: defcore)"16:03
markvoelker#link Strawman proposal16:03
*** slogan has quit IRC16:03
markvoelkerhogepodge posted this yesterday so I'll let him speak to it. =)16:03
markvoelkerAs a general note, you are all (as usual) encouraged to please provide your input in Gerrit.16:04
hogepodgeThe blueprint has a couple of intents. The first is to solidify the relationship with the QA team by marking defcore tests, approved by the board, as important.16:04
markvoelkerhogepodge: around?16:04
markvoelkeryes you are =)16:04
hogepodgeWe've had friction in the past about test names changing, functionality changing, and playing a bit of catch up and writing tooling to work around the changes.16:05
hogepodgeI'm not sure it's a part of the proposal that would pass, especially using a defcore named tags. This is in part because tempest doesn't necessarily want outside influence on the project like this, but they're not 100% opposed to it either. Particularly with regards to tags that indicate a property16:06
hogepodgedo defcore-required may be bad? interop may be good?16:06
*** cartik has joined #openstack-meeting-316:07
hogepodgeIt's starting a dialogue there, which I feel is important.16:07
hogepodgeSecondly it's encoding some of the requirements we talked about at the previous meeting for a spec that defines "interop" test16:07
dwalleckhogepodge:: ++, dialog is good16:07
hogepodgeI tried to write down the minimal things we could reach consensus on, but is a work in progress. I would expect that an official spec would be part of the defcore repository.16:08
*** cloudtrainme has quit IRC16:08
*** eddie_lechtus has quit IRC16:08
eglutehogepodge i do not recall us having consensus on tagging16:08
*** SammyD has joined #openstack-meeting-316:08
hogepodgeAgain, it's trying to encode a relationship, saying that we take responsibility for maintaining, along with qa, what an interop test looks like.16:09
dwalleckhogepodge: Does it really encode though? It's a decorator, but it doesn't enforce anything directly16:09
hogepodgedwalleck: it puts meaning in code, backed by a spec.16:09
*** annegentle has quit IRC16:09
dwalleckBut it does start a dialog. It does add a burden to Tempest reviewers to understand all the things that interop means (single user, etch)16:10
hogepodgefinally, there is talk of forking tempest. I am strongly opposed to that, and personally feel it is harmful to both our aims as a standard body and to the community at large16:10
eglutewe do not have the specs yet. this is jumping ahead and making assumptions what the spec would look like16:10
* docaedo arrives a little late to lurk :)16:10
*** shinya_kwbt has left #openstack-meeting-316:10
hogepodgeeglute: we do have an informal spec. For example, tests are not admin. That is a requirement. They must be api, that is also a requirement.16:11
*** kzaitsev_mb has joined #openstack-meeting-316:11
dwalleckhogepodge: But that's a spec for what attributes a Tempest test should have to be an interop test, which is different from defining an actual spec for capabilities16:12
eglutehogepodge we agreed to work on formal specs first before proceeding further. otherwise we will run into issues again where the test dictates what the spec should be, and not the other way around16:12
dwalleckThe second being the one I thought we had been talking about at the midcycle, but if I'm mistaken, that's okay :-)16:13
hogepodgethe one we talked about at the midcycle?16:13
eglutei agree with dwalleck here, we need to start with defcore specs, not tempest specs16:14
*** annegentle has joined #openstack-meeting-316:14
gemanot sure how much time I can commit to this, but I can have a go at trying to start a spec16:15
*** rbrndt_ has left #openstack-meeting-316:16
gemaI see the tagging as useful regardless, though16:16
gemalike an orthogonal thing16:16
*** banix has quit IRC16:16
eglutegema that would be good. perhaps you could work with dwalleck since he already started on some analysis16:16
hogepodgegema: that would be great16:16
gemaeglute: yep, that was going to be my first task, catch up with dwalleck :D16:16
eglute#action gema and dwalleck to start working on a defcore spec16:17
gemadwalleck: o/16:17
dwalleckgema: Absolutely, I'd be glad to contribute16:17
gemaok, we'll start this week and see how it goes :D16:17
hogepodgeeglute: I would very much like to be involved with what a spec looks like too. As the person who has worked most closely with qa, I'd like us to maintain a good relationship on that.16:17
*** VanL has joined #openstack-meeting-316:17
eglutehogepodge i dont think anyone will be excluded!16:17
gemahogepodge: how about I start a conversation on our mailing tomorrow16:17
gemaand we make it collaborative16:17
gemathen I put the result together on some sort of commit16:18
dwalleckBut which spec are we talking about? The spec for what defines a capability, or the specs of what makes a good interop test?16:18
gemaI thought the spec for defcore16:18
*** bmotz has left #openstack-meeting-316:18
markvoelkerdwalleck: We have Board-approved definitions of Capabilities16:18
gematest spec, that is16:18
VanLdwalleck: Spec for what makes a good interop test16:18
RockygVanL, right16:19
VanLWe have a couple principles that everyone agreed on, IIRC:16:19
dwalleckGotcha, wanted to make sure we were using the same terminology16:19
VanL1. No admin16:19
VanL2. (From Chris:) Two paid accounts not needed.16:19
VanL3. Atomic16:19
VanLI think those were the only ones that we got to before we moved on16:20
VanLI would also suggest:16:20
Rockyg4. available for at least 3 releases16:20
VanL4. The test matches the public documentation16:20
hogepodgeVanL: I object to you using language like "that everyone agreed on". It over simplifies and may not accurately represent my views.16:20
gemahogepodge: I am going to go back to the midcycle notes tomorrow and summarize our discussion on this16:21
gemathen frame the conversation16:21
hogepodgeVanL for example, 3. Atomic, may differ from dwalleck's16:21
VanLRockyg: Yes, but that is a capabilities requirement, not a interop spec.16:21
markvoelkerOne suggestion: let's be careful to not overlap with the Board-approved Criteria we already have.16:21
markvoelker#link Criteria16:21
hogepodgeor 2, when I say two tenant isolated accounts I mean two tenant isolated accounts, not paid accounts.16:21
markvoelkerWe don't want to essentially have two sources of truth about those.16:21
eglute+1 markvoelker16:22
catherineDhogepodge: ++ ... Atomic is the reason causing the issues we have with today's test set16:22
dwalleckhogepodge: that's a fair example. Then we need to drill down into those bits and talk them through and come to a community understanding16:22
VanLhogepodge: Please don't personalize this. I am trying to honestly represent and summarize what I understood, and if the summary isn't accurate, then by all means chime in16:22
hogepodgedwalleck: yes. I agree16:22
*** anilvenkata has quit IRC16:22
*** JOlsen has quit IRC16:22
gemaVanL: no worries, fortunately for everyone my memory is bad, so I will go back and read the notes16:23
VanLI was mostly trying to quote from /summarize the notes16:23
*** vtech has quit IRC16:23
dwalleckMy opinions are my own, but as someone who works in the community and has invested time, I have to share my thoughts, which doesn't mean anyone has to agree16:24
gemadwalleck: ++16:24
markvoelkergema: hogepodge: dwalleck: do you guys have what you need to proceed on drafting something up?16:24
dwalleckI spent a great deal of time working on Tempest and then later on CloudCafe, so I have some strong opinions about tests :)16:24
gemamarkvoelker: I think so16:24
*** kzaitsev_mb has quit IRC16:24
gemadwalleck: me too16:25
gemawe'll have fun :D16:25
*** vgridnev has quit IRC16:25
dwalleckGemma: yup!16:25
*** jschwarz has quit IRC16:25
*** woodster_ has joined #openstack-meeting-316:25
markvoelkerGreat.  I'll look forward to reviewing it then. =)  We're 25 minutes in and have several other agenda items--ready to move on?16:25
eglutemarkvoelker +116:26
markvoelker#topic Capabilities with no tests (or only admin tests)16:26
*** openstack changes topic to "Capabilities with no tests (or only admin tests) (Meeting topic: defcore)"16:26
gemaI'd like to start capturing all of those and make a list16:27
gemaof tests to be created16:27
gemaI have a couple on keystone as well16:27
markvoelkerWe've identified some advisory tests which turn out to require admin creds.  We can't use those in Guidelines, so they'll have to go.16:27
markvoelkerThe biggest question is what to do about it, because the underlying features genereally don't require admin16:28
markvoelkerSo, two things:16:28
*** mickeys has joined #openstack-meeting-316:28
markvoelker1.)  I'm going to spend some time looking for other tests of the same capabilities that don't require admin16:28
markvoelker2.)  I think we should have a chat with the project teams/PTL's/QA teams about potentially changing those tests to not need admin16:28
*** moshele has joined #openstack-meeting-316:29
markvoelkerThose are sort of the natural outcomes...the bigger question is what to with the tests in the meantime since it's uncertain how quickly we could get the tests modified (if that's even realistic...there may be good reasons for using admin)16:29
*** tomasztrebski has quit IRC16:30
catherineD  is an easy one to review  and merge... because the capability affected still have some tests in it after the admin tests are  flagged or removed..16:30
markvoelkerObviously we've got a few months before the Guideline comes up for approval here, so there's potential for us to get things done before then.16:30
*** mrmartin has joined #openstack-meeting-316:30
*** jlanoux has quit IRC16:30
*** ddieterly is now known as ddieterly[away]16:30
markvoelkerFailing that, we could consider leaving the relevant Capabilities in advisory state for another cycle so we don't have to restart the clock by dropping them and then having them go through another advisory cycle16:31
eglutethank you catherineD for calling those tests out. i agree with markvoelker that we need better tests, but also agree that no idea how long this will take16:31
VanLHow much real-world vetting have the advisory capabilities had? Finding admin-requiring tests makes me nervous that they have not been properly vetted by enough people out in the community16:31
eglutei think leaving them advisory would be ok, provided we start working on getting better tests somehow16:32
markvoelkereglute: from a cursory look at a few of them, I think it may be realistic to improve some of these before the Guideline goes up the board, for what it's worth.16:32
catherineDVanL: I have verified all the tests in the advisory section16:32
catherineDand thus found the one with admin requires16:32
markvoelkerVanL: the scoring for them is in the scoring sheet.  They all stacked up to criteria like widely deployed.16:32
*** jtomasek has quit IRC16:33
eglutemarkvoelker i would be really hesitant to make them required if we are going to change the tests16:33
hogepodgemarkvoelker: qa has a history of helping sort the issues out, maybe not in time for a guideline though. They could stay advisory16:33
catherineDThera are also some test records in RefStack that tests the entire API Tempest test that we can use to verify16:33
markvoelkereglute: why so?16:33
VanLmarkvoelker: Sure, but we run into the problem of the *capability* being widely deployed, but the tests to show a capability not being representative or otherwise having problems.16:33
hogepodgemarkvoelker: otherwise they would be immediately flagged, with the action to be to fix or remove. That seems an odd way to start, but it's definitely a workable solution16:33
markvoelkeroh, you mean make the required and then change the tests?  Yeah, definitely.16:33
*** Swami_ has quit IRC16:34
markvoelkerI'm saying we change the tests before we make them required.16:34
markvoelkerRemember that the next Guideline won't get approved for several months yet.  So there's a pretty good window of time here.16:34
hogepodgemarkvoelker: yes, I think that's better (or write new tests if admin is required)16:34
catherineDmarkvoelker: we do have a patch today to move advisory to required16:34
dwalleckBut if a test defines the capability, how can we add a test that we plan on immediately refactoring?16:34
eglutemarkvoelker people that are/could be testing agains this as advisory might be blindsided by new tests. in theory, new tests should test the same stuff, but in reality they might not be exactly the same16:34
catherineDat the mimimum we should flagged those admin tests .... if not removed16:35
*** mickeys has quit IRC16:35
dwalleckIt gives you a placeholder for intent, but I'm not sure what other value it provides16:35
markvoelkereglute: I see the concern.  I think in most cases though, all we'd need to do is modify the existing tests to use ordinary credentials rather than admin ones.  E.g. we're not fundamentally changing what's being tested.16:35
eglutei think keeping them as advisory is a good compromise16:35
dwalleckahh, admin part. Missed that, never mind :)16:36
catherineDeglute: keeping the capability but flagged or removed the admin tests ?16:36
markvoelkercatherineD: keep in mind that even if the patch moving them to required lands, that doesn't actually mean anything until the Board votes on the Guideline in August16:36
eglutekeeping the capability as advisory rahter than making it required16:36
eglutecatherineD ^^16:36
markvoelkercatherineD: until then it's just a draft.  But I'd be fine with dropping those tests from moving right now just for clarity.16:36
catherineDmarkvoelker: agreed but if may make the required in next.json and the advisory in 2016.01 mis-match16:37
catherineDmarkvoelker: agree for dropping ... I think it is cleaner16:37
hogepodgemarkvoelker: eglute: catherineD: it's pretty easy to tell if you're changing essential functionality. I saw this in the multi-tenant tests. It was clear multi-tenancy was not required on all but two tests.16:37
catherineDand send a good message the defcore does not require admin16:38
markvoelkerOk, so I think what I'm hearing here is:16:38
*** dwalleck has quit IRC16:38
*** witek has quit IRC16:38
markvoelker#action markvoelker submit new patchset for to leave the admin-requiring tests as advisory16:39
*** mickeys has joined #openstack-meeting-316:39
markvoelker#action markvoelker (and anyone else interested) look for alternative tests for the same capabilities16:39
*** annegentle has quit IRC16:39
markvoelker#action markvoelker (and anyone else interested) investigate the feasibility of modifying the tests to not need admin16:39
catherineDmarkvoelker: do we leave the admin tests or remove the test but leave the capability?16:40
*** doug-fish has quit IRC16:40
*** doug-fish has joined #openstack-meeting-316:40
catherineDwe really should not have any admin tests now that we identify them16:40
markvoelkercatherineD: I'm planning to leave them for the moment since it seems likely we're going to try to get some of them changed to not need admin.  If that doesn't happen, we have several more months to drop them16:40
*** annegentle has joined #openstack-meeting-316:41
eglutethat sounds like a good plan to me16:41
markvoelkerBut if folks feel strongly one way or the other, I'm not opposed to dropping and re-adding them.  Just seems to make a bit more work for later.16:41
* markvoelker looks at clock16:42
eglutei am ok with dropping as well. the only thing i would be opposed to is making these tests required for 2016.0816:42
markvoelkerOk, so I'll go that route and if anyone has strong opinions about dropping them now or not then voice them in gerrit and we'll iterate there. =)16:42
markvoelkerMove on?16:42
eglutethank you markvoelker!16:42
markvoelker#topic RefStack update to use Tempest tag 10.0.0 as default16:42
*** openstack changes topic to "RefStack update to use Tempest tag 10.0.0 as default (Meeting topic: defcore)"16:42
markvoelkercatherineD: the floor is yours16:43
*** scheuran has quit IRC16:43
catherineDso we will update RefStack to tempest tag 10.0.0 which is the tag for Mitaka16:43
catherineDcurrently RefStack still running with a Sept 11, 2015 tempest vestionb16:44
catherineDit is kind of old ...16:44
eglutecatherineD do you foresee any issues with the new tag?16:44
catherineDeglute: so we have taken care of the test names change by  ...16:45
*** doug-fish has quit IRC16:45
catherineDthere are also some change in tempest conf that the user have to pay attention to16:46
catherineDI know that a lot of the user is using master copy of tempest .... those users will not be affected16:46
hogepodgetempest is moving to a model where credentials and resources are defined outside of tempest.conf. It's a good change, but one that may have short term impact16:47
markvoelkercathrineD: this looks like a pretty routine update to me.  So, seems fine.  I'll see if I can run that version through my lab, but I don't foresee any real issues.16:47
*** Swami has joined #openstack-meeting-316:47
markvoelkerhogepodge: Yep, saw that too.  Perhaps something to note in our instructions.16:47
catherineDquestion is for DefCore to identify new tests to add ... should defcore also use the latest test list?16:47
*** amotoki has quit IRC16:48
hogepodgecatherineD: do you mean on aliasing?16:48
catherineDalias is for the existing defcore test ... but if defcore going to add new tests ... defcore should use update to date test list16:49
markvoelkercatherineD: hogepodge: that's covered here:
markvoelkerI mean
markvoelkerSo basically for a new Guideline (next.json) we use the current name of the test as it appears in Tempest.16:50
markvoelkerIf there's an older name that's been changed, we move that to the alias field in next.json16:50
catherineDfor the new tests .. if defcore use new test lists for its tests  we will avode alias16:50
markvoelkerI think the same principle applies to new tests we're adding too16:50
catherineDavode --> avoid16:51
catherineDnew tests here means the test name that has never appeared in defcore json16:51
markvoelkercatherineD: Well, usually, probably so.  But possibly not always.  Because if someone's using an older version of Tempest it might have an older test name.16:51
*** ddieterly[away] is now known as ddieterly16:52
markvoelkerSo conceivably we may need to add an alias even though we haven't required that test in the past.16:52
markvoelkerI suspect that'll be a pretty rare case in practice though16:52
catherineDif someone is testing a new OpenStack release they should not use old json16:52
*** vineetmenon has joined #openstack-meeting-316:52
*** vtech has joined #openstack-meeting-316:53
markvoelkerWell, we don't bound what version of tempest is used.  So it's not so much using old json as it is using an older Tempest (which might be necessary due to bugs, etc).16:53
catherineDfor example for Mitaka the require tests would jump from 100+ to 200+ because of the advisory tests16:53
eglutebecause defcore covers several releases, they might be using older json16:53
*** vgridnev has joined #openstack-meeting-316:53
catherineDif certify for Mitaka they must use 2016.0816:53
catherineDagree .. for older release the tests will be covered by aliases16:54
catherineDbut the newly defcore added tests does not need to be burdened with aliases16:54
markvoelkercathrineD: correct, they need to use 2016.08.  That Guideline might have a test called "ABC", which is what Tempest calls it today.  But Tempest might have changed it to "ABC" from "ZYX" the week before we added it to the Guideline.16:55
*** sc68cal has quit IRC16:55
markvoelkerSo if someone is using an older version of Tempest, they'll see "ABC" skipped because it's not found.  They might therefore reasonably request an alias be added.16:55
catherineDmarkvoelker: in that case it will cover by aliases becayse the test already exists in defcore16:55
*** banix has joined #openstack-meeting-316:56
catherineDthink about the tests that are not in any defcore json today16:56
*** scheuran has joined #openstack-meeting-316:56
*** scheuran has quit IRC16:56
catherineDthose are the tests that we should use from new test list16:56
catherineDanyway back to refstack update default tempest16:57
catherineDI guess it is a go ?16:57
hogepodgethree minutes16:57
*** vtech_ has joined #openstack-meeting-316:57
markvoelkercatherineD: go from me16:57
egluteyes, catherineD lets go ahead with new version16:57
hogepodgewant to make sure people look at gema's identity capabilities patch16:57
gemayes please16:57
gemano need to take time here, though :D16:57
eglute#topic keystone scoring16:57
*** openstack changes topic to "keystone scoring (Meeting topic: defcore)"16:57
egluteeveryone, please review gema's patch16:58
catherineDthank you ... yea after all that tempest ins 6 month old old as the openstack release :-)16:58
markvoelker#link Keystone scoring patch (new rev)16:58
eglutethank you catherineD!16:58
egluteand thank you gema, I will review the patch today16:58
*** vtech has quit IRC16:58
gemaeglute: thanks!16:58
egluteif any questions, lets take them to the defcore channel16:58
markvoelkerWith that we're about out of time.  We skipped the advisory->required topic, but we actually already discussed it a bit earlier and I have an AI to submit a new patchset on it16:59
markvoelkerThanks everyone!16:59
*** openstack changes topic to "npm lint jobs are failing due to a problem with npm registry. The problem is under investigation, and we will update once the issue is solved."16:59
openstackMeeting ended Wed Apr  6 16:59:25 2016 UTC.  Information about MeetBot at . (v 0.1.4)16:59
openstackMinutes (text):
*** dedery has joined #openstack-meeting-317:01
*** jpomeroy has quit IRC17:02
*** rossella_s has quit IRC17:03
*** rossella_s has joined #openstack-meeting-317:03
*** piet has joined #openstack-meeting-317:03
*** dedery_ has quit IRC17:05
*** cartik has quit IRC17:05
*** dedery has quit IRC17:06
*** vgridnev has quit IRC17:06
*** banix has quit IRC17:06
*** moshele has quit IRC17:08
*** vgridnev has joined #openstack-meeting-317:09
*** vgridnev has quit IRC17:09
*** mrmartin has quit IRC17:10
*** salv-orlando has quit IRC17:12
*** jtomasek has joined #openstack-meeting-317:14
*** sigmavirus24 is now known as sigmavirus24_awa17:14
*** banix has joined #openstack-meeting-317:15
*** e0ne has quit IRC17:17
*** ddieterly is now known as ddieterly[away]17:18
*** annegentle has quit IRC17:19
*** marg7175 has quit IRC17:20
*** marg7175 has joined #openstack-meeting-317:20
*** irenab_ has joined #openstack-meeting-317:21
*** sdake_ is now known as sdake17:21
*** Rockyg has quit IRC17:21
*** ddieterly[away] is now known as ddieterly17:22
*** irenab has quit IRC17:23
*** irenab_ is now known as irenab17:23
*** hdaniel has quit IRC17:24
*** ddieterly is now known as ddieterly[away]17:24
*** ddieterly[away] is now known as ddieterly17:24
*** doug-fish has joined #openstack-meeting-317:24
*** MarkAtwood has joined #openstack-meeting-317:24
*** numan_ has joined #openstack-meeting-317:26
*** vineetmenon has quit IRC17:27
*** Sukhdev_ has quit IRC17:28
*** sdake_ has joined #openstack-meeting-317:29
*** tonytan4ever has quit IRC17:29
*** sdake has quit IRC17:29
*** tqtran has joined #openstack-meeting-317:32
*** sambetts is now known as sambetts|afk17:39
*** sdake has joined #openstack-meeting-317:42
*** david-lyle has quit IRC17:44
*** sdake_ has quit IRC17:44
*** tonytan4ever has joined #openstack-meeting-317:45
*** ddieterly is now known as ddieterly[away]17:46
*** marg7175 has quit IRC17:48
*** lpetrut has quit IRC17:49
*** ihrachys has quit IRC17:49
*** cloudtrainme has joined #openstack-meeting-317:51
*** sigmavirus24_awa is now known as sigmavirus2417:52
*** vgridnev has joined #openstack-meeting-317:53
*** pvaneck has joined #openstack-meeting-317:53
*** annegentle has joined #openstack-meeting-317:55
*** s3wong has joined #openstack-meeting-317:56
*** toddjohn has quit IRC17:59
*** annegentle has quit IRC17:59
*** toddjohn has joined #openstack-meeting-318:00
*** annegentle has joined #openstack-meeting-318:01
*** ajmiller has joined #openstack-meeting-318:01
*** jpomeroy has joined #openstack-meeting-318:01
*** david-lyle has joined #openstack-meeting-318:02
*** e0ne has joined #openstack-meeting-318:04
*** mrmartin has joined #openstack-meeting-318:07
*** stanzgy has joined #openstack-meeting-318:08
*** yamamoto has quit IRC18:10
*** doug-fis_ has joined #openstack-meeting-318:11
*** doug-fi__ has joined #openstack-meeting-318:12
*** numan_ has quit IRC18:13
*** numan_ has joined #openstack-meeting-318:13
*** e0ne has quit IRC18:14
*** doug-fish has quit IRC18:14
*** piet has quit IRC18:15
*** doug-fish has joined #openstack-meeting-318:15
*** doug-fis_ has quit IRC18:15
*** neelashah has joined #openstack-meeting-318:16
*** vhoward has quit IRC18:17
*** doug-fi__ has quit IRC18:17
*** jobrs has quit IRC18:17
*** MarkAtwood has quit IRC18:20
*** SammyD has quit IRC18:21
*** yamamoto has joined #openstack-meeting-318:21
*** yamahata has quit IRC18:21
*** liangy has quit IRC18:22
*** e0ne has joined #openstack-meeting-318:24
*** stanzgy has quit IRC18:24
*** mickeys has quit IRC18:25
*** mickeys has joined #openstack-meeting-318:26
*** mickeys has quit IRC18:26
*** cloudtrainme has quit IRC18:27
*** mrmartin has quit IRC18:27
*** catherineD has left #openstack-meeting-318:31
*** cloudtrainme has joined #openstack-meeting-318:38
*** mrmartin has joined #openstack-meeting-318:40
*** rockyg has joined #openstack-meeting-318:41
*** ddieterly[away] has quit IRC18:46
*** e0ne has quit IRC18:46
*** lpetrut has joined #openstack-meeting-318:47
*** tellesnobrega is now known as tellesnobrega_af18:50
*** tellesnobrega_af is now known as tellesnobrega18:51
*** mrmartin has quit IRC18:51
*** mrmartin has joined #openstack-meeting-318:53
*** ihrachys has joined #openstack-meeting-318:55
*** clu_ has joined #openstack-meeting-318:59
*** ddieterly has joined #openstack-meeting-318:59
*** vgridnev has quit IRC19:00
*** vgridnev has joined #openstack-meeting-319:01
*** vgridnev has quit IRC19:02
*** vgridnev has joined #openstack-meeting-319:03
*** Swami has quit IRC19:04
*** Swami has joined #openstack-meeting-319:06
*** toddjohn has quit IRC19:06
*** aarefiev_ has joined #openstack-meeting-319:06
*** toddjohn has joined #openstack-meeting-319:08
*** Sukhdev has joined #openstack-meeting-319:08
*** yamamoto has quit IRC19:10
*** sc68cal has joined #openstack-meeting-319:12
*** toddjohn has quit IRC19:13
*** liangy has joined #openstack-meeting-319:14
*** itxaka_ has joined #openstack-meeting-319:14
*** TravT has joined #openstack-meeting-319:15
*** rockyg has quit IRC19:15
*** itxaka has quit IRC19:15
*** aarefiev_ has quit IRC19:17
*** cloudtrainme has quit IRC19:19
*** e0ne has joined #openstack-meeting-319:20
*** vgridnev has quit IRC19:26
*** Sukhdev has quit IRC19:26
*** cloudtrainme has joined #openstack-meeting-319:27
*** irenab_ has joined #openstack-meeting-319:28
*** vgridnev has joined #openstack-meeting-319:30
*** irenab has quit IRC19:31
*** irenab_ is now known as irenab19:31
*** tellesnobrega is now known as tellesnobrega_af19:35
*** tellesnobrega_af is now known as tellesnobrega19:35
*** salv-orlando has joined #openstack-meeting-319:37
*** Sukhdev has joined #openstack-meeting-319:38
*** rpjr_ has quit IRC19:40
*** Sukhdev has quit IRC19:42
*** salv-orlando has quit IRC19:44
*** cloudtrainme has quit IRC19:47
*** numan_ has quit IRC19:47
*** toddjohn has joined #openstack-meeting-319:47
*** e0ne has quit IRC19:50
*** crobertsrh has joined #openstack-meeting-319:51
*** toddjohn has quit IRC19:52
*** ajmiller has quit IRC19:53
*** salv-orlando has joined #openstack-meeting-319:54
*** salv-orlando has quit IRC19:54
*** annegentle has quit IRC19:55
*** salv-orlando has joined #openstack-meeting-319:55
*** robcresswell has joined #openstack-meeting-319:55
*** julim has joined #openstack-meeting-319:57
*** piet has joined #openstack-meeting-319:59
robcresswell#startmeeting horizondrivers20:00
openstackMeeting started Wed Apr  6 20:00:00 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: horizondrivers)"20:00
openstackThe meeting name has been set to 'horizondrivers'20:00
*** hurgleburgler has joined #openstack-meeting-320:01
robcresswellLets get started20:01
robcresswell#topic Notices20:01
*** ducttape_ has joined #openstack-meeting-320:01
*** openstack changes topic to "Notices (Meeting topic: horizondrivers)"20:01
*** cloudtrainme has joined #openstack-meeting-320:01
robcresswellOnly one thing to mention briefly20:02
robcresswellMake sure any last minute items are listed. I've reorganised it, and drafted the sessions to match20:02
robcresswellBut if there is any last minute content or sugestions, add it and I'll see about adding to the schedule.20:03
bpokornyAre the things under line 97 all topics for the contributors meetup?20:03
*** mrmartin has quit IRC20:04
bpokornyThanks, sounds good.20:04
*** mickeys has joined #openstack-meeting-320:04
robcresswellI've moved items around to match common topics, and the others are more like individual issues that we can discuss at the meetup.20:04
robcresswellAgenda for today is empty. Does anyone have any blueprints they would like looked at? Otherwise I'll pick at random for review.20:05
david-lyleI have one, I think20:05
*** kmartin has quit IRC20:06
robcresswellGo ahead20:06
* TravT looking at summit again20:06
*** Aish has joined #openstack-meeting-320:06
* david-lyle had to find20:06
*** kmartin has joined #openstack-meeting-320:07
david-lylethis is somewhat time sensitive, in that the longer it's not merged, the more people write tests that are potentially broken20:07
*** tyr_ has joined #openstack-meeting-320:07
david-lyleit started simple and onioned on me20:07
doug-fishsounds like it's a critical piece of work though20:08
robcresswellAh yeah, we discussed this yesterday. It fixes a *really* annoying bug too (
openstackLaunchpad bug 1517704 in OpenStack Dashboard (Horizon) "Test still passes even with tests failure" [High,In progress] - Assigned to David Lyle (david-lyle)20:08
david-lyleyeah, that was the onion part20:08
robcresswellAh, sorry about that20:08
robcresswellThinking approve and mark high. Any objections?20:09
*** fitoduarte has joined #openstack-meeting-320:10
doug-fishmakes sense to me. Let's put david-lyle on the spot!20:10
*** yamamoto has joined #openstack-meeting-320:11
robcresswell#info Approved, High priority20:11
*** banix has quit IRC20:11
robcresswellOops, forgot to change topic20:12
robcresswell#topic Blueprint review20:12
*** openstack changes topic to "Blueprint review (Meeting topic: horizondrivers)"20:12
robcresswellAny others?20:12
robcresswellI'll pick some out.20:13
*** yamahata has joined #openstack-meeting-320:13
*** rockyg has joined #openstack-meeting-320:13
TravT-1 for not giving direct link to nova bp20:14
bpokornyAre blueprints still supposed to use the blueprint template that we used to use?20:14
*** pcaruana has quit IRC20:14
robcresswellbpokorny: Yes20:14
TravT-1 for that too20:14
bpokornyAgree with TravT that this one is light on details.20:14
*** matrohon has joined #openstack-meeting-320:15
ducttape_so how would the flavor info get back and forth with the nova hosts???  that bp causes me more questions20:15
robcresswellits been up for 2 months or so, likely wont go anywhere :/20:15
robcresswellStill, too early to remove outright.20:15
robcresswellLets move on. I left a comment asking for more detail.20:15
doug-fishI have a favorite20:16
robcresswellI like the idea.20:16
ducttape_do we want to make that a horizon construct ?20:17
doug-fishIt's driven by what we want to do with the lbaas wizard20:17
doug-fishI think so20:17
doug-fishI do20:17
ducttape_like a wf is free to have anything for a landing page on success20:17
robcresswellKinda like the Sahara guide20:17
ducttape_and that page could have next steps etc , common actions / status polling20:17
doug-fishI don't think any workflows have landing pages do they?20:17
doug-fishdoes Sahara?20:18
robcresswelldoug-fish: Sahara has a step by step IIRC20:18
ducttape_they typically do not take advantage of that, but it's there to be used20:18
robcresswellIt did before we removed it20:18
robcresswellIt was veeeery laggy20:18
robcresswellBut it was a cool idea. We've talked before about directing Create Net to details for further config20:19
*** yamamoto has quit IRC20:19
doug-fishyes, I'd hope this functionality would work for that scenario as well20:19
TravTdoug-fish: are these really separate actions or just actions that also include help text and can be displayed differenly?20:19
*** vtech_ has quit IRC20:19
doug-fishit's the 2nd20:19
*** vtech has joined #openstack-meeting-320:19
ducttape_I'd like to see two workflows use that concept, then drive some sort of "let's refactor anything common" from there ?20:20
TravTokay, from a angular registry perspective, i'd see this as being extra information being registered with the action.20:20
doug-fishrobcresswell: would/could create net use this right away?20:22
robcresswellWe're a long way off rewriting all the networking panels in angular20:22
*** e0ne has joined #openstack-meeting-320:22
doug-fishit's reasonably straightforward to put into Horizon
doug-fishit *could* be done in the plugin, but would actually be more code. And less available for others to exploit.20:23
robcresswellOh I agree on it being in the horizon lib20:23
robcresswellSorry I think I misconstrued the question.20:24
robcresswellI'm for approving; the concept is good and we can refine the implementation in code review.20:24
*** mbound has joined #openstack-meeting-320:25
doug-fishI'm a fan, but not entirely unbiased. :-)20:25
robcresswellIt'd be useful for complex nested resources (mainly neutron work is jumping to mind)20:25
*** mbound has quit IRC20:25
TravTi think the idea is good. definitely need to talk a bit about impl details.20:25
david-lyleI think that it's on the details page, it's useful. My concern was burying the lead20:25
*** mbound has joined #openstack-meeting-320:25
david-lylebut the tables have that handled20:25
TravTdoug-fish: part of my point being that these aren't really different actions.20:26
TravTthat extra help text could be used in row / batch actions20:26
TravTas pop up or something as well20:26
david-lyleso, this is a JS only thing?20:26
TravThover over20:26
doug-fishoh I see20:26
robcresswelldavid-lyle: Seems like its being targeted at angular20:26
TravTso this is impl detail20:26
doug-fishdavid-lyle: yes, I think so20:26
doug-fishit's new function you can get only with the new code20:26
TravTbut is in the BP as well.20:26
TravTthe bp specifically says angular20:27
david-lyleno much for consistency, but have to make change somewhere20:27
robcresswellI dont think it would be huge issue; this is unlikely to be on every single detail page20:27
TravTdoug-fish: this all just interesting extra metadata about an action20:27
TravTand the actions directive already has templates where you choose how to render it in the input args20:27
*** e0ne has quit IRC20:28
doug-fishwell to developers that's what it is; I hope to users it's clarity on what should happen after creating a new object20:28
david-lyleso some details pages will have actions on the top right, and some in the page?20:28
robcresswellBut I think it fits nicely with making creation more wf-oriented20:28
david-lyleit was more about locating20:28
david-lyleI wouldn't say no, just voicing observations20:28
doug-fishI think all details pages will have actions on the top right. Some details pages will also have some inline actions with extra text as well20:29
robcresswellI think its more about guiding people on more complex setup20:29
david-lyledoug-fish: ok, that's not in the mock20:29
david-lylehence my confusion20:29
david-lyleoh wiat20:29
david-lyleI'm dumb20:29
robcresswelltime for a success?20:29
david-lyleI have no time for success20:30
*** yamahata has quit IRC20:30
*** vgridnev has quit IRC20:30
david-lylelooks good20:30
robcresswellMarking low, since its mainly aesthetic20:31
*** annegentle has joined #openstack-meeting-320:31
*** annegentle has quit IRC20:31
TravTi'll leave a comment reflecting my input above20:32
robcresswell#info Approved, marked Low20:32
robcresswellthanks TravT20:32
*** annegentle has joined #openstack-meeting-320:32
*** annegentle has quit IRC20:32
doug-fishyeah, sounds good, thx for the input!20:32
*** annegentle has joined #openstack-meeting-320:33
david-lylebtw, there is no ConfForFlavor bp in nova20:33
*** vgridnev has joined #openstack-meeting-320:33
robcresswelldavid-lyle: Can you leave a comment on that bp; when we circle back round later, we can just obsolete right away unless its updated.20:34
david-lylerobcresswell: sure20:34
*** ihrachys has quit IRC20:34
david-lyleit's either dead all around or far in the future20:34
robcresswellYeah, but I'd like to at least give the author a fair chance to respond20:35
robcresswellSo this object store bp, its unclear if its Python or Angular based20:35
robcresswellI would assume Angular, but it was put up early March and could be either...20:36
david-lylethe need is there either way20:36
*** sdake_ has joined #openstack-meeting-320:37
*** matrohon has quit IRC20:37
robcresswellTrue. I don't know how this ties in to r1chardj0n3s work20:37
*** itxaka_ has quit IRC20:37
*** sinval-afk has left #openstack-meeting-320:37
david-lyleI don't think r1chardj0n3s has a bp20:38
robcresswellI can't see any conflicting blueprints. I think approve, but ask for clarification on code and ask author to work with richard.20:39
*** sdake has quit IRC20:39
david-lylemakes sense to me20:39
*** ajmiller has joined #openstack-meeting-320:39
TravTrobcresswell: i think you need to state it is angular though20:39
*** vtech has quit IRC20:39
TravTwe deprecated django version20:39
robcresswellTravT: Yup, thats what I meant by clarification on code20:40
david-lylevive le django!20:40
david-lyleremember the django?20:40
TravTwe should buy david-lyle a shirt with that20:40
hurgleburgler+1 TravT20:40
TravTbtw, props on the local-settings.d last release20:40
*** kzaitsev_mb has joined #openstack-meeting-320:41
hurgleburglerI'll take one of those shirts too though20:41
* david-lyle unsure of the gender of django20:41
doug-fishfeminine is djanga20:41
david-lylebut django is like a ship20:42
robcresswell#info Approved20:42
* david-lyle will investigate20:42
*** sdake has joined #openstack-meeting-320:42
robcresswellAn old, old wooden ship20:42
* robcresswell hoping everyone has seen Anchorman20:42
david-lyleoh oh20:43
david-lylekick it out20:43
*** sdake_ has quit IRC20:44
david-lylevpn -> plugin20:44
robcresswellIt looks like they intend to put the 4 tab tables in one page...20:45
robcresswell :/20:45
*** mickeys has quit IRC20:46
robcresswellEither way, VPNaaS is a neutron plugin so should follow the path of LBaaS20:46
david-lylevpn is no longer part of neutron proper20:46
david-lylesame with fwaas20:47
*** rockyg has quit IRC20:47
*** vtech has joined #openstack-meeting-320:47
TravTsounds fine to me20:47
david-lyleI would be reluctant to put much more work on those into the horizon tree20:47
david-lyleother than bug fixes20:47
*** david-lyle_ has joined #openstack-meeting-320:48
* david-lyle going mobile20:48
TravTrobcresswell: why is "plugin" and "operator" feedback one topic?20:49
*** annegentle has quit IRC20:49
*** Aish has quit IRC20:49
*** vgridnev has quit IRC20:49
*** mickeys has joined #openstack-meeting-320:49
robcresswellTravT: Operator rarely uses an entire session, so it seemed sensible to use the fishbowl for something that was most likely to get a larger group of people from outside Horizon20:49
robcresswell#info Marked Obsolete; left comment about creating a Horizon plugin.20:50
*** alaski has joined #openstack-meeting-320:51
*** salv-orl_ has joined #openstack-meeting-320:51
robcresswellI think this has been superseded by hurgleburgler20:52
hurgleburgleruh oh20:52
TravTFrom the BP: "This blueprint is mainly about including some kind of documentation for contributors and reviewers to refer to."20:53
robcresswellYeah, which exists now I believe20:53
*** mickeys has quit IRC20:53
TravTi'd say this is superceded / done with no clear additional done criteria giving it reason to stay open20:54
hurgleburgleryeah, we've been attempting to document as we go20:54
*** annegentle has joined #openstack-meeting-320:54
robcresswell and
*** ddieterly is now known as ddieterly[away]20:54
*** salv-orlando has quit IRC20:55
hurgleburglermany of our naming conventions are defined by our use of Bootstrap as a css framework20:55
robcresswell#info marked Superseded20:55
*** lpetrut has quit IRC20:55
*** annegentle has quit IRC20:55
*** lpetrut has joined #openstack-meeting-320:56
robcresswellWait, thats been approved, ignore it20:56
* TravT ignored. check.20:57
*** mriedem has joined #openstack-meeting-320:58
TravThow would this work with multiple horizon processes deployed?20:59
TravTjust rely on session affinity of load balancer?20:59
TravTshared FS?20:59
doug-fishI'd think a separate service would be needed to store the history20:59
doug-fishthat kind of state seems well outside what Horiozn itself should be doing20:59
robcresswellYeah. I dont think Horizon should be handling this logic. It sounds like something we would display, but would be handled elsewhere21:00
TravTokay, thanks for the meeting today. catch you on the flip side21:00
robcresswellYeah, thats time.21:00
robcresswellThanks all21:00
*** openstack changes topic to "npm lint jobs are failing due to a problem with npm registry. The problem is under investigation, and we will update once the issue is solved."21:01
openstackMeeting ended Wed Apr  6 21:01:09 2016 UTC.  Information about MeetBot at . (v 0.1.4)21:01
openstackMinutes (text):
*** robcresswell has left #openstack-meeting-321:01
alaski#startmeeting nova_cells21:01
openstackMeeting started Wed Apr  6 21:01:30 2016 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** Sukhdev has joined #openstack-meeting-321:01
*** openstack changes topic to " (Meeting topic: nova_cells)"21:01
openstackThe meeting name has been set to 'nova_cells'21:01
*** ccarmack has joined #openstack-meeting-321:01
bauzas#endmeeting ?21:01
*** hurgleburgler has left #openstack-meeting-321:01
* bauzas tries to help dansmith21:01
alaskiwe'll keep this short21:02
alaskibut not that short21:02
melwitto/ hi21:02
alaski#topic testing21:02
*** openstack changes topic to "testing (Meeting topic: nova_cells)"21:02
*** crobertsrh has left #openstack-meeting-321:02
alaskinothing seems to have broken recently21:02
alaskibut ccarmack has changed some of the v1 regexes to ids, which should help prevent breaks21:03
*** rossella_s has quit IRC21:03
ccarmackyes, thats been merged21:03
*** rossella_s has joined #openstack-meeting-321:03
*** TravT has left #openstack-meeting-321:03
alaskion the v2 side the consensus has been that we need a simple command for devstack to use to setup cells. once that's in place we should look at getting grenade going21:03
alaskiI'm working on fixing up my PoC around that21:04
melwittis this separate from "the one command to rule them all?"21:04
bauzasI wrote until that21:04
alaskimelwitt: nope, that's the one21:04
bauzas(well, I actually updated it, rather)21:04
alaskibauzas: cool. are you going to update with the new command?21:05
bauzasalaski: remind me the change ?21:05
bauzasalaski: but I already CC'd21:05
*** ddieterly[away] is now known as ddieterly21:05
bauzasfor sure, anyways21:05
alaski#topic Open Reviews21:06
*** openstack changes topic to "Open Reviews (Meeting topic: nova_cells)"21:06
alaskithat is all21:06
dansmithI have a bunch of reviews21:06
dansmithoh wait, no I don't! :D21:06
alaski#topic Open Discussion21:06
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"21:06
alaskidansmith: hah, nice21:06
doffmCell0 patches are waiting for agreement on the upgrade commands. But once that is sorted should be ready for review.21:06
*** annegentle has joined #openstack-meeting-321:06
alaskiI put a bunch in the etherpad, so there's plenty to go around21:07
alaskidoffm: awesome. so far people seem good with the wrapper command, which means your stuff wouldn't need to change21:07
doffmOk, once commited to the wrapper command i'll ask dansmith to remove his -1. :)21:08
dansmithdoffm: I'll find something else, fear not :)21:08
alaskiso for summit, the schedule isn't final but it looks like we'll have two slots21:08
melwittso it'll be one wrapper command call per cell?21:09
alaskiI think a quick progress report would be good. but if there are open questions you'd like to discuss start thinking about that21:09
*** baoli_ has quit IRC21:09
doffmmelwitt: No, the wrapper is for the simple non-cells upgrade case. (I think)21:09
alaskimelwitt: what doffm said21:09
melwittah, okay. thanks21:10
dansmithfor the single cell case21:10
dansmithwe're rapidly getting to the point where we can't say "non-cells case"21:10
doffmWell, 'rapidly' might be pushing it. But getting there.21:10
alaskiI think this command is just about the tipping point21:11
alaskibut it is a bit fuzzy because not everything is in place yet21:11
*** r1chardj0n3s has left #openstack-meeting-321:12
alaskianything else to discuss today?21:12
alaskicool. thanks all!21:13
*** doug-fish has quit IRC21:13
*** openstack changes topic to "npm lint jobs are failing due to a problem with npm registry. The problem is under investigation, and we will update once the issue is solved."21:13
openstackMeeting ended Wed Apr  6 21:13:24 2016 UTC.  Information about MeetBot at . (v 0.1.4)21:13
openstackMinutes (text):
*** ccarmack has left #openstack-meeting-321:13
*** doug-fish has joined #openstack-meeting-321:13
*** doug-fish has quit IRC21:14
bauzasmeh, says bauzas(8) but I tried to be low-profile, dammit21:14
*** doug-fish has joined #openstack-meeting-321:14
*** julim has quit IRC21:14
*** mriedem has left #openstack-meeting-321:15
*** Sukhdev has quit IRC21:16
*** doug-fish has quit IRC21:18
*** david-lyle_ has quit IRC21:19
*** doug-fish has joined #openstack-meeting-321:21
*** Aish has joined #openstack-meeting-321:22
*** Aish has left #openstack-meeting-321:22
alaskibauzas: heh, second place. better luck next time :)21:23
*** sdague has quit IRC21:24
*** doug-fish has quit IRC21:25
*** rtheis has quit IRC21:31
*** alaski has left #openstack-meeting-321:39
*** piet has quit IRC21:40
*** neelashah has quit IRC21:42
*** jpomeroy has quit IRC21:45
*** Sukhdev has joined #openstack-meeting-321:49
*** kebray_ has joined #openstack-meeting-321:51
*** ddieterly is now known as ddieterly[away]21:51
*** rbak_ has quit IRC21:53
*** Sukhdev has quit IRC21:53
*** sdake has quit IRC21:54
*** kebray has quit IRC21:54
*** Sukhdev has joined #openstack-meeting-321:58
*** sigmavirus24 is now known as sigmavirus24_awa21:58
*** Sukhdev has quit IRC22:03
*** ajmiller has quit IRC22:03
*** ajmiller has joined #openstack-meeting-322:03
*** lpetrut has quit IRC22:04
*** baoli has joined #openstack-meeting-322:10
*** fitoduarte has quit IRC22:10
*** ddieterly[away] is now known as ddieterly22:13
*** annegentle has quit IRC22:14
*** rbak has joined #openstack-meeting-322:15
*** dimtruck is now known as zz_dimtruck22:19
*** piet has joined #openstack-meeting-322:19
*** baoli has quit IRC22:20
*** neiljerram has quit IRC22:20
*** baoli has joined #openstack-meeting-322:20
*** rbrndt_ has joined #openstack-meeting-322:24
*** Sukhdev has joined #openstack-meeting-322:24
*** rbrndt_ has left #openstack-meeting-322:26
*** ducttape_ has quit IRC22:27
*** tonytan4ever has quit IRC22:28
*** kzaitsev_mb has quit IRC22:28
*** ddieterly is now known as ddieterly[away]22:28
*** ddieterly[away] is now known as ddieterly22:29
*** ddieterly is now known as ddieterly[away]22:30
*** ddieterly[away] is now known as ddieterly22:30
*** piet has quit IRC22:32
*** piet has joined #openstack-meeting-322:33
*** ddieterly is now known as ddieterly[away]22:39
*** ddieterly[away] is now known as ddieterly22:42
*** piet has quit IRC22:45
*** piet has joined #openstack-meeting-322:45
*** cloudtrainme has quit IRC22:50
*** ddieterly is now known as ddieterly[away]22:53
*** zz_dimtruck is now known as dimtruck22:58
*** vtech has quit IRC22:58
*** vtech has joined #openstack-meeting-322:58
*** piet has quit IRC22:59
*** annegentle has joined #openstack-meeting-323:05
*** annegentle has quit IRC23:09
*** ajmiller has quit IRC23:11
*** ajmiller has joined #openstack-meeting-323:12
*** mickeys has joined #openstack-meeting-323:13
*** rhochmuth has quit IRC23:14
*** Sukhdev has quit IRC23:14
*** mickeys has quit IRC23:17
*** hichihara has joined #openstack-meeting-323:20
*** mickeys has joined #openstack-meeting-323:25
*** ddieterly has joined #openstack-meeting-323:26
*** ddieterly is now known as ddieterly[away]23:26
*** annegentle has joined #openstack-meeting-323:27
*** mickeys has quit IRC23:28
*** mickeys has joined #openstack-meeting-323:30
*** dimtruck is now known as zz_dimtruck23:34
*** Swami has quit IRC23:34
*** pt_15 has quit IRC23:35
*** salv-orl_ has quit IRC23:36
*** mickeys has quit IRC23:37
*** mickeys has joined #openstack-meeting-323:39
*** annegentle has quit IRC23:39
*** kenji-i has joined #openstack-meeting-323:43
*** baoli has quit IRC23:44
*** sdake has joined #openstack-meeting-323:44
*** sdake_ has joined #openstack-meeting-323:46
*** sdake has quit IRC23:49
*** Sukhdev has joined #openstack-meeting-323:50
*** sdake has joined #openstack-meeting-323:50
*** tyr_ has quit IRC23:50
*** Sukhdev has quit IRC23:52
*** sdake_ has quit IRC23:52
*** hoangcx has quit IRC23:54
*** annegentle has joined #openstack-meeting-323:54
*** hoangcx has joined #openstack-meeting-323:54
*** ajmiller has quit IRC23:57
*** annegentle has quit IRC23:58
*** mickeys has quit IRC23:59
*** mickeys has joined #openstack-meeting-323:59

Generated by 2.14.0 by Marius Gedminas - find it at!