Wednesday, 2016-01-27

*** nelsnels_ has joined #openstack-meeting-300:01
*** nelsnelson has quit IRC00:03
*** peristeri has quit IRC00:04
*** dims has quit IRC00:04
*** rbak has quit IRC00:04
*** baoli has quit IRC00:07
*** Aish has quit IRC00:09
*** Aish has joined #openstack-meeting-300:11
*** shwetaap has quit IRC00:12
*** Sukhdev has joined #openstack-meeting-300:13
*** dimtruck is now known as zz_dimtruck00:15
*** shwetaap has joined #openstack-meeting-300:15
*** Sukhdev has quit IRC00:26
*** tej has joined #openstack-meeting-300:27
*** kebray has quit IRC00:35
*** kebray has joined #openstack-meeting-300:36
*** yamamoto_ has quit IRC00:39
*** liangy has quit IRC00:44
*** shwetaap has quit IRC00:45
*** markvoelker has quit IRC00:51
*** edleafe has quit IRC00:53
*** Swami has quit IRC00:55
*** edleafe has joined #openstack-meeting-300:55
*** markvoelker has joined #openstack-meeting-300:56
*** dixiaoli has joined #openstack-meeting-300:59
*** jmckind_ has joined #openstack-meeting-301:01
*** hoangcx has joined #openstack-meeting-301:03
*** stanzgy has quit IRC01:03
*** jmckind has quit IRC01:04
*** bpokorny_ has joined #openstack-meeting-301:07
*** bpokorny_ has quit IRC01:07
*** bpokorny has quit IRC01:07
*** bpokorny has joined #openstack-meeting-301:07
*** bryan_att has quit IRC01:09
*** spzala has quit IRC01:10
*** spzala has joined #openstack-meeting-301:10
*** baoli has joined #openstack-meeting-301:11
*** baoli has quit IRC01:11
*** jmckind has joined #openstack-meeting-301:13
*** sdake has joined #openstack-meeting-301:13
*** bpokorny has quit IRC01:14
*** spzala has quit IRC01:15
*** sdake_ has joined #openstack-meeting-301:15
*** jmckind_ has quit IRC01:16
*** hoangcx has quit IRC01:16
*** jmckind has quit IRC01:17
*** sdake has quit IRC01:17
*** spzala has joined #openstack-meeting-301:19
*** ivar-laz_ has quit IRC01:22
*** ivar-lazzaro has joined #openstack-meeting-301:22
*** ivar-lazzaro has quit IRC01:23
*** yasui has quit IRC01:23
*** yamamoto_ has joined #openstack-meeting-301:23
*** piet has joined #openstack-meeting-301:23
*** ivar-lazzaro has joined #openstack-meeting-301:23
*** ivar-lazzaro has quit IRC01:24
*** vahidh has quit IRC01:24
*** yasui has joined #openstack-meeting-301:26
*** Sukhdev has joined #openstack-meeting-301:32
*** Aish has quit IRC01:32
*** sdake has joined #openstack-meeting-301:36
*** david-lyle has quit IRC01:36
*** Sukhdev has quit IRC01:37
*** Sukhdev has joined #openstack-meeting-301:37
*** sdake_ has quit IRC01:37
*** Sukhdev has quit IRC01:40
*** Sukhdev has joined #openstack-meeting-301:40
*** piet has quit IRC01:41
*** piet has joined #openstack-meeting-301:41
*** Sukhdev has quit IRC01:43
*** Sukhdev has joined #openstack-meeting-301:44
*** stanzgy has joined #openstack-meeting-301:44
*** FallenPe_ has joined #openstack-meeting-301:44
*** tej has quit IRC01:44
*** Sukhdev has quit IRC01:47
*** Sukhdev has joined #openstack-meeting-301:47
*** FallenPegasus has quit IRC01:47
*** Sukhdev has quit IRC01:50
*** Sukhdev has joined #openstack-meeting-301:50
*** Sukhdev has quit IRC01:53
*** Sukhdev has joined #openstack-meeting-301:53
*** mtanino has quit IRC01:54
*** yasui has quit IRC01:56
*** baohua has joined #openstack-meeting-301:57
*** yasui has joined #openstack-meeting-301:57
*** Sukhdev_ has joined #openstack-meeting-301:58
*** Sukhdev has quit IRC01:59
*** Sukhdev_ has quit IRC02:02
*** Sukhdev has joined #openstack-meeting-302:02
*** rakhmerov has quit IRC02:03
*** yasui has quit IRC02:04
*** yasui has joined #openstack-meeting-302:05
*** Sukhdev has quit IRC02:05
*** Sukhdev has joined #openstack-meeting-302:05
*** rakhmerov has joined #openstack-meeting-302:07
*** Sukhdev has quit IRC02:08
*** Sukhdev has joined #openstack-meeting-302:08
*** Sukhdev has quit IRC02:10
*** Sukhdev has joined #openstack-meeting-302:11
*** Sukhdev has quit IRC02:13
*** Sukhdev has joined #openstack-meeting-302:14
*** Sukhdev has quit IRC02:14
*** banix has joined #openstack-meeting-302:14
*** sdake has quit IRC02:16
*** zhurong has joined #openstack-meeting-302:18
*** dims has joined #openstack-meeting-302:24
*** ivar-lazzaro has joined #openstack-meeting-302:24
*** ivar-lazzaro has quit IRC02:29
*** rossella_s has quit IRC02:31
*** kebray has quit IRC02:31
*** rossella_s has joined #openstack-meeting-302:31
*** kebray has joined #openstack-meeting-302:36
*** FallenPe_ has quit IRC02:37
*** MarkAtwood has quit IRC02:42
*** ivar-lazzaro has joined #openstack-meeting-302:42
*** yamahata has quit IRC02:44
*** hoangcx has joined #openstack-meeting-302:45
*** iyamahat has quit IRC02:47
*** e0ne has joined #openstack-meeting-302:48
*** spzala has quit IRC03:00
*** spzala has joined #openstack-meeting-303:01
*** sdake has joined #openstack-meeting-303:04
*** piet has quit IRC03:04
*** spzala has quit IRC03:05
*** sdake has quit IRC03:12
*** s3wong has quit IRC03:14
*** spzala has joined #openstack-meeting-303:15
*** Aish has joined #openstack-meeting-303:23
*** Aish has quit IRC03:23
*** dims has quit IRC03:30
*** tellesnobrega is now known as tellesnobrega_af03:33
*** baoli has joined #openstack-meeting-303:37
*** FallenPegasus has joined #openstack-meeting-303:38
*** raddaoui has joined #openstack-meeting-303:41
*** baoli has quit IRC03:42
*** kavit_ has quit IRC03:48
*** doug-fish has joined #openstack-meeting-303:49
*** vahidh has joined #openstack-meeting-303:53
*** kavit_ has joined #openstack-meeting-303:55
*** stendulker has joined #openstack-meeting-303:58
*** stendulker_ has joined #openstack-meeting-304:00
*** baoli has joined #openstack-meeting-304:01
*** stendulker has quit IRC04:03
*** banix has quit IRC04:03
*** markvoelker has quit IRC04:04
*** Poornima has joined #openstack-meeting-304:07
*** salv-orl_ has quit IRC04:09
*** shwetaap has joined #openstack-meeting-304:10
*** baoli has quit IRC04:17
*** vahidh has quit IRC04:19
*** stendulker has joined #openstack-meeting-304:23
*** stendulker_ has quit IRC04:23
*** spzala has quit IRC04:23
*** spzala has joined #openstack-meeting-304:24
*** david-lyle has joined #openstack-meeting-304:25
*** david-lyle has quit IRC04:25
*** Sukhdev has joined #openstack-meeting-304:27
*** spzala has quit IRC04:28
*** raddaoui has quit IRC04:30
*** coolsvap|away is now known as coolsvap04:31
*** stendulker_ has joined #openstack-meeting-304:32
*** stendulker has quit IRC04:34
*** david-lyle has joined #openstack-meeting-304:37
*** piet has joined #openstack-meeting-304:49
*** Poornima has quit IRC04:54
*** FallenPegasus has quit IRC04:59
*** shwetaap has quit IRC05:01
*** shwetaap has joined #openstack-meeting-305:02
*** shwetaap has quit IRC05:03
*** vahidh has joined #openstack-meeting-305:03
*** FallenPegasus has joined #openstack-meeting-305:05
*** yamahata has joined #openstack-meeting-305:05
*** markvoelker has joined #openstack-meeting-305:05
*** salv-orlando has joined #openstack-meeting-305:05
*** iyamahat has joined #openstack-meeting-305:06
*** piet has quit IRC05:08
*** markvoelker has quit IRC05:10
*** Poornima has joined #openstack-meeting-305:12
*** sdake has joined #openstack-meeting-305:13
*** salv-orlando has quit IRC05:13
*** krtaylor has quit IRC05:15
*** bsilverman has joined #openstack-meeting-305:15
*** vishwanathj has joined #openstack-meeting-305:15
*** vishwanathj has quit IRC05:16
*** ivar-laz_ has joined #openstack-meeting-305:20
*** ivar-lazzaro has quit IRC05:22
*** spzala has joined #openstack-meeting-305:24
*** ivar-laz_ has quit IRC05:25
*** kebray_ has joined #openstack-meeting-305:25
*** kebray has quit IRC05:28
*** krtaylor has joined #openstack-meeting-305:28
*** kebray_ has quit IRC05:28
*** kebray has joined #openstack-meeting-305:28
*** sdake has quit IRC05:29
*** spzala has quit IRC05:30
*** e0ne has quit IRC05:33
*** vishwanathj has joined #openstack-meeting-305:33
*** vishwanathj has quit IRC05:34
*** FallenPegasus has quit IRC05:36
*** FallenPegasus has joined #openstack-meeting-305:40
*** kebray_ has joined #openstack-meeting-305:45
*** kebray has quit IRC05:46
*** FallenPegasus has quit IRC05:48
*** vahidh has quit IRC05:50
*** lazy_prince has joined #openstack-meeting-305:51
*** sdake has joined #openstack-meeting-305:51
*** piet has joined #openstack-meeting-305:52
*** FallenPegasus has joined #openstack-meeting-305:57
*** soichi has joined #openstack-meeting-306:03
*** nkrinner has joined #openstack-meeting-306:05
*** vishwanathj_ has joined #openstack-meeting-306:05
*** salv-orlando has joined #openstack-meeting-306:05
*** vgridnev has joined #openstack-meeting-306:07
*** salv-orlando has quit IRC06:10
*** muawiakhan has joined #openstack-meeting-306:14
*** fawadkhaliq has joined #openstack-meeting-306:15
*** FallenPegasus has quit IRC06:18
*** kaz has joined #openstack-meeting-306:20
*** vishwanathj has joined #openstack-meeting-306:20
*** vishwanathj has quit IRC06:21
*** piet has quit IRC06:22
*** spzala has joined #openstack-meeting-306:27
*** rossella_s has quit IRC06:31
*** rossella_s has joined #openstack-meeting-306:31
fawadkhaliqyamamoto_: are you the meeting chair?06:32
*** spzala has quit IRC06:32
yamamoto_fawadkhaliq: i don't know :-)06:32
fawadkhaliqyamamoto_: lol06:32
reedipyamamoto_ : I think you can chair it today ...06:32!06:32
fawadkhaliqah, there you go06:32
reedipmain agenda today is mainly to discuss about the specs06:32
fawadkhaliqyou are the chosen one06:32
yamamoto_#startmeeting taas06:33
openstackMeeting started Wed Jan 27 06:33:12 2016 UTC and is due to finish in 60 minutes.  The chair is yamamoto_. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.06:33
*** openstack changes topic to " (Meeting topic: taas)"06:33
openstackThe meeting name has been set to 'taas'06:33
yamamoto_#link agenda06:33
yamamoto_#topic spec06:33
*** openstack changes topic to "spec (Meeting topic: taas)"06:33
yamamoto_i updated the spec review06:33
yamamoto_i think i applied all feedback.  sorry if i missed yours!06:34
yamamoto_does anyone have anything particular about the spec to discuss?06:34
reedipi think fawadkhaliq mentioned about Policy Based packet mirroring06:35
fawadkhaliqyamamoto_: thanks for updating the spec06:35
fawadkhaliqI just look a quick look06:35
fawadkhaliqI am not sure if we covered that yet06:35
fawadkhaliqso maybe we can discuss that and the incorporate in the spec.06:35
fawadkhaliqs/and the/and then/06:36
reedipyamamoto_ : from a use case point of view, would policy based mirroring  be required ?06:36
fawadkhaliqSince we are defining the API06:36
yamamoto_do you have any idea how api for policy thing would look like?06:36
fawadkhaliqI had the following thoughts:06:36
fawadkhaliqWe cover all the potential use cases and define the API to be able to support them.06:37
fawadkhaliqThe implementation can come in pieces.06:37
fawadkhaliqSimilar to how ipv6 works, not everything is implemented and expected to work but API definition is complete and can be consumed by different backends.06:37
reedipfawadkhaliq +1 , but we need to formalize use-cases06:37
fawadkhaliqreedip: Agree06:38
yamamoto_my impression is it's better to wait neutron classifier stuff settle and try to leverage it, rather than trying to invent our own right now.06:38
fawadkhaliqI can take a stab at adding patch to yamamoto_ spec06:38
fawadkhaliqyamamoto_: can you please elaborate a bit about Neutron classifier support for everyone's benefit?06:38
*** hdaniel has joined #openstack-meeting-306:39
*** sdake has quit IRC06:40
yamamoto_my understanding is that it's trying to define something which can be shared among projects like fwaas sg etc06:40
fawadkhaliqyamamoto_: yes, I think so too.06:40
fawadkhaliqyamamoto_: so the classificaiton mechanism will be added as lib to neutron06:41
fawadkhaliqyamamoto_: we will need the API definition06:41
fawadkhaliqI am not sure how active this project is btw06:41
fawadkhaliqdoes anyone know if this is being actively worked on?06:41
yamamoto_i have no idea06:42
fawadkhaliqI see this was last updated 2 months ago :(06:42
reedipfawadkhaliq : I think this is on a slow burner ...06:43
fawadkhaliqreedip: exactly06:43
reedipmight take some time06:43
fawadkhaliqso maybe we move on and think about what's there today and make it happen with the existing primitives and if/when classifiers arrive, we can think about potential changes with an upgrade path06:43
*** numans has joined #openstack-meeting-306:43
fawadkhaliqreedip: yamamoto_ muawiakhan soichi: thoughts?06:44
reedipAnyways, I think keeping dependancy on neutron classifier is more towards the API definition, which can be followed up once a list of definitive use-cases are finalized06:44
reedipfawadkhaliq +1 on thinking about classifiers later06:44
soichifawadkhaliq: +106:45
yamamoto_sure, we can/should feed our requirements to neutron classifer.06:45
fawadkhaliqreedip: soichi muawiakhan yamamoto_. perfect!06:45
fawadkhaliqso next step should be to update the spec with use cases? I can help there.06:46
reedipfawadkhaliq : +106:46
reedipI will also look into it, and if possible update the same.06:47
fawadkhaliqokay cool. yamamoto_ you can assign me an action item on that, I will be happy to help.06:47
*** FallenPegasus has joined #openstack-meeting-306:47
yamamoto_#action fawadkhaliq update the spec with use cases06:48
fawadkhaliqthanks yamamoto_ \o/ I like work :)06:48
reedipThere are some ideas on the spec as well , like (1) Network monitoring, instead of port (2) Policy based monitoring (3) tenant based monitoring(?)06:49
*** sdake has joined #openstack-meeting-306:49
fawadkhaliqreedip: yes, nicely summarized in one line.06:49
*** sdake has quit IRC06:50
fawadkhaliqlots of silence in the room :-)06:51
reedipanything else ?06:51
fawadkhaliq*plays music*06:51
reedipyeah, it tends to be a bit quiet :)06:51
yamamoto_lets move on06:51
yamamoto_#topic Open discussion06:52
*** openstack changes topic to "Open discussion (Meeting topic: taas)"06:52
reedipL2 extnesion for taas is currently on hold, once vyadav comes back , will look into it06:52
fawadkhaliqso from the governance perspective, can someone please summarize a bit whats the status of taas?06:52
fawadkhaliqis it a subproject in neutron etc06:53
yamamoto_it isn't neutron subproject.06:53
reedipfawadkhaliq : Nope , its still under discussion06:53
fawadkhaliqyamamoto_: reedip thanks. what are your thoughts around it? I am assuming we have a proposal06:53
fawadkhaliqoh perfect06:54
fawadkhaliqI will take a look06:54
reedipfawadkhaliq, its currently on hold, mainly because of the spec finalization06:54
fawadkhaliqreedip: I see. thanks.06:54
yamamoto_and "Evolving the stadium concept"06:54
fawadkhaliqgot it06:55
fawadkhaliqthanks guys. that's all from my side.06:55
reedipyamamoto_ and all, nothing from my side as well .06:55
yamamoto_it seems we've done06:56
reedipfawadkhaliq: the 4th comment from Armando on the governance commit is an important one, JFYI06:56
fawadkhaliqreedip: thanks. Will take a look.06:56
yamamoto_thank you for attending06:57
*** openstack changes topic to "OpenStack Meetings ||"06:57
openstackMeeting ended Wed Jan 27 06:57:08 2016 UTC.  Information about MeetBot at . (v 0.1.4)06:57
openstackMinutes (text):
*** salv-orlando has joined #openstack-meeting-306:57
*** salv-orlando has quit IRC06:57
reedipgreat :) Take care everyone06:58
*** salv-orlando has joined #openstack-meeting-306:58
muawiakhantake care bye06:58
*** soichi has left #openstack-meeting-306:59
*** vgridnev has quit IRC07:00
*** kaz has quit IRC07:02
*** hoangcx has quit IRC07:05
*** markvoelker has joined #openstack-meeting-307:06
*** markvoelker has quit IRC07:11
*** belmoreira has joined #openstack-meeting-307:15
*** muawiakh_ has joined #openstack-meeting-307:18
*** hdaniel has quit IRC07:18
*** stanzgy_ has joined #openstack-meeting-307:19
*** stendulker has joined #openstack-meeting-307:20
*** stanzgy has quit IRC07:21
*** muawiakhan has quit IRC07:21
*** stendulker_ has quit IRC07:21
*** FallenPegasus has quit IRC07:28
*** iyamahat has quit IRC07:28
*** vgridnev has joined #openstack-meeting-307:38
*** dixiaoli has quit IRC07:46
*** dedery has joined #openstack-meeting-307:59
*** vtech has joined #openstack-meeting-307:59
*** Sukhdev has quit IRC08:00
*** dixiaoli has joined #openstack-meeting-308:03
*** salv-orlando has quit IRC08:11
*** matrohon has joined #openstack-meeting-308:13
*** vishwanathj_ has quit IRC08:15
*** vahidh has joined #openstack-meeting-308:19
*** egallen has joined #openstack-meeting-308:21
*** vahidh has quit IRC08:24
*** spzala has joined #openstack-meeting-308:28
*** hdaniel has joined #openstack-meeting-308:30
*** spzala has quit IRC08:35
*** dtardivel has joined #openstack-meeting-308:35
*** hdaniel has quit IRC08:35
*** vgridnev has quit IRC08:36
*** evgenyf has joined #openstack-meeting-308:37
*** muawiakh_ has quit IRC08:40
*** jlanoux has joined #openstack-meeting-308:42
*** kebray_ has quit IRC08:43
*** vgridnev has joined #openstack-meeting-308:44
*** armax has quit IRC08:45
*** vgridnev has quit IRC08:46
*** hdaniel has joined #openstack-meeting-308:47
*** safchain has joined #openstack-meeting-308:48
*** jaypipes has joined #openstack-meeting-308:49
*** ihrachys has joined #openstack-meeting-308:53
*** neiljerram has joined #openstack-meeting-308:53
*** adi__ has joined #openstack-meeting-308:56
*** emalin has joined #openstack-meeting-308:57
*** amir_gur has joined #openstack-meeting-308:58
*** elisha_r has joined #openstack-meeting-308:58
emalinhi elisha08:59
*** idan_hefetz has joined #openstack-meeting-308:59
*** mbound has joined #openstack-meeting-309:00
elisha_rcan you hear me all the way over there? I can try and type louder...09:00
*** ifat_afek_ has joined #openstack-meeting-309:00
ifat_afek_#startmeeting vitrage09:00
openstackMeeting started Wed Jan 27 09:00:58 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.09:01
*** openstack changes topic to " (Meeting topic: vitrage)"09:01
openstackThe meeting name has been set to 'vitrage'09:01
ifat_afek_Hi everyone :-)09:01
*** lhartal has joined #openstack-meeting-309:01
lhartalhi all :)09:01
*** mkoushnir has joined #openstack-meeting-309:02
*** armax has joined #openstack-meeting-309:04
*** salv-orlando has joined #openstack-meeting-309:04
*** omer_etrog has joined #openstack-meeting-309:05
*** eyalb has joined #openstack-meeting-309:06
ifat_afek_#topic Current status and progress09:06
*** openstack changes topic to "Current status and progress (Meeting topic: vitrage)"09:06
ifat_afek_I don’t have many updates today09:07
*** markvoelker has joined #openstack-meeting-309:07
ifat_afek_I started checking Aodh solution that gordc suggested when I talked with him on their IRC channel. Still in progress09:07
*** nadav_yakar has joined #openstack-meeting-309:07
ifat_afek_updates anyone?09:08
eyalbI will update09:08
*** JeanBriceCombebi has joined #openstack-meeting-309:08
eyalbI added tests to the vitrage api09:08
*** Ohad has joined #openstack-meeting-309:08
eyalbat the moment only get version09:08
eyalbwill add the get topology later09:09
*** alexey_weyl has joined #openstack-meeting-309:09
alexey_weylHello :)09:09
eyalbwith authentication later09:09
eyalbthat it09:09
ifat_afek_great, thanks09:09
elisha_rMy update: Liat and I worked on the Vitrage Template (for RCA and deduced alarms, etc.) format, and uploaded it to github for review.09:09
ifat_afek_looks good, I already reviewed it09:10
ifat_afek_let's wait for other reviews before we approve it09:10
elisha_rGot a few comments over the past few days, which will be updated there as well, hopefully in the next few days09:10
elisha_rsure. will wait to get more before approving.09:11
elisha_rthat's it09:11
omer_etrogI will update09:11
omer_etrogwe add installation process for vitrage-dashboard in devstack09:12
ifat_afek_thanks elisha_r09:12
lhartalI think we should start to work on it.. no need to wait for approving09:12
ifat_afek_omer_etrog: cool! this is an important progress09:12
*** danoffek has joined #openstack-meeting-309:12
ifat_afek_lhartal: right. you can start working, and if there are minor changes in the design you can change it later09:12
*** markvoelker has quit IRC09:12
ifat_afek_omer_etrog: any other updates on the ui?09:13
*** mkoushnir has quit IRC09:13
*** omer_etrog_ has joined #openstack-meeting-309:13
elisha_rlhartal: I agree09:14
omer_etrog_sorry, need to check the installation of python-vitrage in horizon09:14
*** JeanBriceCombebi has quit IRC09:14
emalinI have no updates today09:14
ifat_afek_emalin: thanks09:15
omer_etrog_Alon is adding Legend to the sunburest09:15
omer_etrog_and I`m done..09:16
ifat_afek_omer_etrog_: thanks09:16
ifat_afek_who else wants to update?09:16
*** omer_etrog has quit IRC09:16
*** woodster_ has quit IRC09:16
lhartalI want09:16
alexey_weylWe have published our first use case demo09:17
alexey_weylYou can find it in Vitrage Wiki09:17
ifat_afek_alexey_weyl: cool!!09:17
*** mkoushnir has joined #openstack-meeting-309:17
lhartaldo you have a link?09:17
ifat_afek_alexey_weyl: you can write it with #link in the beginning09:18
lhartalmy updates: last week I worked on new design for the transformers09:19
*** armax_ has joined #openstack-meeting-309:19
lhartalI did a POC and it looks very good09:19
lhartalthe main idea is that the transformers will be a YAML configuration files (instead of python code)09:19
lhartala transformer engine will load the files, parse them and create Entity Transformer object (per transformer file)09:19
lhartalthe problem was when we needed to add logic to each transformer. This makes the change too complicated and it requires to create a new blueprint09:20
lhartalit becomes a complicated change requires us to open blueprint09:20
ifat_afek_lhartal: do you have an example for such a logic?09:20
*** armax has quit IRC09:21
*** armax_ is now known as armax09:21
lhartalwhen the value is composed of several fields09:22
lhartalwhen the key is the value itself09:22
lhartalwhen the path to the vallue is dynamic09:23
*** itxaka has joined #openstack-meeting-309:23
ifat_afek_lhartal: ok... makes sense to create a blueprint indeed09:23
lhartalAlso I started to work on loading the templates files into vitrage09:24
lhartalthats all :)09:24
ifat_afek_lhartal: thanks09:24
mkoushnirThe first tempest test for graph waiting in git review for approve09:24
ifat_afek_mkoushnir: great!!09:24
mkoushnirnext step is e2e scenario - with real setup or simulator - create several instanses and hosts - create graph and full validation09:26
ifat_afek_mkoushnir: this is an important step. we must have these tempest working in order to say we really completed a use case09:27
ifat_afek_once the first one-two tests work, other people might write more tempest tests09:27
*** JeanBriceCombebi has joined #openstack-meeting-309:27
*** emalin has quit IRC09:27
ifat_afek_any other updates anyone?09:27
ifat_afek_ok, let's move on09:29
ifat_afek_#topic Review action items09:29
*** openstack changes topic to "Review action items (Meeting topic: vitrage)"09:29
ifat_afek_• ifat_afek continue discussions with Aodh09:29
ifat_afek_this is in progress09:29
ifat_afek_#action ifat_afek_ check aodh integration and update the blueprints09:30
ifat_afek_• finalize get topology API09:30
ifat_afek_we are waiting for PinPoint response. No action on our side for now09:30
ifat_afek_#topic Next Steps09:30
*** openstack changes topic to "Next Steps (Meeting topic: vitrage)"09:30
*** baohua has quit IRC09:30
*** jlanoux has quit IRC09:31
ifat_afek_I think it's a good time to review our next use case, go over the blueprints, and re-prioritize them09:31
*** spzala has joined #openstack-meeting-309:31
lhartalI agree with you09:31
eyalbso do i :-)09:32
ifat_afek_#action review our use cases, blueprints and priorities09:32
*** jlanoux has joined #openstack-meeting-309:32
Ohadyes I agree, we need to start work on plug-in for Nagios and HW failures such as switch failure, etc09:34
ifat_afek_Ohad: right09:34
ifat_afek_#topic Open Discussion09:34
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"09:34
ifat_afek_anything someone wants to talk about?09:35
ifat_afek_so I guess we are done for today09:36
ifat_afek_goodbye everybody09:36
*** spzala has quit IRC09:36
*** tmazur has joined #openstack-meeting-309:37
*** openstack changes topic to "OpenStack Meetings ||"09:38
openstackMeeting ended Wed Jan 27 09:38:12 2016 UTC.  Information about MeetBot at . (v 0.1.4)09:38
openstackMinutes (text):
*** Ohad has quit IRC09:38
*** danoffek has left #openstack-meeting-309:40
*** amotoki has joined #openstack-meeting-309:41
*** vgridnev has joined #openstack-meeting-309:46
*** lhartal has quit IRC09:47
*** nadav_yakar has quit IRC09:47
*** idan_hefetz has quit IRC09:47
*** ifat_afek_ has quit IRC09:48
*** omer_etrog_ has quit IRC09:49
*** amir_gur has quit IRC09:50
*** mkoushnir has quit IRC09:50
*** alexey_weyl has quit IRC09:51
*** baoli has joined #openstack-meeting-309:51
*** eyalb has quit IRC09:52
*** alex_xu has quit IRC09:56
*** elisha_r has quit IRC09:57
*** vgridnev has quit IRC09:57
*** baoli has quit IRC09:57
*** alex_xu has joined #openstack-meeting-309:58
*** vgridnev has joined #openstack-meeting-309:58
*** vgridnev has quit IRC09:58
*** vgridnev has joined #openstack-meeting-309:59
*** JeanBriceCombebi has quit IRC10:01
*** JeanBriceCombebi has joined #openstack-meeting-310:02
*** ihrachys has quit IRC10:02
*** ihrachys has joined #openstack-meeting-310:03
*** eliqiao has quit IRC10:06
*** salv-orl_ has joined #openstack-meeting-310:06
*** eliqiao has joined #openstack-meeting-310:06
*** piet has joined #openstack-meeting-310:06
*** lhartal has joined #openstack-meeting-310:07
*** markvoelker has joined #openstack-meeting-310:08
*** salv-orlando has quit IRC10:08
*** markvoelker has quit IRC10:13
*** zhurong has quit IRC10:14
*** JeanBriceCombebi has quit IRC10:14
*** JeanBriceCombebi has joined #openstack-meeting-310:16
*** ihrachys has quit IRC10:17
*** piet has quit IRC10:25
*** killer_prince has joined #openstack-meeting-310:26
*** lazy_prince has quit IRC10:29
*** tellesnobrega_af is now known as tellesnobrega10:30
*** armax has quit IRC10:30
*** spzala has joined #openstack-meeting-310:32
*** salv-orl_ has quit IRC10:35
*** spzala has quit IRC10:37
*** ihrachys has joined #openstack-meeting-310:39
*** killer_prince has quit IRC10:40
*** lazy_prince has joined #openstack-meeting-310:41
*** ifat_afek has joined #openstack-meeting-310:42
*** lhartal has quit IRC10:43
*** JeanBriceCombebi has quit IRC10:48
*** stanzgy_ has quit IRC10:50
*** stendulker_ has joined #openstack-meeting-310:50
*** JeanBriceCombebi has joined #openstack-meeting-310:50
*** stendulker has quit IRC10:53
*** stendulker_ has quit IRC10:56
*** alexpilotti has joined #openstack-meeting-311:02
*** sdake has joined #openstack-meeting-311:05
*** baoli has joined #openstack-meeting-311:07
*** ifat_afek has left #openstack-meeting-311:08
*** tellesnobrega is now known as tellesnobrega_af11:12
*** baoli has quit IRC11:12
*** lhartal has joined #openstack-meeting-311:14
*** dixiaoli_ has joined #openstack-meeting-311:17
*** neiljerram has quit IRC11:17
*** sdake has quit IRC11:20
*** lhartal has quit IRC11:21
*** neiljerram has joined #openstack-meeting-311:22
*** e0ne has joined #openstack-meeting-311:22
*** dixiaoli_ has quit IRC11:25
*** spzala has joined #openstack-meeting-311:33
*** spzala has quit IRC11:38
*** egallen has quit IRC11:40
*** fawadkhaliq has quit IRC11:42
*** fawadkhaliq has joined #openstack-meeting-311:42
*** pcaruana has joined #openstack-meeting-311:44
*** jkraj has joined #openstack-meeting-311:48
*** maurosr has quit IRC11:48
*** JeanBriceCombebi has quit IRC11:49
*** baoli has joined #openstack-meeting-311:51
*** chestack has joined #openstack-meeting-311:51
*** njirap has joined #openstack-meeting-311:52
*** tmazur has quit IRC11:53
*** maurosr has joined #openstack-meeting-311:54
*** tmazur has joined #openstack-meeting-311:55
*** baoli has quit IRC11:57
*** masco has joined #openstack-meeting-311:59
*** sdake has joined #openstack-meeting-312:01
*** tmazur has quit IRC12:01
*** tmazur has joined #openstack-meeting-312:03
*** masco has left #openstack-meeting-312:04
*** vgridnev has quit IRC12:07
*** ajmiller has quit IRC12:07
*** zhurong has joined #openstack-meeting-312:07
*** ajmiller has joined #openstack-meeting-312:07
*** markvoelker has joined #openstack-meeting-312:09
*** vgridnev has joined #openstack-meeting-312:10
*** jlanoux has quit IRC12:10
*** rtheis has joined #openstack-meeting-312:13
*** markvoelker has quit IRC12:14
*** vgridnev has quit IRC12:15
*** baohua has joined #openstack-meeting-312:19
*** vgridnev has joined #openstack-meeting-312:21
*** dims has joined #openstack-meeting-312:23
*** egallen has joined #openstack-meeting-312:31
*** spzala has joined #openstack-meeting-312:34
*** salv-orlando has joined #openstack-meeting-312:35
*** dixiaoli_ has joined #openstack-meeting-312:37
*** pcaruana has quit IRC12:37
*** spzala has quit IRC12:40
*** salv-orlando has quit IRC12:40
*** baoli has joined #openstack-meeting-312:42
*** e0ne has quit IRC12:42
*** primeministerp has joined #openstack-meeting-312:46
*** yamamoto_ has quit IRC12:49
*** claudiub has joined #openstack-meeting-312:52
*** jlanoux has joined #openstack-meeting-312:52
*** e0ne has joined #openstack-meeting-312:52
*** itxaka_ has joined #openstack-meeting-312:54
*** Poornima has quit IRC12:54
*** itoader has joined #openstack-meeting-312:55
*** itxaka has quit IRC12:57
*** kvinod has joined #openstack-meeting-312:59
*** kvinod has quit IRC13:02
*** kvinod has joined #openstack-meeting-313:02
alexpilotti#beginmeeting hyper-v13:02
*** lpetrut has joined #openstack-meeting-313:02
alexpilotti#startmeeting hyper-v13:03
openstackMeeting started Wed Jan 27 13:03:00 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:03
*** openstack changes topic to " (Meeting topic: hyper-v)"13:03
openstackThe meeting name has been set to 'hyper_v'13:03
*** atuvenie has joined #openstack-meeting-313:03
alexpilottimorning folks13:03
alexpilottikvinod: sonu and sagar are joining us today?13:03
kvinodhi all13:03
*** sagar_nikam has joined #openstack-meeting-313:03
kvinodalexpilotti: Sagar will join in 10 min and Sonu will not be able to make it13:04
sagar_nikamHi All13:04
kvinodoh Sagar is in13:04
sagar_nikamjust a bit late13:04
alexpilottihi all!13:04
alexpilotti#topic FC13:04
*** openstack changes topic to "FC (Meeting topic: hyper-v)"13:04
alexpilottisagar_nikam: any updates on the reviews by any chance?13:05
sagar_nikamalexpilotti: Kurt and Hemna are in cinder midcycle meetup13:05
sagar_nikamhence reviews are delayed13:05
sagar_nikamwill ping them again13:06
*** chestack has quit IRC13:06
alexpilottiabout midcycle, claudiub is at the Nova one. Any updates already worth sharing here?13:07
claudiuba loooot of talk about the scheduler and resource pools basically13:07
alexpilotti#topic Nova midcycle updates13:07
*** openstack changes topic to "Nova midcycle updates (Meeting topic: hyper-v)"13:07
claudiubapparently, in the future the scheduler might be a separate project itself13:07
alexpilottiwow, right about time, if you ask me :)13:08
claudiubas there is talk about networking resource pools and volume resource pools, basically cinder and neutron to use the same scheudler13:08
*** david-lyle has quit IRC13:08
claudiubanyways, using the jaypipes' resource pools, the storage problem on the cluster will be solved.13:09
alexpilottiany target release? e.g. N or O?13:09
claudiubbut the thing is, it a 7 part spec, so, for M, they say the first 3 will be implemented13:09
claudiubthe rest will be for N.13:09
*** markvoelker has joined #openstack-meeting-313:09
alexpilottiok, so our nephews will use it, got it :)13:10
alexpilotticlaudiub: are those first 3 realistically merging in M?13:10
sagar_nikamany discussion on drivers ? separate project for nova drivers ? like we have in neutron13:11
claudiubother than that, a lot of discussion for libvirt's live migration, they are going to move away from the current implementation with ssh, which is slow13:11
claudiubalexpilotti: yeah, that is the plan13:11
*** coolsvap is now known as coolsvap|away13:11
*** itxaka__ has joined #openstack-meeting-313:11
alexpilotticlaudiub: hyper-v has by far the best live migration, hopefully that wont require bit changes on our side13:11
claudiubalexpilotti: but i don't think those 3 will be enough to solve the problem, as the last part is the scheduler part, which is the most important for solving this issue13:12
* alexpilotti sobs13:12
claudiubas for splitting the drivers, no, same things, unfortunately13:12
claudiubalthough, there's a new project on the block, called os-vif13:12
alexpilotticlaudiub: any other relevant updates from the midcycle front?13:12
claudiubwhich is going to refactor the vif stuff from nova and neutron into a separate project13:13
claudiubso, I think any ovs vif plugging we have in nove would go there.13:13
sagar_nikamfrom which release ? N or O ?13:13
claudiubas for other updates, specs for N are open, going to try to get live-resize approved.13:14
*** markvoelker has quit IRC13:14
claudiubsagar_nikam: you mean the os-vif? there are still a couple of issues that have to be addressed before it officially replace the vifs in nova13:14
claudiubso, it's a work in progress at the moment13:15
*** itxaka_ has quit IRC13:15
claudiubas for other things, for the second day, its been mostly cross-project topics with neutron and cinder mostly13:16
claudiubi guess one thing that we'll have to take care of in the future, is the neutron hyper-v ml2 driver13:16
claudiubas it will have to be changed, to return an os-vif versioned object13:17
claudiubfrom what I understood.13:17
alexpilottiif there are no other questions, I'd go w the next topic13:19
sagar_nikamno from my side13:19
alexpilotti#topic networking-hyperv scalability13:20
*** openstack changes topic to "networking-hyperv scalability (Meeting topic: hyper-v)"13:20
alexpilottithe pymi + threading patches are pretty good to go13:20
alexpilottiwe're keeping the original BP that kvinod created13:21
*** e0ne has quit IRC13:21
alexpilottisince anyway it does not refer to implementation details13:21
sagar_nikamtested for all scenarios ? will we now have a version of pyMI ?13:21
kvinodwhat I understand from claudiub is that the existing rst file will be modified with the implemented approach13:22
alexpilottisagar_nikam: we are testing on all the scenarios that we already discussed13:22
*** JeanBriceCombebi has joined #openstack-meeting-313:22
alexpilottikvinod: yep claudiub is rewriting the spec to match the current implementation13:22
claudiubkvinod: yeah, I knew I was forgetting something last night. :(13:22
alexpilottisagar_nikam: do you think you could test the patches in the meantime?13:23
alexpilottiwe're also testing sonu's patch13:23
kvinodI have already conveyed this in review link but wanted to bring this up again13:23
sagar_nikamkvinod: thala: testing, can you add these patches13:23
sagar_nikamin that way we can check the perf with pyMI and the patches13:24
kvinodsagar_nikam: sure will ask thala he is on leave till Thursday13:24
sagar_nikamkvinod:ok, please let him know that the patches need to be included13:25
sagar_nikamhis tests are on liberty, so the patches needs to be liberty based13:25
sagar_nikamkvinod: some work needs to be done before it is given to thala13:25
alexpilottialinb tested it, found some issues but most probably due to the that fact that sonu's neutron patch was not there on the neutron side13:25
kvinodmy comment on native thread was about using the existing patches which were already committed rather then creating new one13:26
alexpilottiso we'll provide a complete update ASAP as soon as we test w the updated neutron master13:26
alexpilottikvinod: which patches?13:26
sagar_nikamalexpilotti: thala will be testing liberty + pyMI, since that is what we requested him last meeting. does the same plan hold good today as well ?13:27
*** tellesnobrega_af is now known as tellesnobrega13:27
alexpilotticlaudiub: we can use networking-hyperv master on liberty, correct?13:28
kvinodwe could have used this one rather than creating a new one13:28
claudiubalexpilotti: Don't really think so, requirements are different, so it could conflict with nova requirements.13:29
alexpilottikvinod: the implementation differs13:30
kvinodyes agreed but the concept and few file contents were same13:30
alexpilotticlaudiub: since they are testing on liberty, does it make sense to prepare a backport now?13:30
kvinodwe could have uploaded the new patches on top of existing one with new implementation approach13:31
claudiubbackport what?13:31
claudiubsorry, my attention is split in 3 directions. :(13:31
kvinodthe changes were already in master13:31
claudiubthe native threads ones?13:32
alexpilottithe liberty native threads patches13:32
*** dedery_ has joined #openstack-meeting-313:32
*** edleafe has quit IRC13:32
claudiubwell, the native threads implementation is fairly straightforward and simple, we could.13:32
kvinodclaudiub: agreed, the implementation is straight and good13:33
alexpilottisince HP has already a scheduled test run, we can add it on top, w/o having to wait for another test run13:33
alexpilottisagar_nikam: when is thala going to do run the tests?13:34
*** dedery has quit IRC13:35
*** spzala has joined #openstack-meeting-313:35
sagar_nikamalexpilotti: probably on friday, we should be able to delay by one or two days13:35
sagar_nikamis monday a good day to start the tests ? india monday morning13:36
kvinodalexpilotti: Thala scheduled the test and went on leave, we will login to his setup and collect the results13:36
alexpilottikvinod: can we add some bits to networking-hyperv or it's "sealed"?13:37
sagar_nikamkvinod: the next tests-- with the patches, can it be re-run on monday ? setup available on monday13:37
kvinodwe did not had his setup details so was not able to collect the results13:37
kvinodalexpilotti: Anyways the test might have completed by now, if required we can bring in the changes and schedule the test again13:38
kvinodProbably on Friday or Monday13:39
sagar_nikamkvinod: that will be good13:39
*** vgridnev has quit IRC13:39
alexpilottikvinod: some Hyper-V Windows updates came in very recently that apparently fixed the VLAN issue13:39
sagar_nikamalexpilotti: are there any patches which you want to apply for the next run of tests ?13:39
*** vgridnev has joined #openstack-meeting-313:39
alexpilottialinb has to come back with details, in case it'd be very important to have it in your setup13:40
alexpilottisagar_nikam: the networking-hyperv liberty backport if we have enough time to prepare them :-)13:40
kvinodalexpilotti: so apart from native thread patch you want to pull windows recent update?13:40
*** sdake_ has joined #openstack-meeting-313:40
alexpilottikvinod: yes, the goal is to run always on 100% udpated OSs13:40
sagar_nikamalexpilotti: we should be able to wait for some time, by when will those patches be available ?13:41
alexpilottithere were a few prereq that I sent to thala13:41
*** spzala has quit IRC13:41
alexpilotticlaudiub or alinb will backport them, by early next week we can have them13:41
kvinodalexpilotti:so thala already knows which and how to pull the windows update13:42
sagar_nikamkvinod: i think we should delay thala: next tests till early next week13:42
*** sdake has quit IRC13:42
alexpilottidepends really on when you want to run the tests13:42
alexpilottiwe run scenario tests very often, so it does not really matter13:43
sagar_nikami think the next tests should have the latest windows updates and the patches13:43
kvinodsagar_nikam: then in that case let us know when to trigger the test13:43
alexpilottion the other side since your planning takes more time, we prefer to be flexible around your scheduling13:43
alexpilottikvinod: and the high perf powercfg scheme13:44
*** krtaylor has quit IRC13:44
sagar_nikamkvinod: lets wait to hear from alexpilotti: when the patches are ready and then use them13:44
*** davidsha has joined #openstack-meeting-313:44
kvinodalexpilotti: sagar_nikam: fine13:44
alexpilottisagar_nikam cool!13:44
alexpilottinext topic13:45
sagar_nikamalexpilotti: as soon the patches are ready, let us know13:45
alexpilotti#topic Hyper-V cluster13:45
*** openstack changes topic to "Hyper-V cluster (Meeting topic: hyper-v)"13:45
kvinodalexpilotti: wanted to know when you are planning to merge the Enhanced RPC Changes done by Sonu13:45
*** markvoelker has joined #openstack-meeting-313:45
alexpilottikvinod: as soon as we have tests results from alinb13:46
kvinodBlueprint spec is created and commit message is modified13:46
kvinodok, in the mean time I will upload the .rst file13:46
alexpilottiI wrote you above that we had issues but most probably due to the missing neutron patch that just merged13:46
alexpilottikvinod: no need for an RST for this one13:46
alexpilottiit's quite straight forward13:47
kvinodalexpilotti: fine, will not upload it13:47
kvinodi mean the rst file13:47
claudiubkvinod: also, unit tests should be added on the enhanced rpc patch.13:47
alexpilottiback to the topic13:47
*** baohua_ has joined #openstack-meeting-313:47
alexpilottisonu wrote that he's adding them13:48
*** baohua has quit IRC13:48
*** julim has joined #openstack-meeting-313:48
kvinodclaudiub: I added one to test the newly added function and committed13:48
alexpilottifolks: we have a different topic now :-)13:49
kvinodclaudiub: please review and let me know anything additional required13:49
sagar_nikamalexpilotti: how is the cluster driver progressing ?13:49
alexpilottihere we go13:49
kvinodsorry, please continue with topic13:49
alexpilottiatuvenie is porting it from the original kilo implementation to mitaka13:50
alexpilottisome important areas13:50
alexpilottivolumes: ensuring that passthrough volumes are logged in the target host during a failover is quite tricky13:51
alexpilottithe first implementation will support SMB3 volumes13:51
alexpilottiwhich is also MSFT's recommended approach13:51
*** absubram has quit IRC13:51
*** tmazur has quit IRC13:52
alexpilottifor iSCSI / FC, we're investigating how to trigger an event on the target and block the VM start until all LUNs are mounted13:52
alexpilottiin short, replicating what happens for live migration13:52
*** tmazur has joined #openstack-meeting-313:53
alexpilottion the other side, the interaction with Nova became easier since we dont have to explicitly call into the conductor13:53
alexpilottithanks to the new versioned objects, this becomes more transparent13:54
alexpilottithe patches will be ready in the short term (February)13:54
*** numans has quit IRC13:55
*** sagar_nikam_ has joined #openstack-meeting-313:55
sagar_nikam_i got disconnected13:55
sagar_nikam_i am back13:55
primeministerpwelcome back13:55
*** fawadkhaliq has quit IRC13:55
sagar_nikam_alexilotti: what about iscsi and FC volumes ?13:55
*** fawadk has joined #openstack-meeting-313:55
alexpilottisagar_nikam_: talked about it while you were disconnected :-)13:56
sagar_nikam_for cluster driver13:56
primeministerpsagar_nikam_, :<alexpilotti> for iSCSI / FC, we're investigating how to trigger an event on the target and block the VM start until all LUNs are mounted13:56
alexpilottisagar_nikam_: in short: SMB3 now, iSCSI / FC later13:56
*** sagar_nikam has quit IRC13:56
*** numans has joined #openstack-meeting-313:56
sagar_nikam_later as in Mitaka or N ?13:57
sagar_nikam_in compute-hyperv ?13:57
*** vishwanathj_ has joined #openstack-meeting-313:57
alexpilottiwe need also to contain the patches if we want to hope for merging them in N or O13:57
alexpilottithey will go straight in compute-hyperv in Mitaka of course13:57
alexpilottiand we might even think about a Liberty backport if customers ask, but that's a separate topic13:57
sagar_nikam_alexpilotti: in Mitaka, compute-hyperv will have support for iscsi and FC for cluster driver ?13:58
alexpilottiwe're alsmost out of time13:58
alexpilottisagar_nikam_: depends if we find a feasible solution13:58
alexpilottisagar_nikam_: the issue is with how the clustering works13:58
alexpilottithe VM gets migrated before we can trigger an event and mount the LUNs on the target13:59
sagar_nikam_lets discuss in detail in next meeting13:59
alexpilottiresulting in I/O issues13:59
sagar_nikam_we are almost out of time now13:59
*** jkraj has quit IRC13:59
alexpilottiwe have a few ideas in an embryonal state13:59
sagar_nikam_can we have this topic as first topic next meeting ?13:59
alexpilottiwhich require some C/C++ native components on the cluster side13:59
alexpilottisagar_nikam_: sure14:00
alexpilottiok guys time's up!14:00
alexpilottithanks for joining!14:00
kvinodthanks, bye14:00
*** openstack changes topic to "OpenStack Meetings ||"14:00
openstackMeeting ended Wed Jan 27 14:00:37 2016 UTC.  Information about MeetBot at . (v 0.1.4)14:00
openstackMinutes (text):
*** atuvenie has quit IRC14:00
*** kvinod has quit IRC14:00
*** ShillaSaebi has joined #openstack-meeting-314:01
*** JeanBriceCombebi has quit IRC14:01
*** JeanBriceCombebi has joined #openstack-meeting-314:02
*** ShillaSaebi has left #openstack-meeting-314:02
*** julim_ has joined #openstack-meeting-314:02
*** ShillaSaebi_ has joined #openstack-meeting-314:03
*** edleafe has joined #openstack-meeting-314:03
ajohi ihrachys , irenab , hdaniel14:03
hdanielhi ajo14:03
*** reedip_ has joined #openstack-meeting-314:03
ajohi hdaniel  :)14:04
ajook, I'll leave 3 more minutes,14:05
*** sdake_ is now known as sdake14:05
*** julim has quit IRC14:05
*** vikram has joined #openstack-meeting-314:07
ajohi vikram14:07
*** moshele has joined #openstack-meeting-314:07
ajook, moshele , irenab , hdaniel , ihrachys , vikram , let's start14:07
ajo#startmeeting neutron_qos14:08
openstackMeeting started Wed Jan 27 14:08:10 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:08
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:08
openstackThe meeting name has been set to 'neutron_qos'14:08
ajoHi everyone :-)14:08
ajo#link The usual etherpad-agenda14:08
*** alexpilotti has quit IRC14:08
ajoLast meeting was a bit lonely, due to strange things with ics, or human error and misleading from my side :)14:09
*** yamamoto has joined #openstack-meeting-314:10
ajoWe had a couple of things merged since last meeting14:10
*** njirap has left #openstack-meeting-314:10
ajoRBAC spec: .. yey hdaniel !14:10
ajoand Validation for ml2 extension driver to be enabled when qos service plugin is used with the plugin:
ajoyes slawek, probably more QoS related stuff was merged,14:11
*** yamamoto_ has joined #openstack-meeting-314:11
ihrachysprolly. let's not celebrate for too long look at stuff NOT merged :)14:11
ihrachys*and look14:12
*** lblanchard has joined #openstack-meeting-314:12
ajo#topic Tracking items14:12
*** openstack changes topic to "Tracking items (Meeting topic: neutron_qos)"14:12
*** fawadk has quit IRC14:12
ajoIf somebody dares to call me optimist, will be right. I'm still working in the RPC callback rolling upgrade core logic:
*** neelashah has joined #openstack-meeting-314:12
ajoI was working on another patch right now, and I will continue after meeting, it looks considerable well, thanks ihrachys for the reviews14:13
*** salv-orlando has joined #openstack-meeting-314:13
*** sagar_nikam_ has quit IRC14:13
reedip_ajo : Hello14:13
ajohi reedip_ welcome14:13
*** ^Gal^ has joined #openstack-meeting-314:14
ihrachysI think we should be almost there with it; as long as tests are ready.14:14
ihrachyshonestly, I was not checking those since it seemed to me we should shake API first.14:14
ajoihrachys, yes, I think my current testing is reasonable, but I'm the writer, probably I must do an extra pass and verify I'm not missing stuff14:14
*** itoader has quit IRC14:14
ajoihrachys, ack, let's get into testing afterwards14:15
*** yamamoto has quit IRC14:15
ajoalso, I mush push a second patch for integration with the agent, adding some db migrations, I have a version locally for that which I haven't updated lately, now it's out of sync with the core logic api14:15
*** fawadkhaliq has joined #openstack-meeting-314:15
ihrachysI suggest we get the first piece in, then care about the 2nd one14:16
*** fawadkhaliq has quit IRC14:16
*** alexpilotti has joined #openstack-meeting-314:16
ajoyes, this is why I'm not updating the 2nd part patches without the 1st part being ready, it's too much rework every time14:16
ajowasted work14:16
*** vhoward has joined #openstack-meeting-314:16
ajook, so let's keep that rolling, and going forward,14:16
*** david-lyle has joined #openstack-meeting-314:17
ajoas a note, when this ( is ready, the DSCP patches will need to be rebased on top of it14:17
ajobut now that breaks the world,14:17
ajoand it's quite far from my local version14:17
ihrachysajo: it's already based on l2-agent-extensions patch, I bet we don't want to have too deps14:17
ihrachys*two deps14:18
*** vhoward has quit IRC14:18
*** piet has joined #openstack-meeting-314:18
*** vhoward has joined #openstack-meeting-314:18
ajook, they probably don't need the dept14:18
*** piet has quit IRC14:19
ajoor to rebase on top of mine, as long as it's not merged until rpc callbacks upgrade support is merged14:19
ihrachyswe'll manage the order manually14:19
*** piet has joined #openstack-meeting-314:19
ihrachysnot that there are people pushing the patch apart from us :)14:19
ajoihrachys: can we use the Depends-On for that?14:20
ajoihrachys, will the gate check the dependency is merged before ?14:20
ihrachysajo: we can, in theory. but I would keep test failures separate14:20
*** dims has quit IRC14:21
ihrachysajo: if you depends-on, you get all failures from all patches14:21
*** spzala has joined #openstack-meeting-314:21
ihrachysand honestly, I would not be bothered by dscp piece right now until we get the deps in. the deps are the blockers that concern me a lot.14:21
ajook, let's try to move the upgrades quicker,14:22
ajook, next topic then14:22
ajo#topic RBAC status14:22
*** openstack changes topic to "RBAC status (Meeting topic: neutron_qos)"14:22
ajohdaniel, could you update about RBAC integration status? :)14:23
*** slaweq has joined #openstack-meeting-314:23
hdanielthe patch is rewritten - to be used in a more "magical" way14:23
hdanielper ihrachys suggestion - I've added metaclass to inject the functionality14:23
hdanielwill push first wip patch today.14:24
*** tellesnobrega is now known as tellesnobrega_af14:24
hdanielwait, till you see it ,14:24
ihrachysok let's see it first indeed :D14:24
hdanielthe client's patch needs to be rebased too, but I didn't have the time yet14:24
ajoI must admit, magical sounds good and worrying ;D14:25
ajofor example, mixins could seem magical at first sight14:25
ajoso, let's see it :D14:25
hdanielmixins are like mushrooms - they are magical, but there's a price to pay ..14:25
hdanielok, so I'm pretty sure I'll push the WIP draft today14:26
ihrachyssounds reassuring :)14:26
ajothanks hdaniel  :)14:26
ajook, next topic14:26
ajo#topic Linux bridge integration14:26
*** openstack changes topic to "Linux bridge integration (Meeting topic: neutron_qos)"14:26
ajoslaweq, the stage is yours14:26
slaweqok, so14:27
slaweqmy patch for qos in linuxbridge is (I hope) almost ready14:27
slaweqmost reviewers gave "+1" for this14:27
ihrachysit was pretty clean the last time I checked, yes14:27
*** peristeri has joined #openstack-meeting-314:27
slaweqI have to update some docs and release notes to it14:27
ihrachyswe need fullstack, that's the concern now I guess14:27
slaweqbut I'm still fighting with this fullstack tests support14:27
ihrachyshave you tried to add rootwrap filters as I suggested before?14:28
slaweqthat is not so easy for linuxbridge (I'm testing connectivity there)14:28
slaweqihrachys: not yet14:28
slaweqI'm in business trip this week and I have not too much time to do this14:28
slaweqbut I hope to do it today or tomorow14:28
ihrachysthat's fine. note that I will be pretty much off the next week.14:29
slaweqFYI: fullstack test for connectivity is passing for me with linuxbridge but when I run it as root14:29
*** baohua_ has quit IRC14:29
slaweqwhen I run it as normal user that linuxbrigde agent is not spawning properly14:29
slaweqand test is failing14:29
ajoslaweq, looks like the root wrap filters for fullstack then14:29
*** Swami has joined #openstack-meeting-314:29
ihrachys...and we suspect it may be missing IpNetNs rootwrap filter for lb agent14:29
slaweqso I have to solve this issue and do some (big) refactoring to address all coments from reviewers14:30
slaweqajo, ihrachys: yes, it looks like that :)14:30
ihrachysslaweq: pay special attention to John's comments, he is our fullstack guru :)14:30
slaweqbut I have to check it and check where I should configure rootwrap rules for tests14:30
slaweqI know where to add it for "normal" working scripts but not for tests14:31
*** rossella_s has quit IRC14:31
ihrachysright. I think you need to run as part of fullstack target14:31
ihrachysas we do for functional target14:31
*** rossella_s has joined #openstack-meeting-314:31
slaweqok, thx for tips ihrachys14:32
ihrachysok, I guess we have a plan here.14:32
ihrachyslet's move on14:32
slaweqso generally it is all about linuxbridge14:32
ajothanks slaweq and ihrachys  :)14:32
ajo#topic DSCP markings14:32
*** openstack changes topic to "DSCP markings (Meeting topic: neutron_qos)"14:32
ajonjohnston, vhoward , any update on the topic?14:32
ihrachysI need to admit I haven't looked into the code lately. was spending time on reviews for ajo and David for l2-agent-extensions.14:33
ajoyes, I was going to point that out14:33
ihrachysright, that one14:33
ihrachysI think we are mostly ok with API part, just need testing coverage14:33
*** jpomeroy has joined #openstack-meeting-314:34
ajois David around?14:34
ajodavidsha, ping :)14:34
*** galstrom_zzz is now known as galstrom14:35
davidshaHi, sorry14:35
ajoI'd loop yamamoto and ann to check the patch :)14:35
davidshaNate said he was working on tests for the l2-agent14:35
*** dims has joined #openstack-meeting-314:36
davidshaI'm working my way through the comments.14:36
ihrachysoh nice that you do stuff in parallel. :)14:37
ihrachysI try to get back to the patch every day, hopefully I down slow down it14:37
ihrachysajo: ok, I will add them.14:37
ajoI have pinged yamamoto_, akamyshnikova on irc, but cannot find Ann's email14:38
ajoihrachys, : thanks14:38
*** spzala has quit IRC14:38
ajo#topic Open discussion14:38
*** openstack changes topic to "Open discussion (Meeting topic: neutron_qos)"14:38
ajoanybody want's to raise any other topic or important bug?14:38
* ajo looks at the bug list14:39
reedip_ajo : pimg14:39
ajohi reedip, go ahead :)14:39
ihrachysI just want to say we need more reviews on our patches in general14:39
irenabajo: any update on scheduling part?14:39
ihrachysoh scheduling... I saw today the spec was -1'd14:39
ihrachysdue to some parallel effort from inside nova14:40
ajoihrachys: yes, probably I should be spending my time more in QoS patches instead of other stuff14:40
vikramajo: can you plz help approving
openstackLaunchpad bug 1505631 in neutron "QoS VLAN 802.1p Support" [Wishlist,New] - Assigned to Reedip (reedip-banerjee)14:40
*** spzala has joined #openstack-meeting-314:40
ihrachysvikram: it will be discussed on next drivers meeting14:40
ajoihrachys, : true, I need to look at the other approach, I looked at it once a month ago, and it didn't look like compatible with what we wanted to do, but may be it's able to model our problem and I just didn't get it14:40
ihrachyson one of next meetings ;)14:40
vikramihrachys: thanks14:40
irenabajo: the neutron side RFE for reporitng actual bw was rejected14:41
ajovikram, , correct, it has the same RPC callback upgrade support dependency as DSCP does,14:41
ihrachysajo: yeah, we should clarify that with nova folks before they get too far in their implementation14:41
vikramajo: yup14:41
reedip_wow , open discussion indeed :)14:41
*** yamamoto_ has quit IRC14:41
ihrachysirenab: I think it was sort of 'postponed'14:41
ajoirenab, yes, as ihrachys said, we need to clarify who pushes that, and how14:41
ihrachysjust because we are not sure how scheduler will work14:42
reedip_ajo: I just wanted to share about
openstackLaunchpad bug 1505627 in neutron "QoS Explicit Congestion Notification (ECN) Support" [Wishlist,New] - Assigned to Reedip (reedip-banerjee)14:42
ajoif it's going to be the agents, we don't need centralised reporting to neutron-server14:42
irenabajo: ihrachys agreed14:42
ajoif somebody has some time to analyze again the other nova spec14:42
ajoit would be great14:42
ajoI have not enough bandwidth currently :(14:42
ajo#link  resource-providers: generic resource pools14:43
ajomay be every host can be a resource pool...14:43
ihrachysirenab: are you up for the challenge? :)14:43
ajobut then , we'd have to see how to integrate us updating the resource pool details... I almost don't remember14:43
irenabihrachys: I am afraid I am over my BW currently14:43
ajomay be jaypipes is up and around ;)14:43
ihrachysthat's sad14:44
*** david-lyle has quit IRC14:44
ihrachyswell, we'll get to it some time14:44
*** dedery_ has quit IRC14:44
ihrachysajo: should we have some todo in etherpad?14:44
ajoreedip_, vikram we may look at that when we have bandwidth: but please, move this to etherpad.openstack.org14:45 can be eventually deleted14:45
ajoit's just a demo14:45
reedip_ajo : ok, in a minute14:45
ajoihrachys, isn't that the track items?14:46
ajoihrachys,  slow moving are the ones unnatended14:46
ihrachysajo: yeah, but it's like a general scheduler thing. we need some details like the link to the alternative spec14:46
ihrachysoh sorry, I see it's ther14:46
reedip_ajo, vikram, ihrachys:
ajoihrachys, np, making it more clear14:47
ihrachysok, that's fine now14:47
ajothanks reedip_, link it to the bug so it doesn't get lost14:48
*** yamamoto has joined #openstack-meeting-314:48
*** david-lyle has joined #openstack-meeting-314:48
reedip_already done ajo14:48
ajoanything else ?14:49
ajoor shall we do the farewell dance ? :)14:50
* ihrachys dances14:50
ajolol :)14:50
*** tellesnobrega_af is now known as tellesnobrega14:50
*** zz_dimtruck is now known as dimtruck14:50
jaypipesajo: I'm in the Nova mid-cycle...14:50
jaypipesajo: how can I help you?14:50
ajohi, jaypipes :)14:50
ajook, let's not end the meeting, we have 10 more minutes14:51
ajowe were talking about your spec:
ajoand we wonder if we could use your model to track available bandwidth in hosts14:51
ihrachystrack and decide on14:51
ajoyes, and decide on, for instance scheduling purposes14:51
ajojaypipes,  ^14:52
jaypipesajo: yes, I am almost done with the next revision which has a description of the use case of routed networks in Neutron and using generic resource pools in Nova to give the cloud user ability to specify a port and have Nova able to understand that that port is in a particular subnet, which is attached to a particular segment and that segment is attached to a rack of compute nodes.14:52
*** e0ne has joined #openstack-meeting-314:53
jaypipesajo: oh... bandwidth...14:53
ajojaypipes, ok, that's related, and probably more detailed the our intent14:53
*** david-lyle has quit IRC14:53
jaypipesajo: sorry, that wasn't the use case I talked abotu with Carl.14:53
ajojaypipes, correct, it's something differnt14:53
*** shinya_kwbt has joined #openstack-meeting-314:53
ajoour intent was to track available bandwidth on hosts14:53
ajotowards providing bandwidth guarantees to instance ports14:53
ihrachysyeah, Carl cares about L3, but here we have QoS case.14:53
jaypipesajo: the problem with QoS and bandwidth is that unlike other resources, bandwidth is an entirely transient thing. it changes from minute to minute.14:54
ajojaypipes, not for guarantees14:54
ajojaypipes, for guarantees you need to know the total host bandwidth (ingress & egress) over each specific physical network14:54
*** rhochmuth has joined #openstack-meeting-314:54
jaypipesajo: it's not a quantifiable resource, though... it's a qualitative assertion about something.. more of a capability than a resource.14:54
ajoand then, it's left to the underlaying technology, to make sure the bandwidth limits and guarantees are kept within limits14:55
ajothe important constraint is14:55
*** piet has quit IRC14:55
ajoon a physical network:  sum(port[i].guaranteed_bw) < total_bw on that physnet14:55
ajofor an specific host14:55
*** sigmavirus24_awa is now known as sigmavirus2414:55
*** piet has joined #openstack-meeting-314:56
*** tej has joined #openstack-meeting-314:56
*** ho_away has joined #openstack-meeting-314:56
ajothe idea is that no instance would be scheduled to that host, if it's using a port with an specific bw requirement, that we won't be able to guarantee14:56
jaypipesajo: what is the difference between "guaranteed bw" and normal bw?14:56
ajobecause we'd be overcommitting the host14:56
*** dandruta has joined #openstack-meeting-314:56
ajojaypipes, : the idea of the guarantee is that14:57
ajoyou provide a minimum bandwidth for a port (instead of a maximum)14:57
jaypipesajo: no, sorry, lemme rephrase my question...14:57
*** rbak has joined #openstack-meeting-314:57
ajoso, in any case, if the port is trying to use that bandwidth, (or more) it's packets are sent first14:57
*** yamamoto has quit IRC14:57
ajothen the packets of ports with no guarantees are sent14:57
*** oheydorn has joined #openstack-meeting-314:58
ajoor the packets of ports with lower guarantees (or already sending over it's minimum bandwidth guarantee)14:58
jaypipesajo: if a port has 100 total bw capacity, and 10 instances are given 10 guaranteed bw units each, is there some other process (not an instance, or some privileged thing?) that can consume bandwidth on that port and essentially overcommit the port to more bandwidth than SUM(port[i].guaranteed_bw)?14:58
*** bmotz has joined #openstack-meeting-314:58
ajothere are a few ways to do it, but basically it's based on queues and packet prioritisation14:58
ihrachysthe assumption here of course is that underlying infra is capable to handle any bandwidth from any compute node14:59
ajojaypipes, if the guaranteed ports and not using the traffic, the unguaranteed can use it14:59
*** e0ne has quit IRC14:59
ajoihrachys,  correct14:59
ajothat's another level of complexity I don't feel capable of tackling yet14:59
ihrachysjaypipes: well, it does not require ideal fit, it's best effort14:59
jaypipesajo, ihrachys: so I think the current modeling of generic resource pools will be able to meet these needs.15:00
*** shwetaap has joined #openstack-meeting-315:00
ajojaypipes, thanks for the feedback, I will re-read your spec as soon as I can15:00
ihrachyscool with me :)15:00
jaypipesajo, ihrachys: or at least the latest (almost ready to be uploaded) patch's model will meet those needs ;)15:00
ajoan try to fit our needs with your model15:00
ihrachyswe need to consider the case, that's all we are asking :)15:00
jaypipesyup, of course.15:00
ajothanks a lot :)15:00
ajoI'm ending the meeting15:00
ihrachysthanks a lot for replying!15:00
*** openstack changes topic to "OpenStack Meetings ||"15:00
openstackMeeting ended Wed Jan 27 15:00:56 2016 UTC.  Information about MeetBot at . (v 0.1.4)15:00
openstackMinutes (text):
rhochmuth#startmeeting monasca15:01
openstackMeeting started Wed Jan 27 15:01:24 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:01
*** openstack changes topic to " (Meeting topic: monasca)"15:01
*** witek has joined #openstack-meeting-315:01
openstackThe meeting name has been set to 'monasca'15:01
reedip_bye ..15:01
rhochmuthhi everyone15:02
rhochmuthwe have a pretty light agenda today15:02
rhochmuthAgenda for Wednesday January 27, 2016 (15:00 UTC)15:02
rhochmuth1. Is monasca-common published automatically to pypi ?15:02
rhochmuthSo, I'll open it up for discussion after we cover that item15:02
*** tgraichen has joined #openstack-meeting-315:02
rhochmuth#topic monasca-common15:02
*** openstack changes topic to "monasca-common (Meeting topic: monasca)"15:02
rhochmuthCurrently, it is not published to pypi15:02
rhochmuththat needs to get resolved15:03
rhochmuthIs this urgent for someone to resolve?15:03
*** e0ne has joined #openstack-meeting-315:05
witek0.0.4 is there15:05
rhochmuthit is?15:05
*** jobrs has joined #openstack-meeting-315:05
*** JeanBriceCombebi has quit IRC15:05
rhochmuthinteresting, i thought it was in pypi15:05
rhochmuththen i looked at the catalog and i cant' find it15:05
rhochmuthso i thought i was wrong15:06
rhochmuthbut pip install works15:06
rhochmuthand it is listed15:06
*** andymaier has joined #openstack-meeting-315:06
rhochmuthso, is this just a catalog issue?15:06
rhochmuthIs it just the pypi index/catalog isn't listing it15:06
*** rbrndt has joined #openstack-meeting-315:07
rhochmuthIf you search for monasca-common it isn't listed15:07
*** MarkAtwood has joined #openstack-meeting-315:08
*** yamamoto has joined #openstack-meeting-315:08
*** jmckind has joined #openstack-meeting-315:09
rhochmuthSo, my guess is something is not completely correct, but it is in pypi15:09
rhochmuthOK, next topic15:09
shinya_kwbtI searched now, but I can't see list neither.15:09
rhochmuthAre there other items to cover today15:10
rbakI can give a grafana update15:10
rhochmuth#topic grafana15:10
*** openstack changes topic to "grafana (Meeting topic: monasca)"15:10
rbakI've put up the fork with keystone authentication here:
rbakI know some people found that already.15:11
rbakI've also solved using that authentication to provide tokens for the data source, so this is close to being done.15:11
tgraicheni have taken it and i have keystone v3 basically working already15:11
rhochmuthwasn't there a directory for grafana-plugins15:11
rbakI sent an email to grafana to start talking about getting this upstream15:11
rhochmuthhow is that going15:12
rbakHaven't heard back on that, I only sent the email last night.15:12
rbakBut it's getting close.15:12
*** piet has quit IRC15:13
rhochmuthso, does this directory include all your code15:13
rbaktgraichen: Just submit a pull request on my branch once your v3 keystone auth is ready15:13
*** JeanBriceCombebi has joined #openstack-meeting-315:13
rhochmuthwasn't there a grafana-plugins repo15:13
witek#link Grafana fork15:13
rbakThere is a separate repo which has the grafana datasource15:13
tgraicheni see one little thing for keystone v3 - for that we would need another input for the domain name in the login screen ... so far i have hardcoded the domain via config option15:13
rbakAlso worth noting, the format for datasource plugins changed again.15:14
tgraichenrbak: is your code to use the token from auth for the datasource in the tree already?15:15
rbakSo if anyone is having trouble with the latest code working with the monasca plugin, I do have a patch for that15:15
rbaktgraichen: Not yet. I haven't quite finished it, I just managed to prove I could do it yesterday.15:15
*** michael-hoppal has joined #openstack-meeting-315:15
rhochmuthso, if i pull your latest repo, does it work, or do i need the patch15:15
rbakIf you install the latest release of grafana you can use the monasca datasource in grafana-plugins15:16
rbakIf you pull the latest code and build, you'll need my patch15:16
rbakI'll put it up at some point, but I didn't want to mess up anyone who was using the datasource with the latest release15:17
tgraichenmaybe we should move the monasca plugin into the grafana tree as well until we are merged to grafana upstream?15:17
rbakSounds reasonable.  I'll do that after the meeting.15:18
tgraichencool - thx ... and big thx for your keystone v3 preparations in the code - it was quite easy to add by filing the gaps you left15:18
rbakI'll leave the monasca-plugin fork with the code for the latest release, and but the fully up to date monasca code in the grafana fork15:18
*** yamamoto has quit IRC15:19
tgraichensounds very good - will create a pull request with my keystone v3 stuff later today15:19
rbakSounds good15:19
*** JOlsen has joined #openstack-meeting-315:19
rbakI think that's all I had15:19
rhochmuththx rbak15:19
rhochmuth#topic midcycle15:20
*** openstack changes topic to "midcycle (Meeting topic: monasca)"15:20
rhochmuthi just want to mentiont again that the midcycle is next week15:20
rhochmuthit will be remote via webex15:20
rhochmuthThe Agenda, data, time and location is at15:21
rhochmuthI'm the only attendees listed right now15:21
rhochmuthIt would be good if folks start filling out information15:21
rhochmuthin the agenda section15:21
rhochmuthI see some items related to send sms15:21
rhochmuthand add to skype15:21
rhochmuthso, those topics seem to be related to the notificatino engine15:22
rhochmuththe other items listed are the logging api and performance15:22
*** catherineD|2 has joined #openstack-meeting-315:22
rhochmuthso, please fill out the etherpad with topics that you would like to cover and i'll try and organize15:22
ho_away is there any conditions to join the mid-cycle? (so far i didn't contribute monasca...)15:23
rhochmuthho_away: there are no conditions15:23
rhochmuthit is open to anyone15:23
rhochmuthso your topic of anomaly detection would be a good one15:23
ho_awayrhochmut: cool!15:23
rhochmuthi saw your email posting15:23
rhochmuthi think there was only one other response asking questions around the current status of it15:24
ho_awayrhochmuth: yeah, i tried to get someone's interest but it failed :-)15:24
rhochmuthcurrent status of the monasca anomaly prediction engine15:24
*** piet has joined #openstack-meeting-315:24
rhochmuthwell, there were some folks last week that seemed interested15:24
rhochmuthand then there is me15:25
rhochmuthso, if you woudl like i can go over what i've done and we can share ideas15:25
rhochmuthi'm interested in hearing what your ideas in this area are15:26
ho_awayrhochmuth: really? it's appreciate15:26
*** zhurong has quit IRC15:26
ho_awayrhochmuth: we have some POC around IT analytics but it's not related to monasca now15:26
rhochmuthho_away, so please add an agenda item15:27
rhochmuthand we can start discussions next week15:27
ho_awayrhochmuth: to mid-cycle?15:27
ho_awayrhochmuth: i will add it :-)15:27
rhochmuthplease also feel free to start sharing ideas via email or the openstack-dev list15:28
ho_awayrhochmuth: thanks! if i get no response, i might get big damage... :-)15:29
rhochmuthwell, we can talk next week15:29
rhochmuthso, are there other topics15:29
rhochmuthare there reviews folks want me to llok at15:29
*** JeanBriceCombebi has quit IRC15:29
rhochmuthwe've recovered from the CI problems we had last week15:30
*** yamahata has quit IRC15:30
rhochmuthso, i'm trying to catch up on reviews15:30
rhochmuthwe have a lot of outstanding ones15:30
*** jmckind has quit IRC15:30
*** yamahata has joined #openstack-meeting-315:30
rhochmuthwitek: Did you every look at all the reviews and pull requests to the ansible changes, that i was having trouble with15:31
*** MarkAtwood has quit IRC15:31
*** iyamahat has joined #openstack-meeting-315:31
*** dixiaoli_ has quit IRC15:31
witekyes, i'm testing it15:32
*** vishwanathj has joined #openstack-meeting-315:32
witeki had problems with smoke tests15:32
*** alexpilotti has quit IRC15:32
*** mtanino_ has joined #openstack-meeting-315:32
witekhad to downgrade monasca-notification15:32
rhochmuthhmmm, i was seeing different problems15:32
rhochmuthlet me know if you want me to test that again15:32
witekyes, I will let you know, when I'm done15:33
rhochmuthAlso, i see that you have a proposal for the log apu batching up15:33
rhochmuthtsv and his team did some performane analysis15:33
witekit's a follow-up after the chaotic discussion last week :)15:34
rhochmuthtsv's analysis shows > 12X improvement going to batch15:34
*** JeanBriceCombebi has joined #openstack-meeting-315:34
witekyes, i can believe that15:34
rhochmuthso, if anyone wants/needs some reviews bumped up let me know and i'll see what i can do now that we are getting out of the mess we were in past week15:36
*** krtaylor has joined #openstack-meeting-315:36
*** jmckind has joined #openstack-meeting-315:36
witekwe don't have restrictions in requirements any more15:36
witeki'm not sure, but it could be, we monasca-vagrant is not working now15:37
witeki'm not sure, but it could be, why monasca-vagrant is not working now15:37
*** alexpilotti has joined #openstack-meeting-315:37
rhochmuthi wasn't aware monasca-vagrant was broken15:37
rhochmuthi'll need to take a look15:37
rhochmuthbut, that could be the reason15:37
witekmonasca-notification does not start15:38
*** MarkAtwood has joined #openstack-meeting-315:38
witekafter downgrade it does15:38
rhochmuthi'll verify here15:38
*** vgridnev has quit IRC15:38
*** yamamoto has joined #openstack-meeting-315:39
witeknice, thanks15:39
*** dimtruck is now known as zz_dimtruck15:39
*** alexpilotti has quit IRC15:39
rhochmuthok, i think we are done for the day15:39
*** alexpilotti has joined #openstack-meeting-315:39
rhochmuthsee everyone next week15:40
*** fawadkhaliq has joined #openstack-meeting-315:40
witekthank you Roland15:40
witeksee you15:40
*** fawadkhaliq has quit IRC15:40
tgraichensee you15:40
*** fawadkhaliq has joined #openstack-meeting-315:40
*** zz_dimtruck is now known as dimtruck15:40
*** openstack changes topic to "OpenStack Meetings ||"15:41
openstackMeeting ended Wed Jan 27 15:41:13 2016 UTC.  Information about MeetBot at . (v 0.1.4)15:41
openstackMinutes (text):
*** ho_away has left #openstack-meeting-315:41
*** rbrndt has left #openstack-meeting-315:41
*** liangy has joined #openstack-meeting-315:42
*** Sukhdev has joined #openstack-meeting-315:43
*** vgridnev has joined #openstack-meeting-315:43
*** witek has quit IRC15:43
*** shinya_kwbt has quit IRC15:43
*** nkrinner has quit IRC15:44
*** michael-hoppal has quit IRC15:50
*** matrohon has quit IRC15:51
*** adi__ has quit IRC15:57
*** tgraichen has quit IRC15:58
*** vgridnev has quit IRC15:59
*** Aish has joined #openstack-meeting-316:00
eglute#startmeeting defcore16:00
openstackMeeting started Wed Jan 27 16:00:06 2016 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** gema has joined #openstack-meeting-316:00
*** openstack changes topic to " (Meeting topic: defcore)"16:00
openstackThe meeting name has been set to 'defcore'16:00
egluteHello everyone, please raise your hand if you are here for DefCore meeting16:00
eglute#topic agenda16:00
*** openstack changes topic to "agenda (Meeting topic: defcore)"16:00
egluteAgenda: #link please review and add/edit as needed16:00
egluteHello gema and markvoelker!16:01
gemahello :D16:01
egluteChris Hoge will not be able attend today's meeting16:01
*** Cathy_ has joined #openstack-meeting-316:01
*** dwalleck has joined #openstack-meeting-316:01
eglutenot sure if we are getting more people to join us today16:02
eglute#topic board report16:02
*** openstack changes topic to "board report (Meeting topic: defcore)"16:02
egluteyesterday during the board meeting board approved 2016.01.json guideline16:03
egluteas well as 2016A process document16:03
*** cbouch has joined #openstack-meeting-316:03
*** numans has quit IRC16:04
eglutehad a couple questions, but nothing major.16:04
*** rmoe has quit IRC16:04
eglutethe next board meeting is at the end of February, so if we need something approved then, we can16:04
eglute#topic Electing DefCore CoChair during next meeting16:05
*** openstack changes topic to "Electing DefCore CoChair during next meeting (Meeting topic: defcore)"16:05
*** rmoe has joined #openstack-meeting-316:05
egluteSo the patch for changing defcore cochair description was out for a very short time16:05
eglutemarkvoelker and Rob commented, but I didnt really get other feedback16:06
*** salv-orl_ has joined #openstack-meeting-316:06
*** AlanClark has joined #openstack-meeting-316:06
eglutesince it was a bit rushed, I want everyone to know that if we need to make changes to the process, we can. The reason for rushing was that the process document requires board approval16:06
*** dcarmon has joined #openstack-meeting-316:06
markvoelkereglute: I got the impression that moving to a WG was something Board wanted to move toward anyway, so I'm generally fine with it.16:07
eglutemarkvoelker correct.16:07
egluteI spoke to Alan Clark, chairman of the board, about Rob's replacement as a co-chair (not that he is easy to replace)16:08
gemawhat is a WG?16:08
egluteWorking group16:08
egluteCommittee usually implies board committee16:09
*** salv-orlando has quit IRC16:09
eglutemeaning, run by the board, responsible to the board16:09
*** reedip_ has quit IRC16:09
egluteDefCore WG would still require board oversight16:09
*** brunssen has joined #openstack-meeting-316:09
egluteas is now, it will continue requiring approval to process documents as well as new capabilities16:09
*** banix has joined #openstack-meeting-316:10
eglutethe main change is that both cochairs would not be board appointed16:10
*** ShillaSaebi_ has quit IRC16:10
egluteonly one16:10
eglute if anyone have reservations/concerns about the change, i am available to talk about it here, or via email/phone. just let me know16:11
eglutei do hope that everyone sees this as a positive change16:11
*** bmotz has left #openstack-meeting-316:11
markvoelkereglute: I think the change invites more community participation, so ++./16:11
dwalleckmakes perfect sense to me16:11
eglutemarkvoelker i agree!16:12
gemaeglute: +116:12
eglutewhich brings up the next question: elections of the cochair16:12
egluteright now, the only requirement in the process document is that elections are announced 1 week before16:13
egluteOne DefCore CoChair needs to be elected by DefCore working group. Election16:13
eglute     quorum is composed of attendees present during the election meeting.16:13
eglutethis means we have to figure out a good election process16:14
eglutei would like the voting people to be comprised of people that usually participate, or have participated in the defcore discussions16:14
*** jobrs has quit IRC16:14
*** david-lyle has joined #openstack-meeting-316:14
egluteand for people nominated/running to be active participants16:14
egluteone of the suggestions i received was for people running to submit a gerrit patch, and voters do +1.16:15
* markvoelker notes that there was very brief discussion around this in
dwalleckeglute: To handle nominations or the actual vote?16:16
eglutedwalleck suggestion was for both16:16
markvoelkereglute: Submit a patch to...what, exactly?  E.g. are we creating a new text file that lists co-chairs or something?16:17
egluteanother suggestion is to have it in some form during actual meeting16:17
eglutemarkvoelker i think it would be a patch to declare candidacy. voters would +1 their candidate. this might be too formal though16:17
eglutei am ok with IRC polling as well16:18
eglutebut would like to hear ideas from others16:18
gemaeglute: the voting in the same way you did the choosing of midcycle location would also work16:18
markvoelkerHmm...I think I'd prefer something that doesn't require a specific time/place to cast a ballot so we can be more inclusive.  E.g. not at an IRC meeting.  But honestly everyone that's likely to cast a ballot it probably at our meetings anyway.16:19
eglutedoodle? Yes, I agree. I thought of it16:19
dwalleckI don't mind the idea of nominations through Gerrit, but doing the actual voting in Gerrit might be a bit complicated16:19
markvoelkerWhat about setting up a Condorcet?16:19
purpo/ (sorry to be late, catching up)16:19
gemamarkvoelker: yeah, but you are right, someone may miss a meeting due to other commitments and miss the opportunity to vote16:19
eglutemarkvoelker i thought of condorcet, that would mean we dont know who is voting i believe16:20
eglutehello purp we are discussing how to elect a cochair16:20
purpGot it. All caught up.16:20
egluteso, i am all for being inclusive, and we could open voting next week and close it one week later? whichever voting method we choose16:21
*** woodster_ has joined #openstack-meeting-316:21
dwalleckeglute: +116:21
gemaeglute: +116:21
*** mbound has quit IRC16:21
markvoelkerWorks for me16:22
purpeglute +116:22
eglutenow, the next question would be, open voting, where we see who votes for who, or closed16:22
*** yantarou has quit IRC16:22
purpI'd suggest if you've attended *n* DefCore meetings over the past cycle/period/minute, you're a voter.16:22
purpIt's equivalent to being an ATC to vote for PTL.16:23
eglutealso, Rob has volunteered to be ombudsman for collecting votes if needed16:23
eglutepurp i like that suggestion16:23
dwalleckI do also16:23
*** rtheis_ has joined #openstack-meeting-316:23
*** yantarou has joined #openstack-meeting-316:23
markvoelkerWell, for this election the Board pretty much already set who gets a vote, no?  "quorum is composed of attendees present during the election meeting."16:23
purpI think 12 > n > 316:23
egluteso, more than 3 meetings in 12 months?16:24
markvoelkerBut we could obviously fix that for next time16:24
purpmarkvoelker: Yeah, that was the bit I had a problem with.16:24
*** rtheis has quit IRC16:24
*** JasonF has joined #openstack-meeting-316:24
purpI'd say 3+ meetings in past cycle/6 months.16:24
*** NobodyCa1 has joined #openstack-meeting-316:24
*** NobodyCam has quit IRC16:25
*** JayF has quit IRC16:25
eglutemarkvoelker purp -- we could amend that during February board meeting i think. I am ok with having one week long elections16:25
egluteand not insisting on being present during the meeting16:26
purpeglute: +1 to amend for Condorcet elections and a criteria for "ATCs"16:26
*** rockyg has joined #openstack-meeting-316:26
*** NobodyCa1 is now known as NobodyCam16:27
egluteok, I will work on the patch, but will wait for after these elections. I suspect we will have more changes16:27
markvoelkerpurp: I think I need to noodle on ATC criteria a bit.  I like the idea of regular participation being more a metric than "contribution" (since we're not actually producing code here).  Not quite sure how to structure it though.16:27
*** MarkAtwood has quit IRC16:28
markvoelkerGenerally ++ on the idea though16:28
egluteso, for defcore ATC-- we do have irc logs, we would have to go through them and get a list of people16:28
*** tmazur has quit IRC16:28
purpmarkvoelker: fair, and no hurry. Do you have a particular concern, or just generally uneasy?16:28
*** vahidh has joined #openstack-meeting-316:29
purpeglute: Happy to write a snippet of code to do that. =]16:29
* purp never gets to write much code these days.16:29
dwalleckI think the summary at the end of each log lists the participants also16:29
eglutethanks purp!16:29
markvoelkerNot a particular concern, just want to be sure we're setting good criteria.16:29
*** Cathy_ has quit IRC16:29
purp#action purp to write a tool to summarize logged DefCore participation for a given time period16:30
* eglute lets purp know over the last 6 months we used 3 different chat rooms and need to account for midcycles which were in person16:30
rockygReviews of stuff would help as an indicaor16:30
markvoelkerdwalleck: true, though not necessarily a good measure of "participation".  E.g. you get your name on the log by simply saying o/. =)16:30
rockygEveryone who "speaks" gets listed16:30
*** dimtruck is now known as zz_dimtruck16:31
dwalleckmarkvoelker: Very true :D16:31
*** sambetts has joined #openstack-meeting-316:31
markvoelkerAnyway, I suggest we table the discussion for the moment and think on it some more, then come prepared next week with suggestions (or just propose patches to the process doc).16:31
eglutei think the o/ at the end of the log indicates they were here, and most do speak. very rarely it is just o/16:31
catherineD|2markvoelker: and sometime we forget to sau /o16:31
*** JeanBriceCombebi has quit IRC16:31
* rockyg sheepishly hopes no one notices she overslept16:31
purpmarkvoelker dwalleck rockyg: Figuring I'll start by summarizing the stats of attendance, # of meetings with participation, and overall IRC linecount during the period.16:31
rockygor even o/16:31
markvoelkerpurp: sounds useful16:32
gemaand sometimes people have weird nicknames like catherineD|2 today16:32
purpmarkvoelker: at least gives us a dataset to look at16:32
rockygOh yeah, the attendance also has number of lines spoken...16:32
egluteSo, when do we want to start elections? I am selfish and dont want to wait too long16:32
* purp nods at rockyg16:32
catherineD|2gema: :-)16:32
brunssenI think the sooner we can start elections the better, but we need to make sure we allow enough time to gather quality candidates.16:33
gemaeglute: as soon as we have a list of candidates?16:33
gemaand voters16:33
*** MarkAtwood has joined #openstack-meeting-316:33
rockygWell, one week after the list is complete....16:33
*** iyamahat has quit IRC16:33
purpeglute: you intend this one by the "whoever's in the meeting" rule, correct?16:34
eglutehow do we want to gather the list of candidates? self nominations? nominations by others? nominations via mailing list?16:34
markvoelkerI think we can probably get started proposing candidates right away, just need to work out the mechanics of the voting.16:34
brunssenI think send an email and let the community know that we are going to hold an election and there is a two week window to raise your hand or be nominated16:34
eglutepurp i think if there are enough objections i dont have to stick to that rule. I am ok with having one week long elections16:34
rockygYeah, my China comrades have already been pushing me.16:34
*** iyamahat has joined #openstack-meeting-316:35
*** itxaka__ has quit IRC16:35
purpCan I suggest that we mirror the PTL process relatively closely, then?16:35
rockygThey've finally gotten the hang of how to follow DefCore ;-)16:35
eglutewhich, if we have 1 week for candidates, 1 week to vote, that puts us out at least 2 weeks16:35
rockyg+1 on PTL process16:36
purpTake noms, self or other, determine what an ATC looks like here, then vote?16:36
eglutepurp i like that16:36
dwalleck1 week for each seems fair16:36
purprockyg: How? *I* still haven't got the hang of it.16:36
egluteStart nominations today? I will send out an email after the meeting16:36
*** sdake_ has joined #openstack-meeting-316:36
rockygI'll give you a hand :-)16:36
markvoelkereglute: ++16:36
purpeglute: +116:37
brunsseneglute: +116:37
purpeglute: If I nominate someone, do they have to ratify it?16:37
rockygYeah.  Self nominations with statement in an email to list16:37
eglutenominations will close next week by 10 AM CST: is everyone ok with that?16:37
* purp looks evilly at markvoelker and rockyg16:37
dwalleckeglute: sounds good16:37
eglutepurp yes, would like people to respond to the nomination accepting it16:37
gemapurp: you probably don't want a cochair that doesn't have the time16:37
rockygoh you sneaky purp!16:38
brunssenYes, I agree, that the nominee has to accept to be on the ballot16:38
*** belmoreira has quit IRC16:38
egluteso condorcet we need a list of voters emails, correct?16:38
*** david-lyle has quit IRC16:38
markvoelkereglute: yes16:38
*** slaweq has quit IRC16:38
egluteok, we will need to get a list of emails based on IRC handles16:39
rockyginfra can help with the election.  Or ttx16:39
egluterockyg good idea16:39
* purp is writing code already.16:40
*** vikram has quit IRC16:40
catherineD|2eglute: Also who can also get a list of people who had submitted, reviewed DefCore patches16:40
*** sdake has quit IRC16:40
*** sdake_ is now known as sdake16:40
*** slaweq has joined #openstack-meeting-316:40
*** david-lyle has joined #openstack-meeting-316:40
rockygcatherineD|2, ++16:41
purpcatherineD|2 I can grab that from Stackalytics.16:41
purpWill grab commits, emails, reviews as contribs.16:41
egluteI propose voting period to be from February 3rd till February 9th. so by February 10 we can be done16:41
catherineD|2great, I think that is one way to measure participation ...16:41
*** bpokorny has joined #openstack-meeting-316:41
eglutei agree on participation to include commits16:41
rockygThere can be reviewers that arn't on the IRC logs.   They may not be able to make the meetings.  But, that doesn't mean they don't follow all of this16:42
egluteso does anyone have issues with the timeline? nominations until next Wednesday, elections start next Wednesday, close before defcore meeting the following week?16:43
purpI'm pretty sure I can have interesting data up in an etherpad by end of weekend.16:43
* eglute thanks purp 16:43
*** liyi has joined #openstack-meeting-316:44
* rockyg thinks purp knows more than he's letting on16:44
egluteand eveyone ok with condorcet voting?16:44
purprockyg: yeah, but it's mostly '80s trivia and recipes for cooking game.16:45
egluteany other comments regarding elections? we will ask the board to approve new process during the february meeting16:45
*** oheydorn has quit IRC16:46
*** galstrom is now known as galstrom_zzz16:46
rockygsounds like we have it16:46
eglutegreat, thank you everyone for your input.16:47
eglute#topic DefCore Capabilities should have more than one test.16:47
*** openstack changes topic to "DefCore Capabilities should have more than one test. (Meeting topic: defcore)"16:47
*** vikram has joined #openstack-meeting-316:47
eglutei dont think we have a consensus on this. I would suggest we either review it again, or drop it16:48
*** zz_dimtruck is now known as dimtruck16:48
markvoelkereglute: actually, I think it just needs a commit message update.  The most recent patchset doesn't actually include a rule change at all.  It's just a re-grouping of tests.16:48
markvoelkerSo it's no longer about whether or not Capabilities should have more than one test or not at all16:49
egluteok, so if we update the commit message, move forward with regrouping?16:49
markvoelker(which was the controversial point)16:49
*** dwalleck has quit IRC16:49
rockygI'd say ask for more reviews/comments on mailing list and if still quiet, go for it.16:49
markvoelkerYEah, I think the regrouping was fine by most.16:49
egluteok, sounds good to me16:49
*** slaweq_ has joined #openstack-meeting-316:49
eglutemarkvoelker would you update the commit message?16:50
markvoelkereglute: sure, I can do that16:50
eglutethank you!16:50
*** bpokorny has quit IRC16:50
eglute#topic Next guideline will be 2016.08, to be approved during August 23rd board meeting.16:50
*** openstack changes topic to "Next guideline will be 2016.08, to be approved during August 23rd board meeting. (Meeting topic: defcore)"16:50
rockygmarkvoelker, could you take a look at my comment and see if I'm just an idiot?  Might be a dupe line in the file...16:50
markvoelker#action markvoelker will rewrite commit message for and everyone will review16:50
markvoelkerrockyg: will do16:50
eglutethank you markvoelker!16:50
*** bpokorny has joined #openstack-meeting-316:50
markvoelkerrockyg: you're right, I'll remove the dupe too16:51
* gema has to run early today, sorry!16:51
egluteregarding the next timeline, please review it in etherpad, see if it makes sense16:51
* eglute waves goodbye to gema16:51
*** vineetmenon has joined #openstack-meeting-316:51
eglutesince there is no board meeting in July, the approval would happen in august. meaning, next guideline would be 2016.0816:52
* markvoelker notes that the scoring deadline is a couple weeks after the midcycle, so would love to have folks ready to discuss in Austin16:53
eglutemarkvoelker good point16:53
*** slaweq has quit IRC16:53
egluteif there are no other questions/comments, next topic16:53
markvoelkerAre we pretty firm on the date/place for that now, by the way?  Enough that I should be booking a flight?16:54
eglutei am waiting for final confirmation from brunssen16:54
brunssenI am working with our facilities folks to get everything finalized.16:54
rockygOooh!  At IBM again?  Lonestar Motel, here I come!16:55
brunssenI am not worried about getting the space, just need to get final confirmation16:55
markvoelkerOk, cool.  Just light the bat signal when we're good to go. =)16:55
eglutebrunssen do you have estimated time for confirmation?16:55
brunssenI will do that.  Hope to know by the end of the day today.16:55
eglutethat would be great!16:55
brunssenOnce I know, I will send an email to eglute so she can distribute to the team.16:55
*** lpetrut has quit IRC16:55
purpCool. brunssen if something falls through, I can probably commit to hosting there, but need ~2 weeks notice to get contacts and logistics lined up.16:55
egluteand yes, Lone Star hotel has the best prices. I actually made reservations yesterday, thinking i can cancel just in case16:55
*** JeanBriceCombebi has joined #openstack-meeting-316:56
purpAre we talking about ?16:56
rockygIt's a great place to congregate after, too.16:56
brunssenThere also a bunch of new hotels near the IBM site that look nice in case any of you are working on points or airline miles :-)16:56
purpWow. Braker and Burnet has upgraded a bit since back when.16:56
brunssenThe Domain is a very nice area16:57
eglutebrunssen yes, but that one my corporate tool told to book, since it is the cheapest at the moment. lots of great other options too16:57
eglutewell, we are almost out of time16:57
eglute#topic DefCore submissions for OpenStack Summit16:57
*** openstack changes topic to "DefCore submissions for OpenStack Summit (Meeting topic: defcore)"16:57
egluteplease submit defcore related proposals!16:57
eglutei submitted the working group session, but no others16:58
*** galstrom_zzz is now known as galstrom16:58
eglutealso, sorry markvoelker we ran out of time for your topic. move it to defcore irc or wait for next week?16:58
*** hdaniel has quit IRC16:58
rockygWith the progress refstack is making, we might be ready for a "corporate" show and tell and demo16:58
markvoelkerIt's not urgent; it'll keep till next week16:59
egluterockyg that would be great!16:59
eglutethank you markvoelker16:59
catherineD|2rockyg: I think so ... The RefStack team is very busy in making this happens ...16:59
eglutei will be around in defcore irc if anyone wants to chat16:59
eglutethanks everyone!16:59
*** openstack changes topic to "OpenStack Meetings ||"16:59
openstackMeeting ended Wed Jan 27 16:59:48 2016 UTC.  Information about MeetBot at . (v 0.1.4)16:59
brunssenThank you16:59
openstackMinutes (text):
*** matrohon has joined #openstack-meeting-317:02
* vineetmenon wondering if we have cell v2 meet today!17:02
*** jlanoux has quit IRC17:03
*** brunssen has quit IRC17:04
*** vahidh has quit IRC17:04
*** vishwanathj_ has quit IRC17:05
*** yamahata has quit IRC17:07
*** yamamoto has quit IRC17:07
*** numans has joined #openstack-meeting-317:07
*** jaypipes has quit IRC17:07
*** vtech has quit IRC17:09
*** vishwanathj has quit IRC17:11
*** JeanBriceCombebi has quit IRC17:12
*** claudiub has quit IRC17:12
*** andymaier has quit IRC17:12
*** slaweq_ has quit IRC17:13
*** aarefiev has quit IRC17:13
*** jmckind_ has joined #openstack-meeting-317:13
*** iyamahat has quit IRC17:13
*** kebray has joined #openstack-meeting-317:15
*** kebray has quit IRC17:15
*** ihrachys has quit IRC17:15
*** kebray has joined #openstack-meeting-317:15
*** matrohon has quit IRC17:16
*** salv-orl_ has quit IRC17:16
*** jmckind has quit IRC17:16
*** aarefiev has joined #openstack-meeting-317:17
*** neelashah has quit IRC17:17
*** dandruta has quit IRC17:24
*** vahidh has joined #openstack-meeting-317:27
*** davidsha has quit IRC17:27
*** lazy_prince has quit IRC17:27
*** kebray has quit IRC17:28
*** iyamahat has joined #openstack-meeting-317:29
*** neelashah has joined #openstack-meeting-317:31
*** yamahata has joined #openstack-meeting-317:31
*** vikram has quit IRC17:32
*** dcarmon has quit IRC17:32
*** iyamahat has quit IRC17:33
*** iyamahat has joined #openstack-meeting-317:33
*** krtaylor has quit IRC17:41
*** armax has joined #openstack-meeting-317:42
*** kebray has joined #openstack-meeting-317:42
*** jed56 has quit IRC17:43
*** mbound has joined #openstack-meeting-317:43
*** mbound has quit IRC17:44
*** neelashah has quit IRC17:45
*** vineetmenon has quit IRC17:45
*** vahidh has quit IRC17:46
*** vahidh has joined #openstack-meeting-317:47
*** fawadkhaliq has quit IRC17:51
*** vahidh has quit IRC17:52
*** sdake has quit IRC17:53
*** krtaylor has joined #openstack-meeting-317:53
*** salv-orlando has joined #openstack-meeting-317:53
*** mbound has joined #openstack-meeting-317:54
*** kebray has quit IRC17:58
*** Aish has quit IRC17:58
*** dims has quit IRC17:58
*** Sukhdev has quit IRC17:59
*** kebray has joined #openstack-meeting-318:00
*** neelashah has joined #openstack-meeting-318:01
*** ajmiller has quit IRC18:02
*** armax has quit IRC18:02
*** ajmiller has joined #openstack-meeting-318:02
*** kebray has quit IRC18:03
*** sambetts has quit IRC18:06
*** moshele has quit IRC18:06
*** Swami has quit IRC18:06
*** Aish has joined #openstack-meeting-318:10
*** dimtruck is now known as zz_dimtruck18:15
*** jpomeroy has quit IRC18:15
*** SridarK has joined #openstack-meeting-318:16
*** doug-fish has quit IRC18:16
*** neiljerram has quit IRC18:18
*** madhu_ak has joined #openstack-meeting-318:18
*** mbound has quit IRC18:18
*** mickeys has joined #openstack-meeting-318:20
*** ihrachys has joined #openstack-meeting-318:20
*** doug-fish has joined #openstack-meeting-318:22
*** galstrom is now known as galstrom_zzz18:23
*** zz_dimtruck is now known as dimtruck18:25
*** Swami has joined #openstack-meeting-318:25
*** safchain has quit IRC18:25
*** vtech has joined #openstack-meeting-318:26
*** vhoward has quit IRC18:26
*** vhoward has joined #openstack-meeting-318:26
*** neelashah has quit IRC18:26
*** doug-fish has quit IRC18:27
*** annp has joined #openstack-meeting-318:27
*** ihrachys has quit IRC18:28
sc68calhi all18:29
SridarKHi All18:29
sc68cal#startmeeting networking_fwaas18:30
openstackMeeting started Wed Jan 27 18:30:29 2016 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:30
*** openstack changes topic to " (Meeting topic: networking_fwaas)"18:30
openstackThe meeting name has been set to 'networking_fwaas'18:30
sc68cal#chair xgerman SridarK18:30
openstackCurrent chairs: SridarK sc68cal xgerman18:30
*** annp has quit IRC18:31
sc68calI've been a little busy with multinode grenade and MTUs this week and haven't had a chance to do any fwaas stuff18:31
sc68calSridarK and xgerman - if you guys have anything to drive today's meeting please do18:32
*** kebray has joined #openstack-meeting-318:32
xgermansame here - lot’s of internal stuff for me + getting used to versioned objects takes time18:32
*** annp has joined #openstack-meeting-318:32
xgermanwe need to figure out who does the versioned objects...18:32
*** jwarendt has joined #openstack-meeting-318:33
xgermanI might be able to but will be a while18:33
xgermanso if somebody has spare cycles...18:33
SridarKi too have been on some internal stuff, but i am beginning to get something basic for fw policy going then i can get a basic fw group methods in18:33
SridarKthen we can look at the agent communication18:33
SridarKyes i have not started looking at the versioned objects either - i need to get a basic fw group standing b4 even getting there18:34
SridarKi will try to have something up by end of the week18:34
xgermanyeah, they seem like a pain18:34
SridarKthen we can start discussing the agent interface18:34
xgermanso i will keep poking at those then...18:34
SridarKyes seems like more understanding is needed on that18:34
*** doug-fish has joined #openstack-meeting-318:35
SridarKwill Aish have some cycles to help as well18:35
*** jmckind_ has quit IRC18:35
SridarKok that is good18:36
xgermanI will try to loop her in…18:36
xgermanjwarendts said he will have some CLI patch up soon18:37
SridarKsc68cal: i will add some stuff around policy and fw group to the db patch18:37
sc68calSridarK: ok18:37
xgermanyeah, I think we all will need to chain on that patch18:37
xgermanwhich brings me to our dev startegy18:38
xgermanin LBaaS we were running a 8 patch deep chain for V218:38
*** jmckind has joined #openstack-meeting-318:38
xgermanalternaticely we can merge things since they don’t do anything (especially DB)18:38
sc68callets defer that decision.18:39
xgermandependency chains are painful… so I would prefer merging whenever possible18:39
xgermansc68cal ok18:39
sc68calI don't think we should merge things just for the sake of merging. We'd need to have very good unit test coverage before considering that18:39
xgermanwell, can we get the DB part to get there?18:40
SridarKyes having some things merge make it easier to deal with but i think this is something that is frowned upon to push things without the backend18:40
*** doug-fish has quit IRC18:40
xgermandependency chains it is ;-)18:40
mickeysI have also been sidetracked by other stuff over the past week, but I have managed to spend some cycles bringing my colleague Sukanya up to speed. She will be helping me out with the firewall driver.18:41
sc68calalso - please make sure you are setting your topic correctly when pushing patches to gerrit - the -t option of "git review"18:41
SridarKoh good that we can add another resource18:41
AishSridarK: yes, I shall work along with xgerman18:41
*** vahidh has joined #openstack-meeting-318:42
mickeysWe need to focus on changes to Neutron security groups first. Two changes we are looking at. One is singleton for conntrack management, with some restructuring to get all the conntrack stuff under the conntrack manager.18:42
mickeysThe other one is the jump to the firewall chain. We want to investigate a singleton approach, should be a lot cleaner than a jump from security groups to firewall and sprinkling is_sg_enabled all over the place.18:43
xgermanis anyone going to the neutron mid cycle to champion those patches?18:43
xgerman(anyone with travel budget:-)18:43
mickeysNot planning to18:43
SridarKor mickey u can make ur boss a proxy ;-)18:43
mickeysNot a bad thought ...18:43
*** vahidh_ has joined #openstack-meeting-318:44
SridarKsc68cal: on the topic - it should be fwaas_v2_api correct ?18:44
*** vahidh__ has joined #openstack-meeting-318:44
xgermanwell, our lt. dougwig should also be working for us there :-)18:44
*** vahidh_ has quit IRC18:44
sc68calskath_: yep18:45
sc68calSridarK: yep18:45
SridarKgood thx18:45
*** shwetaap has quit IRC18:45
mickeysFor the driver, I put fwaas_v2_driver through the patch, after pushing the first patch set18:45
mickeysthrough the web18:45
mickeysI think one of the other patch sets was just fwaas_v218:46
*** vahidh has quit IRC18:46
xgermanI am I think I ignored that alltogether18:46
mickeysxgerman: Your patch set currently has topic "l2_agent"18:48
mickeysRoey's is the one with topic "fwaas_v2"18:48
xgermanyep, that’s what I meant...18:48
sc68callet's try and fix our topics up - so that we can easily see the whole chain of patches18:49
sc68calthe easiest thing to do is create a branch in your local git repo - git review uses that for the topic18:49
sc68calso ... fwaas_v2_api as your branch18:49
* sc68cal grumbles18:49
*** spzala has quit IRC18:49
xgermanok, will do for future patches18:49
*** galstrom_zzz is now known as galstrom18:50
xgermanand also chain mine on top of FDB18:50
*** shwetaap has joined #openstack-meeting-318:50
*** spzala has joined #openstack-meeting-318:50
xgermansince I need the versioned objects18:50
SridarKi think the dependency chain is like:  REST -- DB  -- Plugin -- Agent -- Driver18:51
*** s3wong has joined #openstack-meeting-318:51
xgermanwell, then we need another patch18:51
xgermanREST-DB-versioned Objects - Plugin -...18:52
SridarKsc68cal: has the resource ext patch out i believe18:52
SridarKok so for this versioned obj now will need another patchset ?18:53
xgermanor we shoehorn that into the plugin18:53
SridarKwe can do that too18:53
xgermanI just thought if Aish/I work on that an extra patch would be better18:54
SridarKthats fine - whichever is easier18:54
*** spzala has quit IRC18:54
*** sdake has joined #openstack-meeting-318:54
xgermanI think an extra patch gives us more flexibility18:54
*** doug-fish has joined #openstack-meeting-318:55
*** ivar-lazzaro has joined #openstack-meeting-318:56
SridarKother things to discuss ?18:57
xgermanI am good18:57
*** badveli has joined #openstack-meeting-318:57
SridarKif no one has other points to discuss we can get some time back18:58
*** openstack changes topic to "OpenStack Meetings ||"18:58
openstackMeeting ended Wed Jan 27 18:58:45 2016 UTC.  Information about MeetBot at . (v 0.1.4)18:58
openstackMinutes (text):
SridarKBye all18:58
*** doug-fish has quit IRC19:00
*** doug-fish has joined #openstack-meeting-319:01
*** galstrom is now known as galstrom_zzz19:01
*** doug-fis_ has joined #openstack-meeting-319:02
*** doug-fi__ has joined #openstack-meeting-319:03
*** SridarK has quit IRC19:05
*** doug-fish has quit IRC19:06
*** numans has quit IRC19:06
*** doug-fis_ has quit IRC19:07
*** jpomeroy has joined #openstack-meeting-319:09
*** e0ne has quit IRC19:13
*** primeministerp has quit IRC19:15
*** piet has quit IRC19:15
*** Sukhdev has joined #openstack-meeting-319:23
*** ihrachys has joined #openstack-meeting-319:24
*** e0ne has joined #openstack-meeting-319:25
*** bpokorny_ has joined #openstack-meeting-319:29
*** bpokorny_ has quit IRC19:29
*** bpokorny_ has joined #openstack-meeting-319:29
*** moshele has joined #openstack-meeting-319:30
*** bpokorny has quit IRC19:32
*** jwang_ has quit IRC19:33
*** hdaniel has joined #openstack-meeting-319:34
*** jwang has joined #openstack-meeting-319:36
*** piet has joined #openstack-meeting-319:36
*** spzala has joined #openstack-meeting-319:37
*** galstrom_zzz is now known as galstrom19:40
*** egallen has quit IRC19:40
*** neelashah has joined #openstack-meeting-319:40
*** ihrachys has quit IRC19:44
*** ihrachys has joined #openstack-meeting-319:45
*** kebray has quit IRC19:46
*** neelashah has quit IRC19:47
*** egallen has joined #openstack-meeting-319:47
*** badveli has quit IRC19:48
*** evgenyf has quit IRC19:49
*** neelashah has joined #openstack-meeting-319:51
*** dims has joined #openstack-meeting-319:53
*** Sukhdev has quit IRC19:57
*** hurgleburgler has joined #openstack-meeting-319:58
*** matt-borland has joined #openstack-meeting-319:58
*** tyr_ has joined #openstack-meeting-319:59
*** ihrachys has quit IRC19:59
*** tqtran has joined #openstack-meeting-320:00
david-lyle#startmeeting Horizon20:00
openstackMeeting started Wed Jan 27 20:00:45 2016 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** ying_zuo has joined #openstack-meeting-320:00
*** openstack changes topic to " (Meeting topic: Horizon)"20:00
openstackThe meeting name has been set to 'horizon'20:00
*** robcresswell has joined #openstack-meeting-320:00
hurgleburgler( ಠ‿ಠ)┘20:01
*** MarkAtwood has quit IRC20:01
david-lyleLet's roll20:02
david-lyleWe tagged M-2 last week20:02
david-lyleso we're officially in the race to the end20:03
*** tsufiev has joined #openstack-meeting-320:03
david-lyletarget date for M-3 March 3rd20:03
*** r1chardj0n3s_afk has joined #openstack-meeting-320:04
david-lyleis essentially the same as last week20:05
david-lyleso I won't belabor it20:06
*** barra204 has quit IRC20:06
*** mickeys has quit IRC20:06
david-lyleI don't have any other general items. There were a couple on the agenda20:06
*** r1chardj0n3s_afk is now known as r1chardj0n3s20:06
david-lyle#topic Categorizing incoming bugs20:07
*** openstack changes topic to "Categorizing incoming bugs (Meeting topic: Horizon)"20:07
tsufievI thought now there should be much fewer opened themization patches :)20:07
david-lylelhcheng added this item, but I think I can speak to it20:08
hurgleburglerI can help with that20:08
david-lylethe volume of bugs that comes in to Horizon via launchpad is quite large20:08
david-lyleit would be worlds better to have someone actively watching them as they come in to triage/classify them20:09
david-lyleotherwise we get into our current state with 400 uncategorized bugs20:09
david-lylewhen we were smaller, I could watch that too, but I cannot handle that any more20:09
david-lylehurgleburgler: did you volunteer?20:10
robcresswellI think hurgleburgler volunteered20:10
hurgleburglerI can help out20:10
david-lyleI should have not said anything else20:10
hurgleburglerI can help categorize, but I can't say I'd be the only one ;)20:10
david-lyleit's a gloriously rewarding pleasure cruise20:11
matt-borlandI can help hurgleburgler20:11
hurgleburglerdavid-lyle I'm not sure I believe you20:11
tqtranso as we move away from a central horizon to plugin, we can encourage people to file bug their own respective repo instead20:11
robcresswellI'm working on reducing the total too. We've knocked about 1/3 off the uncategorised since first bug day, and about 120 from total iirc.20:11
robcresswelltqtran: We've already removed all the trove and sahara bugs.20:12
robcresswellThese are mostly outs.20:12
tqtranew... gl matt-borland and hurgleburgler!20:12
tsufievmany bugs I´ve seen there are actually feature requests20:12
david-lylethank you matt-borland and hurgleburgler20:12
*** egallen has quit IRC20:12
david-lyletsufiev: we do have the wishlist category20:13
robcresswelltsufiev: If they are small, wishlist, if big, mark invalid and ask for blueprint.20:13
david-lyleI give up on trying to figure out how OpenStack thinks bugs and features should be tracked20:13
tsufievdavid-lyle, robcresswell: got it20:13
*** evgenyf has joined #openstack-meeting-320:13
david-lylematt-borland, hurgleburgler I will add you to the horizon-bug team so you can do the things20:14
hurgleburgler┏(^0^)┛┗(^0^) ┓20:14
* matt-borland updating todo list20:14
* tsufiev imagines whole Horizon community walks in one of intra task-tracking sessions and start demanding new task tracker20:14
r1chardj0n3s"congrats" hurgleburgler an matt-borland :-)20:14
*** vtech has quit IRC20:14
tsufievI join the congratulations :)20:15
tyr_Would "bug review" fit as a natural, regular part of each release? Say...the first 2 weeks after a Summit?20:15
david-lyleok added20:16
*** Sukhdev has joined #openstack-meeting-320:16
*** neelashah1 has joined #openstack-meeting-320:16
tsufievtyr_, unfortunately bugs are being added all the time :(20:16
david-lyletyr_: I would prefer an ongoing process20:16
robcresswelltyr_: No, its too constant to do it that way20:16
robcresswellWe'd be ignoring 5.5 months of bugs every time20:16
david-lylemy biggest concern is missing High/Critical defects20:16
*** neelashah has quit IRC20:16
tsufievtyr_, besides that we had already 2 Bug Days20:16
robcresswellPlus RC1 is already supposed to be bug cleanup time.20:17
david-lylethat could have been fixed prior to release20:17
tyr_I understand that, and am not suggesting there isn't regular maintenance...just curious about having a bug party phase of the release. Perhaps it is already RC1.20:17
*** julim_ has quit IRC20:17
david-lyletyr_: certainly not a bad endeavor for the weeks between release and summit20:18
robcresswellI have enough difficulty recruiting people for a single bug day :)20:18
tyr_e.g. please don't pester the cores about our pet features during this window because we are collectively focused on bugs. Just an idea.20:18
david-lylebut that's mostly the RC cycle for cores20:19
*** ivar-lazzaro has quit IRC20:19
david-lyleor at least should be20:19
*** tej has quit IRC20:19
*** ivar-lazzaro has joined #openstack-meeting-320:19
david-lyleI'm for anything that raises the visibility of bugs and their solutions :)20:20
*** tej has joined #openstack-meeting-320:20
david-lyleeven to the detriment of landing features20:20
david-lylebut I'm going to move on20:20
r1chardj0n3s(aka "new bugs")20:20
*** hdaniel has quit IRC20:20
david-lyle#topic QA and Cross project liaison, need a volunteer20:21
*** openstack changes topic to "QA and Cross project liaison, need a volunteer (Meeting topic: Horizon)"20:21
*** ivar-lazzaro has quit IRC20:21
david-lyleThere are a ton of cross project liaison roles for each project in OpenStack20:21
david-lylethese two are currently open20:22
tsufievwhat are QA liason responsibilities?20:22
*** egallen has joined #openstack-meeting-320:22
david-lyletsufiev: quite honestly, for Horizon not much20:22
tsufievoh, Tempest/Grenade, I´m staying away from that20:22
david-lyletsufiev: well think about our tempest footprint, 1 test20:23
david-lyleadditionally, it's on my list to make that a tempest plugin20:23
tsufievbut if that is related to integration testing of Horizon against the rest of Openstack, I may sign in20:23
*** madhu_ak has quit IRC20:23
tyr_I'm interested in the Cross Project Spec Liaison.20:24
*** bpokorny_ has quit IRC20:24
*** ihrachys has joined #openstack-meeting-320:24
*** bpokorny has joined #openstack-meeting-320:24
*** ivar-lazzaro has joined #openstack-meeting-320:24
tsufievdavid-lyle, is there any place besides with some info about this role?20:25
*** tej has quit IRC20:25
david-lyletsufiev: not that I'm aware of20:25
tqtrani will sign up for zaqar and trove20:25
*** ducttape_ has joined #openstack-meeting-320:25
tsufievok, I´ll other QA liasons20:26
david-lyleand since all liaison roles default to me if no one occupies it, I can tell you that I don't recall anything that was required, but I do write tempest and devstack patches for horizon20:26
david-lyleas required20:26
*** baoli has quit IRC20:26
hurgleburgler david-lyle I need one of those devstack patches, btw20:27
tqtranwe have our own liason list too right?20:27
david-lyletyr_ you'll mainly just need to review the cross project specs20:27
david-lyletqtran: not that I'm aware of20:27
*** salv-orlando has quit IRC20:27
david-lylemaybe in an etherpad somewhere20:27
*** ihrachys has quit IRC20:27
robcresswellThere's an interproject liaison list too if anyone is working with specific projects.20:27
*** doug-fi__ is now known as doug-fish20:27
tqtrani could have sworn i saw a liason list for horizon somewhere20:27
*** evgenyf has quit IRC20:28
david-lylethose who volunteered please enter your name20:28
robcresswelltyr_: Yeah, just need to pop up in the weekly meetings and let us know if there are any cross-project plans we should be aware of.20:28
tqtranas in, horizon people checking out other projects to make sure we are in sync with their api20:28
tsufievdavid-lyle, ha, hope they have some courses for new QA liaisons on how to write devstack patches :)))20:28
david-lyletyr_:  you will find that since our architecture is so different from the other services that little applies to us directly20:29
david-lyletsufiev: they are mostly horizon code change driven20:29
david-lyleping me20:29
tyr_Ok. I'm assuming things like WebSSO where Horizon has a role to play in the overall experience.20:29
tyr_I'll add my name.20:30
david-lyletyr_: nothing that topical20:30
tyr_ha! Ok, maybe a background task, but seems like good breadth opportunity.20:31
*** mbound has joined #openstack-meeting-320:31
david-lyleI'll keep watching too, because I can't help myself20:31
robcresswellAre there any meetings relevant to the cross-project specs?20:31
david-lylerobcresswell: I'm not entirely sure any more20:32
tyr_wiki claims one on Feb 2nd20:32
david-lylewith the shift roll of the cross-project meeting, I'm uncertain as to it's intent anymore20:32
david-lyleat one point it was to discuss cross-project specs20:32
david-lyleadditionally there is #openstack-meeting-cp but it doesn't seem to be used20:33
*** ying_zuo has quit IRC20:34
david-lylehere's my cynical take, we're replacing all the parts of the car while in motion and I'm not certain what pieces are back, what have changed or why20:34
*** vtech has joined #openstack-meeting-320:34
david-lylethanks to the volunteers20:35
david-lyle#topic Open Discussion20:35
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"20:35
robcresswellJust a reminder for mid-cycle attendees: Fill in your name etc, and put topic ideas on the etherpad20:36
hurgleburglerWould it be possible to get some eyes and testing help with :
david-lyleby filling in your name and email, I can get your internet access set up at Intel ahead of time20:36
robcresswellbtw, why is everyones email AT and DOT instead of @ . ? Did I miss a memo?20:37
david-lylerobcresswell: not easily scraped20:37
tsufievrobcresswell, spammers don´t sleep?20:38
robcresswellAh, makes sense.20:38
david-lylejust like tsufiev20:38
david-lyledoesn't sleep20:38
tsufievI´m not a spammer :D20:39
robcresswellidk, interview doodle says otherwise tsufiev...20:39
tqtrantsufiev: you spam the horizon reviews, stop it!20:39
david-lyleno don't !20:39
*** madhu_ak has joined #openstack-meeting-320:40
tsufievcircling back to serious business :)...20:40
tsufievdo most of people here look through mitaka-priorities etherpad? Would it make sense if I wrote down the list of new integration tests ready for review (on a regular basis)?20:40
david-lyleor provide the link to the gerrit topic at least20:40
hurgleburglertsufiev are you adding them to the weekly bug report?20:40
robcresswelltsufiev: I have a potentially better (and selfish) idea. Use the weekly bug report, put a couple on each week.20:40
david-lylethat wasn't on the agenda!20:41
tqtranok, since we have some time, i also like to bring up the plugin doc again. its high on priority atm but not getting enough love can we agree to push it through and make amends, the information is useful enough20:41
robcresswellI've gotten slow on updating it, because its quite time consuming to do it on my own each week20:41
*** matrohon has joined #openstack-meeting-320:41
robcresswelldavid-lyle: Yeah, its 2-3 weeks out of date iirc.20:41
david-lyleah ok20:41
tsufievrobcresswell, hurgleburgler: okay, works either for me20:41
robcresswellI'd like it if people could sensibly drop a patch or two in, and I'll moderate it anyway. I'm going through the bug list in my spare time, and when thats properly in order we can drop the weekly report I hope.20:42
*** vishwanathj has joined #openstack-meeting-320:42
tqtranthere are a few follow on docs that i would really like to get started on, but that cant happen until this one goes through20:42
tsufievrobcresswell, I´ll just put there new integration tests and bump the date every week. If anyone would like add their bugs/bps, they´re welcome20:42
robcresswelltsufiev: That would be great, thanks!20:42
r1chardj0n3sI think it'd be good if hurgleburgler and matt-borland could punt the hard-to-reproduce bugs (ie. require edge cases or obscure openstack components to reproduce) to the group20:43
hurgleburglerr1chardj0n3s +10020:43
tsufievrobcresswell, to me this is only a question of moderating - to ensure that every bug/bp mentioned somehow fits our priorities for current release cycle20:43
matt-borlandyes, that would be good20:43
r1chardj0n3sshould use the weekly bug report for that20:43
robcresswellYeah, I don't expect them to be able to reproduce every bug, r1chardj0n3s, its just useful to have someone to keep the moving target-ness down20:43
matt-borlandah, ok20:43
r1chardj0n3srobcresswell: yeah, but we need to flag the hard-to-reproduce ones so they don't just sit and pile up :-)20:44
*** Sukhdev has quit IRC20:44
robcresswellMay be worth going over the bug tags so that people with specific expertise can check. Like scale requirements, or specific component setups.20:45
tqtranits no fun when you have to restack to test something though. i usually lose a day trying to reproduce and get no where.20:45
tsufievin an ideal world the scenario for bug reproduction would be a devstack config/script...20:45
*** vtech has quit IRC20:45
r1chardj0n3syep, and I've lost a day to trying to set up some part of openstack that I've never used before20:45
*** galstrom is now known as galstrom_zzz20:45
r1chardj0n3stsufiev: heh, and a pony!20:45
*** jwarendt has quit IRC20:45
tsufievr1chardj0n3s, if you find a pony who could write devstack scipts :)...20:46
david-lyleas I stated above "it's a gloriously rewarding pleasure cruise"20:46
* tsufiev looking for such pony for at least 1 year20:46
robcresswellIf we got stackalytics to track karma, our bugs would be gone in a day.20:46
hurgleburglermaybe if we get enough people on the list, we can make it a rotating duty20:46
* ducttape_ wonders about noro-virus on dave's cruise20:46
*** vtech has joined #openstack-meeting-320:46
david-lyleif the bug is vague and provides no clues for its reproduction, mark it incomplete20:46
hurgleburglerif we have 4 people, then we can take a week a month20:46
david-lyleducttape_: it's a mix of cruise ship/oregon trail20:47
robcresswellhurgleburgler: Can you and Matt alternate?20:47
robcresswellMight make it easier to maintain, keeps it less time consuming.20:47
hurgleburglerrobcresswell thought you were going to help too?20:48
robcresswellI'm trying to work through the backlog.20:48
david-lylerobcresswell: is keen on the past20:48
robcresswellHey I got about 50 categorised so far this week.20:48
robcresswellIts time consuming :)20:48
hurgleburglercan we work some backlogging into the current persons rotation?20:48
robcresswellhurgleburgler: No need to overload, I think. Just keep on top of the new reports. If you have spare time, then by all means have at it.20:49
robcresswelltqtran: I'll look through the docs again. The last comment I left (patch set.. 15?) was a complete blocker to betherly the other day.20:50
robcresswellWe need to double check its complete otherwise it doesnt save anyone time.20:50
david-lylethere is a point of contention around pbr in there20:51
david-lyleI will comment in the review20:51
david-lylebut mandating pbr is not great20:51
robcresswellAh, okay, maybe my misunderstanding then.20:51
david-lyleok for openstack/plugin-x, less great for company-y/plugin-x20:52
david-lyleprobably both should be documented20:52
robcresswellI'm happy with getting a minimum viable doc situation, but it has to definitely work the whole way through for a new plugin.20:53
robcresswellOtherwise I lose half a day debugging plugins that I'm unfamiliar with20:53
robcresswellNot ideal :)20:53
*** vtech has quit IRC20:53
robcresswellAs I said, I'll check it again, it looks mostly all done. I can carry it too if you're short on time tqtran.20:54
*** galstrom_zzz is now known as galstrom20:54
tqtranits basically the same steps that i took for zaqar ui, which is last week20:54
robcresswellor just fed up of my reviews :p20:54
tqtranand its proven to work, i might have missed a few things here or there, but the bulk of the info is valid and should work20:54
*** TravT has joined #openstack-meeting-320:54
tqtrani'll also verify again end of today20:55
david-lylelet's get something in20:55
david-lyleand improve20:55
david-lyleI don't think something wildly inaccurate is acceptable20:55
david-lylebut reasonably accurate20:55
david-lyleif we release without it :(20:56
robcresswellIt needs to be part of the release. I'm sure we can merge it within the next couple days.20:56
tqtrangreat, i can start documenting plugin localization and workflow extensions once it lands20:57
david-lyle3 minutes20:57
robcresswellSounds good20:57
*** dtardivel has quit IRC20:57
*** egallen has quit IRC20:58
david-lyleanyone else?20:58
david-lyleThanks everyone!20:59
*** openstack changes topic to "OpenStack Meetings ||"20:59
openstackMeeting ended Wed Jan 27 20:59:36 2016 UTC.  Information about MeetBot at . (v 0.1.4)20:59
openstackMinutes (text):
*** r1chardj0n3s has left #openstack-meeting-320:59
*** robcresswell has left #openstack-meeting-320:59
*** tqtran has left #openstack-meeting-321:01
*** TravT has left #openstack-meeting-321:01
*** mbound has quit IRC21:01
*** JOlsen has quit IRC21:01
*** julim has joined #openstack-meeting-321:03
*** rocky_g has joined #openstack-meeting-321:04
*** mbound has joined #openstack-meeting-321:04
*** tsufiev has left #openstack-meeting-321:04
*** annp has quit IRC21:09
*** galstrom is now known as galstrom_zzz21:13
*** salv-orlando has joined #openstack-meeting-321:16
*** jwarendt has joined #openstack-meeting-321:20
*** matt-borland has left #openstack-meeting-321:25
*** vhoward has quit IRC21:32
*** matrohon has quit IRC21:36
*** piet has quit IRC21:40
*** bpokorny_ has joined #openstack-meeting-321:41
*** bpokorny_ has quit IRC21:41
*** bpokorny_ has joined #openstack-meeting-321:42
*** bpokorny has quit IRC21:44
*** baoli has joined #openstack-meeting-321:44
*** kebray has joined #openstack-meeting-321:45
*** baoli_ has joined #openstack-meeting-321:46
*** dims has quit IRC21:46
*** fitoduarte has joined #openstack-meeting-321:48
*** e0ne has quit IRC21:49
*** baoli has quit IRC21:49
*** kebray has quit IRC21:50
*** spzala has quit IRC21:50
*** spzala has joined #openstack-meeting-321:51
*** piet has joined #openstack-meeting-321:51
*** bpokorny_ has quit IRC21:52
*** bpokorny has joined #openstack-meeting-321:52
*** lifeless has quit IRC21:53
*** FallenPegasus has joined #openstack-meeting-321:53
*** lifeless has joined #openstack-meeting-321:55
*** Sukhdev has joined #openstack-meeting-321:55
*** spzala has quit IRC21:55
*** mtanino_ has quit IRC21:55
*** mtanino has joined #openstack-meeting-321:56
*** cbouch has quit IRC21:56
*** spzala has joined #openstack-meeting-321:57
*** spzala has quit IRC22:03
*** mickeys has joined #openstack-meeting-322:04
*** salv-orl_ has joined #openstack-meeting-322:06
*** salv-orlando has quit IRC22:09
*** bpokorny has quit IRC22:11
*** lblanchard has quit IRC22:15
*** lblanchard has joined #openstack-meeting-322:15
*** lblanchard has quit IRC22:15
*** rtheis_ has quit IRC22:23
*** jmckind_ has joined #openstack-meeting-322:26
*** piet has quit IRC22:28
*** jmckind has quit IRC22:30
*** bpokorny has joined #openstack-meeting-322:30
*** peristeri has quit IRC22:31
*** rossella_s has quit IRC22:31
*** jmckind has joined #openstack-meeting-322:31
*** rossella_s has joined #openstack-meeting-322:31
*** baoli_ has quit IRC22:33
*** jmckind_ has quit IRC22:33
*** ivar-laz_ has joined #openstack-meeting-322:33
*** banix has quit IRC22:34
*** bpokorny_ has joined #openstack-meeting-322:34
*** bpokorny_ has quit IRC22:35
*** ivar-lazzaro has quit IRC22:35
*** bpokorny has quit IRC22:35
*** bpokorny has joined #openstack-meeting-322:36
*** AlanClark has quit IRC22:41
*** jmckind has quit IRC22:41
*** neelashah1 has quit IRC22:42
*** dimtruck is now known as zz_dimtruck22:43
*** sdake has quit IRC22:45
*** dims has joined #openstack-meeting-322:51
*** dims has quit IRC22:54
*** Sukhdev has quit IRC22:57
*** hurgleburgler has quit IRC22:58
*** e0ne has joined #openstack-meeting-323:02
*** doug-fish has quit IRC23:03
*** e0ne_ has joined #openstack-meeting-323:04
*** e0ne has quit IRC23:06
*** davidlenwell has quit IRC23:06
*** jpomeroy has quit IRC23:07
*** moshele has quit IRC23:08
*** davidlenwell has joined #openstack-meeting-323:08
*** tej has joined #openstack-meeting-323:08
*** doug-fish has joined #openstack-meeting-323:10
*** tej has quit IRC23:10
*** tej has joined #openstack-meeting-323:11
*** rocky_g has quit IRC23:11
*** tej has quit IRC23:13
*** tej has joined #openstack-meeting-323:14
*** sigmavirus24 is now known as sigmavirus24_awa23:16
*** armax has joined #openstack-meeting-323:17
*** doug-fish has quit IRC23:18
*** tej has quit IRC23:18
*** doug-fish has joined #openstack-meeting-323:21
*** e0ne_ has quit IRC23:24
*** doug-fish has quit IRC23:24
*** doug-fish has joined #openstack-meeting-323:25
*** doug-fish has quit IRC23:25
*** doug-fish has joined #openstack-meeting-323:25
*** doug-fish has quit IRC23:27
*** doug-fish has joined #openstack-meeting-323:27
*** dims_ has joined #openstack-meeting-323:30
*** bpokorny_ has joined #openstack-meeting-323:31
*** bpokorny_ has quit IRC23:32
*** bpokorny_ has joined #openstack-meeting-323:32
*** doug-fish has quit IRC23:32
*** bpokorny has quit IRC23:35
*** bpokorny_ has quit IRC23:38
*** zz_dimtruck is now known as dimtruck23:38
*** bpokorny has joined #openstack-meeting-323:40
*** bpokorny has quit IRC23:42
*** ducttape_ has quit IRC23:43
*** dimtruck is now known as zz_dimtruck23:45
*** Sukhdev has joined #openstack-meeting-323:46
*** rbak has quit IRC23:46
*** bpokorny has joined #openstack-meeting-323:49
*** Sukhdev has quit IRC23:49
*** alexpilotti has quit IRC23:50
*** Sukhdev has joined #openstack-meeting-323:51
*** shwetaap has quit IRC23:51
*** Sukhdev has quit IRC23:52
*** Sukhdev has joined #openstack-meeting-323:52
*** Sukhdev has quit IRC23:54
*** Sukhdev has joined #openstack-meeting-323:54
*** Sukhdev has quit IRC23:56
*** Sukhdev has joined #openstack-meeting-323:56
*** Sukhdev has quit IRC23:57
*** Sukhdev has joined #openstack-meeting-323:58
*** Sukhdev has quit IRC23:59

Generated by 2.14.0 by Marius Gedminas - find it at!