Wednesday, 2016-03-23

*** ddieterly has joined #openstack-meeting-300:01
*** salv-orl_ has joined #openstack-meeting-300:02
*** dims_ has joined #openstack-meeting-300:03
*** dims has quit IRC00:04
*** salv-orlando has quit IRC00:05
*** Sukhdev has joined #openstack-meeting-300:06
*** salv-orl_ has quit IRC00:07
*** baojg has joined #openstack-meeting-300:07
*** baojg has quit IRC00:08
*** baoli has quit IRC00:09
*** baoli has joined #openstack-meeting-300:10
*** iyamahat has quit IRC00:15
*** iyamahat has joined #openstack-meeting-300:20
*** SumitNaiksatam has quit IRC00:26
*** baoli has quit IRC00:32
*** Swami has quit IRC00:32
*** toddjohn has quit IRC00:33
*** piet has joined #openstack-meeting-300:41
*** krotscheck has joined #openstack-meeting-300:42
*** brad_behle_ has left #openstack-meeting-300:45
*** reedip_away is now known as reedip00:49
*** sdake has quit IRC00:50
*** kzaitsev_mb has joined #openstack-meeting-300:50
*** sdake has joined #openstack-meeting-300:51
*** claudiub|2 has joined #openstack-meeting-301:02
*** stanzgy has joined #openstack-meeting-301:04
*** claudiub|3 has joined #openstack-meeting-301:04
*** claudiub has quit IRC01:05
*** stanzgy has quit IRC01:07
*** claudiub|2 has quit IRC01:08
*** SumitNaiksatam has joined #openstack-meeting-301:09
*** Sukhdev has quit IRC01:12
*** zhurong has joined #openstack-meeting-301:15
*** piet has quit IRC01:15
*** fawadkhaliq has quit IRC01:18
*** fawadkhaliq has joined #openstack-meeting-301:18
*** fawadkhaliq has quit IRC01:19
*** fawadkhaliq has joined #openstack-meeting-301:20
*** alexpilotti has quit IRC01:23
*** mtanino has joined #openstack-meeting-301:23
*** baoli has joined #openstack-meeting-301:24
*** stanzgy has joined #openstack-meeting-301:29
*** baoli has quit IRC01:30
*** stanzgy has quit IRC01:32
*** baoli has joined #openstack-meeting-301:34
*** salv-orlando has joined #openstack-meeting-301:35
*** ddieterly is now known as ddieterly[away]01:36
*** zz_dimtruck is now known as dimtruck01:38
*** dims_ has quit IRC01:40
*** iyamahat has quit IRC01:42
*** salv-orlando has quit IRC01:42
*** yamahata has quit IRC01:43
*** baojg has joined #openstack-meeting-301:46
*** s3wong has quit IRC01:59
*** fawadkhaliq has quit IRC02:01
*** fawadkhaliq has joined #openstack-meeting-302:02
*** ddieterly[away] is now known as ddieterly02:02
*** fawadkhaliq has quit IRC02:10
*** fawadkhaliq has joined #openstack-meeting-302:10
*** bpokorny_ has joined #openstack-meeting-302:11
*** bpokorny_ has quit IRC02:11
*** bryan_att has quit IRC02:12
*** ddieterly is now known as ddieterly[away]02:13
*** bpokorny has quit IRC02:15
*** claudiub has joined #openstack-meeting-302:17
*** kzaitsev_mb has quit IRC02:17
*** ivar-laz_ has quit IRC02:20
*** claudiub|3 has quit IRC02:20
*** neelashah has joined #openstack-meeting-302:22
*** banix has joined #openstack-meeting-302:23
*** woodster_ has quit IRC02:27
*** vtech has quit IRC02:27
*** vtech has joined #openstack-meeting-302:27
*** dimtruck is now known as zz_dimtruck02:31
*** hoangcx has joined #openstack-meeting-302:39
*** MarkAtwood has joined #openstack-meeting-302:40
*** salv-orlando has joined #openstack-meeting-302:41
*** neelashah has quit IRC02:45
*** tfukushima has joined #openstack-meeting-302:47
*** baojg has quit IRC02:48
*** baojg has joined #openstack-meeting-302:50
*** salv-orlando has quit IRC02:51
*** fawadkhaliq has quit IRC02:51
*** askb has joined #openstack-meeting-302:52
*** fawadkhaliq has joined #openstack-meeting-302:52
*** iyamahat has joined #openstack-meeting-302:53
*** markvoelker has quit IRC02:59
*** fawadkhaliq has quit IRC03:01
*** fawadkhaliq has joined #openstack-meeting-303:01
*** fawadkhaliq has quit IRC03:01
*** fawadkhaliq has joined #openstack-meeting-303:02
*** piet has joined #openstack-meeting-303:10
*** ddieterly[away] has quit IRC03:14
*** kzaitsev_mb has joined #openstack-meeting-303:15
*** claudiub has quit IRC03:17
*** piet has quit IRC03:23
*** yamahata has joined #openstack-meeting-303:26
*** geno has joined #openstack-meeting-303:28
genoHello03:28
*** geno has left #openstack-meeting-303:32
*** baoli has quit IRC03:46
*** Poornima has joined #openstack-meeting-303:55
*** hoangcx has quit IRC03:56
*** tfukushima has quit IRC03:57
*** hoangcx has joined #openstack-meeting-303:57
*** markvoelker has joined #openstack-meeting-303:59
*** stanzgy has joined #openstack-meeting-304:03
*** markvoelker has quit IRC04:04
*** banix has quit IRC04:06
*** salv-orlando has joined #openstack-meeting-304:10
*** baoli has joined #openstack-meeting-304:13
*** salv-orlando has quit IRC04:14
*** baoli has quit IRC04:14
*** baoli has joined #openstack-meeting-304:15
*** fawadkhaliq has quit IRC04:17
*** fawadkhaliq has joined #openstack-meeting-304:17
*** baoli has quit IRC04:24
*** yamamoto_ has joined #openstack-meeting-304:30
*** fawadkhaliq has quit IRC04:35
*** fawadkhaliq has joined #openstack-meeting-304:36
*** fawadkhaliq has quit IRC04:40
*** fawadkhaliq has joined #openstack-meeting-304:41
*** fawadkhaliq has quit IRC04:41
*** fawadkhaliq has joined #openstack-meeting-304:42
*** fawadkhaliq has quit IRC04:42
*** fawadkhaliq has joined #openstack-meeting-304:43
*** fawadkhaliq has quit IRC04:46
*** fawadkhaliq has joined #openstack-meeting-304:46
*** fawadkhaliq has quit IRC04:47
*** fawadkhaliq has joined #openstack-meeting-304:48
*** fawadkhaliq has quit IRC04:48
*** fawadkhaliq has joined #openstack-meeting-304:49
*** MarkAtwood has quit IRC05:04
*** hoangcx has quit IRC05:30
*** hoangcx has joined #openstack-meeting-305:32
*** kzaitsev_mb has quit IRC05:35
*** shinya_ has joined #openstack-meeting-305:36
*** MarkAtwood has joined #openstack-meeting-305:36
*** lpetrut has joined #openstack-meeting-305:37
*** iyamahat has quit IRC05:41
*** salv-orlando has joined #openstack-meeting-305:42
*** kaz has joined #openstack-meeting-305:42
*** shinya_ has quit IRC05:45
*** salv-orlando has quit IRC05:49
*** stendulker has joined #openstack-meeting-305:57
*** Sukhdev has joined #openstack-meeting-305:57
*** markvoelker has joined #openstack-meeting-306:00
*** fawadkhaliq has quit IRC06:03
*** fawadkhaliq has joined #openstack-meeting-306:04
*** markvoelker has quit IRC06:04
*** SumitNaiksatam has quit IRC06:10
*** lpetrut has quit IRC06:15
*** nkrinner has joined #openstack-meeting-306:17
*** fawadkhaliq has quit IRC06:20
*** fawadkhaliq has joined #openstack-meeting-306:21
*** ihrachys has joined #openstack-meeting-306:22
*** soichi has joined #openstack-meeting-306:23
*** kaz has quit IRC06:24
*** kaz has joined #openstack-meeting-306:25
*** fawadkhaliq has quit IRC06:25
*** fawadkhaliq has joined #openstack-meeting-306:25
*** fawadkhaliq has quit IRC06:26
*** fawadkhaliq has joined #openstack-meeting-306:26
*** fawadkhaliq has quit IRC06:27
*** anilvenkata has joined #openstack-meeting-306:28
*** fawadkhaliq has joined #openstack-meeting-306:28
reediphmm06:28
*** fawadkhaliq has quit IRC06:28
reedipanyone here ?06:28
soichihi06:28
reediphi soichi06:29
kazhi06:29
*** fawadkhaliq has joined #openstack-meeting-306:29
reedipwaiting for anil_rao and vnyyad for the meeting...06:29
reediphi kaz06:29
reedipsaw your commit for the Dashboard06:29
yamamoto_hi06:30
reediplets wait for 2 more minutes, then we will start..06:30
reediphi yamamoto_06:30
*** ihrachys has quit IRC06:31
reedipyamamoto_ : can you chair?06:32
*** kzaitsev_mb has joined #openstack-meeting-306:32
yamamoto_i can06:32
reedipI guess we can start now...06:33
yamamoto_#startmeeting taas06:33
openstackMeeting started Wed Mar 23 06:33:13 2016 UTC and is due to finish in 60 minutes.  The chair is yamamoto_. Information about MeetBot at http://wiki.debian.org/MeetBot.06:33
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_#topic Agenda06:33
*** openstack changes topic to "Agenda (Meeting topic: taas)"06:33
yamamoto_#link https://wiki.openstack.org/wiki/Meetings/taas06:33
yamamoto_#topic Summit planning schedule finalization06:33
*** openstack changes topic to "Summit planning schedule finalization (Meeting topic: taas)"06:33
yamamoto_who added this?  is this about taas session?06:34
reedipyamamoto_ yes06:34
reedipI thought that if all the members are present here, we can finalize it quickly06:34
reedipthan over the email06:35
*** lpetrut has joined #openstack-meeting-306:35
yamamoto_unfortunately it doesn't seem to be case though.  let's use email.06:35
*** sdake_ has joined #openstack-meeting-306:35
yamamoto_#topic Async Calls06:36
reedipYes, okay, lets skip it06:36
*** openstack changes topic to "Async Calls (Meeting topic: taas)"06:36
yamamoto_#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html06:36
reedipyamamoto_ Anil sent an email06:36
*** sdake has quit IRC06:36
reedipfor the async calls06:36
reedipand I thought we can discuss it here06:36
reedipbut, I am not sure now06:36
reedipcan we discuss it on the ML itself?06:36
yamamoto_sure.06:37
reedipokay, moving on then, I guess06:37
yamamoto_i guess we all agree async stuff is good idea.06:37
reedipyamamoto_ : as per the last meeting, yes definetly06:37
reedipdefinitely*06:37
*** kzaitsev_mb has quit IRC06:37
yamamoto_#topic TaaS Dashboard discussion06:37
*** openstack changes topic to "TaaS Dashboard discussion (Meeting topic: taas)"06:37
reedipbut I think we can also get some input from neutrinoes06:37
yamamoto_#undo06:38
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x9fb9d50>06:38
reedipokay, next topic ?06:38
yamamoto_#topic TaaS Dashboard discussion06:38
*** openstack changes topic to "TaaS Dashboard discussion (Meeting topic: taas)"06:38
reedipso kaz submitted a patch06:39
kazyes06:39
reedip#link https://review.openstack.org/#/c/295735/06:39
reedipkaz, I see that its 403161 Lines long06:39
reedipyou copied the entire horizon onto taas?06:40
kazyes06:40
reedipany reason ?06:40
kazbecause we are based on kilo.06:40
yamamoto_any idea what happened on "Conflicts With" ?06:40
reedipis there any reason for using Kilo and not using Mitaka?06:41
reedipyamamoto_ : Not a clue... that what triggered my thoughts on this patch06:41
soichiThe Network Topology view was dramatically changed from Liberty.06:41
*** lpetrut has quit IRC06:41
reedipsoichi : okay06:42
reedipsoichi : so if we are to support TaaS in Newton06:42
reedipsoichi: would we request Horizon to be based on Kilo to see the TaaS dashboard?06:42
soichino06:42
reedipsoichi: but if our changes are made on Kilo, wont we have to rework on it again, if we get the inclusion into governance in Newton?06:43
soichiI guess one of the idea is to show the network topoloy view in kilo on the TaaS panel06:43
reedipsoichi: I think its a great idea to showcase it in the Summit06:43
reedipsoichi: yes, +1 , but I think some users may ask why we are showing the older topology, isnt it?06:44
*** sdake_ has quit IRC06:44
*** iyamahat has joined #openstack-meeting-306:44
*** sdake has joined #openstack-meeting-306:44
reedipsoichi: lets work with this implementation , but can we start also to look for integration into Horizon  in its M-release version ?06:45
soichiyes, i think some users may have a question.06:45
yamamoto_soichi: kaz: for some reasons you want to stick with kilo, or it just means not-rebased-yet?06:45
soichireedip: agree06:45
reedipI mean we can , for now, use the dashboard as it is, and demonstrate it, and get some ideas06:46
kaznot rebased yes.06:46
reedipand then , moving forward, we can use the latest release, rebase most the changes which can be ported, and work out the other nitty gritties in N-Release06:46
soichireedip: okay06:47
*** MarkAtwood has quit IRC06:47
reedipsoichi : great , thats all from my side for the dashboard. Any other points to discuss for the dashboard?06:47
yamamoto_how long do you think it would take to "rebase" it to master?06:48
yamamoto_(i have no idea how different horizon kilo vs master)06:48
kazI am not sure , but it takes a few months.06:49
reedipyamamoto_ : huge , if I am correct06:49
reedipkaz, rebase takes months ?06:49
reedipI think a lot of manual work is required, right06:50
reedip?06:50
yamamoto_will it likely be re-implementation rather than a rebase?06:50
kazwe need to see a new source code.06:51
*** vgridnev has joined #openstack-meeting-306:53
yamamoto_ok, i understand it's a major work.06:54
yamamoto_i guess it's better (at least easier to read) to submit a patch to horizon/kilo rather than having the entire horizon tree.06:55
kazi see06:56
yamamoto_let's move on06:57
yamamoto_#topic Spec Discussion completion06:57
*** openstack changes topic to "Spec Discussion completion (Meeting topic: taas)"06:57
yamamoto_i updated the review yesterday06:57
reedipyamamoto_ I didnt see the new spec06:58
*** salv-orlando has joined #openstack-meeting-306:58
*** e0ne has joined #openstack-meeting-306:58
yamamoto_reflected many of comments and moved some more things to "future work" section to minimize the scope for the first step06:58
reedipyamamoto_ I think you put up some queries for me as well, I will check it out on the weekend/tomorrow and update it with the same06:58
yamamoto_reedip: thank you06:59
reedipyamamoto_ I would have preferred having the discussion with Anil and Vinay as well, for the points left in the spec which I mailed on the ML. Can we discuss this point as well next week ( I know the list is getting longer for the next week's discussion)07:00
*** markvoelker has joined #openstack-meeting-307:01
yamamoto_#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html07:01
yamamoto_let's discuss on ML and/or review.07:02
yamamoto_#topic Open Discussion07:03
*** openstack changes topic to "Open Discussion (Meeting topic: taas)"07:03
reedipyamamoto_ : nothing much from my end07:03
*** vasubabu has joined #openstack-meeting-307:03
*** pgadiya has joined #openstack-meeting-307:03
soichii have no additional topic.07:03
kazme too07:04
yamamoto_i wanted to ask anil and vnyyad to tweak LP permissions to allow me triage bugs07:04
reediplets skip this and end the meeting then :)07:04
reedipyamamoto_ I think you can email them07:04
reedip??07:04
yamamoto_i said it here as i think anil said he will read the log :-)07:05
yamamoto_thank you for attending everyone07:05
yamamoto_bye07:05
yamamoto_#endmeeting07:05
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"07:05
openstackMeeting ended Wed Mar 23 07:05:47 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:05
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-03-23-06.33.html07:05
kazbye07:05
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-03-23-06.33.txt07:05
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-03-23-06.33.log.html07:05
vasubabubye07:05
soichibye07:05
*** vasubabu has quit IRC07:06
*** watanabe_isao has joined #openstack-meeting-307:06
*** markvoelker has quit IRC07:07
*** soichi has left #openstack-meeting-307:11
*** vishwanathj is now known as vishwanathj_away07:12
*** hdaniel has joined #openstack-meeting-307:13
*** kaz has quit IRC07:14
*** salv-orlando has quit IRC07:15
*** lazy_prince has quit IRC07:23
*** sdake has quit IRC07:23
*** Sukhdev has quit IRC07:25
*** davidlenwell has quit IRC07:26
*** lazy_prince has joined #openstack-meeting-307:26
*** e0ne has quit IRC07:28
*** kzaitsev_mb has joined #openstack-meeting-307:33
*** davidlenwell has joined #openstack-meeting-307:34
*** kebray has quit IRC07:38
*** kzaitsev_mb has quit IRC07:38
*** kebray has joined #openstack-meeting-307:41
*** alexpilotti has joined #openstack-meeting-307:42
*** vtech has quit IRC07:42
*** egallen has joined #openstack-meeting-307:44
*** vgridnev has quit IRC07:49
*** alexpilotti has quit IRC07:53
*** alexpilotti has joined #openstack-meeting-307:54
*** pt_15 has quit IRC07:55
*** egallen has quit IRC07:58
*** alexpilotti has quit IRC07:58
*** vgridnev has joined #openstack-meeting-307:58
*** dtardivel has joined #openstack-meeting-308:00
*** vtech has joined #openstack-meeting-308:02
*** kebray has quit IRC08:04
*** tmazur has joined #openstack-meeting-308:07
*** kebray has joined #openstack-meeting-308:10
*** claudiub has joined #openstack-meeting-308:12
*** nkrinner has quit IRC08:12
*** matrohon has joined #openstack-meeting-308:13
*** vgridnev has quit IRC08:15
*** zhurong has quit IRC08:16
*** nkrinner has joined #openstack-meeting-308:17
*** MarkAtwood has joined #openstack-meeting-308:26
*** jschwarz has joined #openstack-meeting-308:27
*** egallen has joined #openstack-meeting-308:27
*** hdaniel has quit IRC08:29
*** ihrachys has joined #openstack-meeting-308:30
*** MarkAtwood has quit IRC08:31
*** mbound has joined #openstack-meeting-308:34
*** zhurong has joined #openstack-meeting-308:34
*** kzaitsev_mb has joined #openstack-meeting-308:34
*** safchain has joined #openstack-meeting-308:38
*** kzaitsev_mb has quit IRC08:39
*** watanabe_isao has quit IRC08:39
*** tmazur has quit IRC08:43
*** kzaitsev_mb has joined #openstack-meeting-308:43
*** tmazur has joined #openstack-meeting-308:44
*** hdaniel has joined #openstack-meeting-308:44
*** jed56 has joined #openstack-meeting-308:44
*** jlanoux has joined #openstack-meeting-308:45
*** russellb has quit IRC08:58
*** Igor_Iris has joined #openstack-meeting-308:59
*** russellb has joined #openstack-meeting-309:00
*** eyalb has joined #openstack-meeting-309:00
*** evgenyf has joined #openstack-meeting-309:00
*** piet has joined #openstack-meeting-309:01
*** ifat_afek has joined #openstack-meeting-309:01
ifat_afek#startmeeting vitrage09:01
openstackMeeting started Wed Mar 23 09:01:56 2016 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.09:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:01
*** openstack changes topic to " (Meeting topic: vitrage)"09:01
ifat_afekhi everyone09:02
openstackThe meeting name has been set to 'vitrage'09:02
*** pradipm has joined #openstack-meeting-309:02
eyalbhi all09:03
*** e0ne has joined #openstack-meeting-309:03
*** amir_gur has joined #openstack-meeting-309:03
*** rossella_s has quit IRC09:03
*** markvoelker has joined #openstack-meeting-309:03
*** idan_hefetz has joined #openstack-meeting-309:03
*** emalin has joined #openstack-meeting-309:03
*** rossella_s has joined #openstack-meeting-309:03
*** alexey_weyl has joined #openstack-meeting-309:04
*** elisha_r has joined #openstack-meeting-309:04
idan_hefetzHi09:04
alexey_weylHello09:04
emalinhi hi09:04
elisha_rhey09:04
*** doug-fish has quit IRC09:04
amir_gurHi09:05
ifat_afek#topic Current status09:05
*** openstack changes topic to "Current status (Meeting topic: vitrage)"09:05
ifat_afekOhad and I attended the opnfv hackfest last week, and presented a demo of vitrage that included deduced alarms, deduced states, RCA and Aodh alarms09:06
*** vtech_ has joined #openstack-meeting-309:06
*** vtech has quit IRC09:06
*** salv-orlando has joined #openstack-meeting-309:06
ifat_afek. I also showed the static physical plugin configuration, and how to configure our templates09:06
*** dedery has joined #openstack-meeting-309:06
*** claudiub|2 has joined #openstack-meeting-309:06
ifat_afekWe got very positive responses, and we will be mentioned as an optional reference implementation for Doctor Inspector component09:07
ifat_afekThanks for everyone who helped preparing the demo!09:07
ifat_afekRegarding Aodh, the synchronizer still has a few bugs, which I’m about to handle this week09:07
alexey_weylThumbs up!!! :)09:08
ifat_afekIn addition, it currently supports only threshold alarms and event alarms. I should install Gnocchi and make sure we support also gnocchi alarms.09:08
*** eyalb has quit IRC09:08
*** markvoelker has quit IRC09:08
*** eyalb_ has joined #openstack-meeting-309:08
ifat_afekAnother issue is the round-trip of deduced alarms -> notify aodh -> aodh synchronizer gets the deduced alarms from aodh09:08
eyalb_hi again09:08
ifat_afekidan_hefetz, can you explain about it?09:08
idan_hefetzsure09:08
*** vgridnev has joined #openstack-meeting-309:09
*** zhurong has quit IRC09:09
*** hdaniel has quit IRC09:09
*** claudiub has quit IRC09:09
idan_hefetzwe need to make sure a deduced alarm, that was created by the evaluator, and later created in aodh (by the notifier). is handled correctly09:09
*** dannoffel has joined #openstack-meeting-309:10
*** mkovacik__ has joined #openstack-meeting-309:10
idan_hefetzso that we'll need to add the appropiate resource_id to the query09:10
ifat_afekidan_hefetz: ok. and we should identify that this is the same alarm09:11
dannoffelhi09:11
idan_hefetzThat's right, from my side (the notifier) i hope to finish this cycle soon09:11
ifat_afekidan_hefetz: cool, thanks09:11
ifat_afekwho else wants to update?09:12
*** dedery has quit IRC09:12
eyalb_I want to update09:12
eyalb_I started to work on a neutron plugin09:12
eyalb_also did some refactoring in the code09:12
eyalb_mostly cosmetic09:13
eyalb_thats it09:13
*** Ohad has joined #openstack-meeting-309:13
ifat_afekeyalb_: do you know what information you are going to import from neutron?09:14
*** lhartal has joined #openstack-meeting-309:14
eyalb_still working on it :-)09:14
eyalb_it will be very basic in the begining09:14
ifat_afekeyalb_: ok, thanks09:14
elisha_rI'll go next09:15
elisha_rI've started working on installing and configuring nagios as part of our vitrage devstack installation.09:15
elisha_rThe goal being to allow devstack users to see how Vitrage can integrate with it09:15
elisha_rI'll be installing this using the OMD package #link http://omdistro.org/09:16
*** piet has quit IRC09:16
elisha_rso far, I was able to do this manually. The main issues are determining the version to install, and that there is an overlap with port 5000 which is what keystone listens on09:17
elisha_rhope to get this done sometime next week.09:17
elisha_rthe main thing I'm wondering about is, whether or not doing this, automatically, as part of vitrage makes sense. Nagios can be used in many other projects, so I'm not sure if the vitrage context is the correct one09:19
elisha_rfor example, if the vitrage install installs is, should we also assume the uninstall also removes nagios?09:19
ifat_afekelisha_r: that's a good question. I'm also not sure that everyone who uses vitrage will want to use nagios09:19
ifat_afekelisha_r: I don't think we can uninstall nagios...09:20
ifat_afekmaybe it should be optional09:20
eyalb_I think tha we should have a flag in the devstack installation09:20
eyalb_that09:20
ifat_afek#action elisha_r decide about our approach to nagios installation as part of devstack installation09:21
eyalb_you can see how other projects install therir packages09:21
elisha_rthats it for me09:21
eyalb_their09:21
ifat_afekeyalb_: I agree that a flag is a good idea09:21
ifat_afeklet's move on, who wants to update?09:21
*** nelsnels_ has quit IRC09:22
*** kzaitsev_mb has quit IRC09:23
alexey_weylI will update09:24
*** jlanoux has quit IRC09:24
alexey_weylWe have Vitrage's internal plugins configuration working, and now we are planning to work on the external pluggins configuration09:25
alexey_weylin addition we want to be able to handle some more complicated issues with the plugins, such as:09:25
alexey_weyldefining number of transformers for one synchronizers09:25
alexey_weyland more09:26
ifat_afekalexey_weyl: cool, thanks09:27
*** yamahata has quit IRC09:27
*** egallen has quit IRC09:27
*** jlanoux has joined #openstack-meeting-309:27
*** iyamahat has quit IRC09:28
ifat_afekanyone else wants to update?09:28
ifat_afekmoving on09:31
*** egallen has joined #openstack-meeting-309:31
ifat_afek#topic Review action items09:31
*** openstack changes topic to "Review action items (Meeting topic: vitrage)"09:31
*** mkoushnir has joined #openstack-meeting-309:31
ifat_afek1. support template validation09:31
mkoushnirHi09:31
lhartalThere is no progress on this issue09:32
*** mkoushnir has quit IRC09:32
lhartalI will work on it this week09:32
ifat_afeklhartal: ok, thanks09:33
*** mkoushnir has joined #openstack-meeting-309:33
ifat_afek#action lhartal support template validation09:33
ifat_afekmkoushnir: I see you joined, do you want to update about your status?09:33
mkoushniryep. I finish work on nova alarms and validations of alarms correctness09:35
ifat_afekmkoushnir: you mean in the templest?09:35
mkoushnirnext step - nagios alarms and rca09:35
mkoushniryes. Tempest api test09:36
ifat_afekmkoushnir: cool!09:36
mkoushnir:)09:36
ifat_afekthanks, let's move on09:36
ifat_afek#topic Next Steps09:36
*** openstack changes topic to "Next Steps (Meeting topic: vitrage)"09:36
ifat_afekWe should record a new demo with all the existing functionality, and put it in our wiki page09:36
ifat_afekI just want to fix, with lhartal's help, some minor ui issues first09:37
ifat_afek#action record a new demo09:37
ifat_afek#topic Open Discussion09:37
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"09:37
ifat_afekanyone wants to talk about anything?09:37
ifat_afekso I guess we are done for today09:39
lhartalbye09:39
alexey_weylbye bye09:39
ifat_afekbye everyone09:40
dannoffelbye09:40
*** dannoffel has left #openstack-meeting-309:40
ifat_afek#endmeeting09:40
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:40
openstackMeeting ended Wed Mar 23 09:40:27 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-03-23-09.01.html09:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-03-23-09.01.txt09:40
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-03-23-09.01.log.html09:40
mkoushnirbye09:40
*** mkoushnir has quit IRC09:41
*** alexey_weyl has quit IRC09:41
*** lhartal has quit IRC09:52
*** idan_hefetz has quit IRC09:54
*** Ohad has quit IRC09:54
*** sc68cal has joined #openstack-meeting-309:56
*** sdague has joined #openstack-meeting-309:58
*** lpetrut has joined #openstack-meeting-310:00
*** dims has joined #openstack-meeting-310:00
*** sambetts|afk is now known as sambetts10:00
*** baojg has quit IRC10:06
*** amir_gur has quit IRC10:07
*** dedery has joined #openstack-meeting-310:08
*** egallen has quit IRC10:09
*** pradipm has left #openstack-meeting-310:09
*** zhurong has joined #openstack-meeting-310:11
*** dedery has quit IRC10:13
*** claudiub has joined #openstack-meeting-310:15
*** eyalb_ has quit IRC10:15
*** claudiub|2 has quit IRC10:18
*** vgridnev has quit IRC10:19
*** askb has quit IRC10:19
*** vgridnev has joined #openstack-meeting-310:20
*** dedery has joined #openstack-meeting-310:23
*** hoangcx has quit IRC10:23
*** hdaniel has joined #openstack-meeting-310:31
*** kzaitsev_mb has joined #openstack-meeting-310:31
*** e0ne has quit IRC10:35
*** elisha_r has quit IRC10:41
*** claudiub|2 has joined #openstack-meeting-310:41
*** baojg has joined #openstack-meeting-310:42
*** claudiub has quit IRC10:44
*** e0ne has joined #openstack-meeting-310:45
*** baojg has quit IRC10:47
*** alexpilotti has joined #openstack-meeting-310:55
*** zhurong has quit IRC10:59
*** alexpilotti has quit IRC10:59
*** zhurong has joined #openstack-meeting-311:02
*** MarkAtwood has joined #openstack-meeting-311:02
*** markvoelker has joined #openstack-meeting-311:04
*** dims_ has joined #openstack-meeting-311:05
*** dims has quit IRC11:06
*** MarkAtwood has quit IRC11:07
*** markvoelker has quit IRC11:08
*** ifat_afek has left #openstack-meeting-311:13
*** emalin has quit IRC11:16
*** doug-fish has joined #openstack-meeting-311:22
*** stendulker_ has joined #openstack-meeting-311:32
*** stendulker has quit IRC11:33
*** stendulker_ has quit IRC11:38
*** rtheis has joined #openstack-meeting-311:43
*** atuvenie has joined #openstack-meeting-311:45
*** itxaka has joined #openstack-meeting-311:50
*** askb has joined #openstack-meeting-311:51
*** askb has quit IRC11:51
*** primeministerp has joined #openstack-meeting-311:53
*** robcresswell has joined #openstack-meeting-311:54
*** askb has joined #openstack-meeting-311:56
*** neiljerram has joined #openstack-meeting-311:56
*** sankarshan_away is now known as sankarshan11:56
*** wangbo has joined #openstack-meeting-311:58
*** sagar_nikam has joined #openstack-meeting-311:58
*** david-lyle_ has joined #openstack-meeting-311:58
*** Poornima has quit IRC12:00
david-lyle_#startmeeting Horizon12:00
openstackMeeting started Wed Mar 23 12:00:51 2016 UTC and is due to finish in 60 minutes.  The chair is david-lyle_. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: Horizon)"12:00
openstackThe meeting name has been set to 'horizon'12:00
*** david-lyle has quit IRC12:00
*** tsufiev has joined #openstack-meeting-312:01
itxakao/12:01
tsufievo/12:01
tmazuro/12:01
*** wangbo has quit IRC12:01
*** salv-orl_ has joined #openstack-meeting-312:02
*** wangbo has joined #openstack-meeting-312:02
robcresswell\o12:02
david-lyle_So we had a time mixup on meetings for the past month or so12:02
david-lyle_This is the correct start time12:03
* robcresswell hides in shame12:03
david-lyle_This is my last meeting as PTL and will be handing the keys to robcresswell for future meetings12:04
*** lpetrut has quit IRC12:04
*** salv-orlando has quit IRC12:04
david-lyle_We tagged and branched RC-1 Friday12:05
david-lyle_so master is open for Newton12:05
david-lyle_#chair robcresswell12:05
openstackCurrent chairs: david-lyle_ robcresswell12:05
david-lyle_it's snowing here and the lights just flickered12:05
david-lyle_if my power goes robcresswell gets and early start :)12:06
robcresswellwhat a way to go12:06
david-lyle_does anyone have any bugs they think warrant consideration for RC-2?12:06
david-lyle_we don't have a milestone yet in launchpad12:07
tsufievI'd like to propose new Swift UI buttons fixup12:07
david-lyle_so we'll have to tag such bugs12:07
robcresswellYeah, agreed tsufiev12:07
david-lyle_tsufiev: link?12:07
* tsufiev looking for a link12:07
robcresswellI asked cindy to backport her fix12:07
*** primeministerp has quit IRC12:07
robcresswell#link https://review.openstack.org/#/c/295428/12:07
robcresswellIts minor, but just addresses a couple of styling oddities which would be a shame to ship in our shiny new UI.12:08
robcresswelllow risk too.12:08
itxakaIgor this one, which is tagged newton but I think it should be mitaka12:08
tsufievdavid-lyle_, https://review.openstack.org/#/c/294223/12:08
itxakahttps://bugs.launchpad.net/horizon/+bug/156014512:08
openstackLaunchpad bug 1560145 in OpenStack Dashboard (Horizon) ""Copy Data" checkbox on Image create has the wrong label" [Medium,In progress] - Assigned to Daniel Castellanos (luis-daniel-castellanos)12:08
david-lyle_robcresswell: 295428 is cosmetic ?12:09
tsufievrobcresswell, ah, that's more correct link, thanks12:09
robcresswelldavid-lyle_: Yeah. Is that a blocker for backports? A few things are weird, like massive cancel buttons.12:09
robcresswellThey work, though.12:10
*** annegentle has joined #openstack-meeting-312:10
david-lyle_robcresswell: not a blocker, but the bar for RC-2 is pretty high12:10
david-lyle_that one is probably benign enough to be ok12:10
*** pgadiya has quit IRC12:10
robcresswellMy understanding was no string changes or high risk refactors.12:11
david-lyle_the one itxaka linked seems like its not ready yet12:13
david-lyle_robcresswell: probably ok12:13
robcresswellitxaka: Its targeted for Newton because it needs to hit master first and backport.12:13
robcresswellI could add another line for hitting mitaka stabel though12:14
robcresswellbut its tagged, so its fine.12:14
*** jaypipes has joined #openstack-meeting-312:15
david-lyle_yeah at this point tags are all we have12:15
david-lyle_any other RC-2 bugs?12:15
robcresswellNothing else has jumped out.12:15
itxakarobcresswell, ack!12:16
david-lyle_moving on12:18
david-lyle_#topic Next bug day suggestion: 5th April12:18
*** openstack changes topic to "Next bug day suggestion: 5th April (Meeting topic: Horizon)"12:18
david-lyle_robcresswell: o/12:18
robcresswellI'd like to continue doing bug days roughly once per month. We still have a decent backlog of bugs that need to be triaged.12:19
*** lpetrut has joined #openstack-meeting-312:19
robcresswellNext date proposal is April 5th (Tuesday)12:19
david-lyle_sounds good to me12:19
robcresswellCool. I'll send out an email later today. Any questions?12:20
david-lyle_seems there is overwhelming support ;-)12:20
*** markvoelker has joined #openstack-meeting-312:20
tsufievrobcresswell, yeah, I have a related question/suggestion12:20
robcresswelltsufiev: fire away12:20
*** yamamoto_ has quit IRC12:20
tsufievthere are a lot of bugfixes that are overlooked in favor of hotter Angular features/fixes... it would be nice if we established a regular communication regarding these fixes12:21
*** k-ishii has joined #openstack-meeting-312:21
robcresswellI agree. Personally I see the first step as organising and categorising our list of bugs and bps so we can see the important ones, rather than letting them sit as Undecided, when they might be very serious issues.12:22
tsufievfor example, many Django patches are in unclear situation - I feel that many cores are simply don't think these patches are worth reviewing (too much efforts)12:22
tsufievwe need to communicate this to patch authors12:22
tsufievto set their expectations12:22
*** annegentle has quit IRC12:23
robcresswellAny ideas? I'd imagine having your bug set to Low or Wishlist might be a hint :)12:23
david-lyle_tsufiev: can you give an example of a high or so bug that has failed to get reviews?12:24
david-lyle_we are drowning in medium and low12:25
robcresswellI should add its also *very* difficult to categorise all the bugs alone, so priority is overly subjective. My values will not be the same as others for example.12:26
robcresswellI feel if we get a list sorted, we can start working down from Critical to Low, and use the bug days for fixing, not triage work.12:26
robcresswellBut thats where we are right now :)12:26
david-lyle_sounds like a good plan to me12:27
tsufievdavid-lyle_, do not have an example of High bug right now out of my head12:27
tsufievI think that most of them are Medium/Low12:28
tsufievstill... that doesn't IMO mean that they should be ignored forever :)12:28
david-lyle_tsufiev: my only point is that the input to the review funnel is greatly over the review capacity at the other end of the funnel12:28
david-lyle_things will be lost12:28
tsufievdavid-lyle_, completely agree12:28
robcresswelltsufiev: If you want to, you can use something like this http://russellbryant.net/openstack-stats/horizon-openreviews.html12:29
david-lyle_but I totally agree that new feature dev often gets priority over fixing real issues12:29
david-lyle_making new issues just happens to be more fun, I guess12:29
robcresswellThat shows the reviews that have been sitting for a long time without negative review.12:29
david-lyle_we can try to more tightly control new feature dev, but people will still work on their pets and in the end we have no real control over what anyone works on other than ourselves12:31
david-lyle_unless you want to get more active in core cycling for looking at the wrong things12:31
*** sankarshan is now known as sankarshan_away12:32
*** krtaylor has quit IRC12:32
david-lyle_moving on12:33
david-lyle_#topic Broadcasting summit working sessions?12:33
*** openstack changes topic to "Broadcasting summit working sessions? (Meeting topic: Horizon)"12:33
david-lyle_robcresswell: o/12:33
tsufievbroadcasting = recording?12:33
robcresswellI've mentioned this before, but wanted to revisit, since some orgs seem to be scaling back on summit attendance12:33
david-lyle_#link https://etherpad.openstack.org/p/horizon-newton-summit12:34
robcresswellI'd quite like to try doing something like a hangouts on air with summit sessions, so that people can listen to discussions12:34
robcresswelland potentially feed back via IRC or similar.12:34
david-lyle_there is chat in the etherpads12:34
robcresswellSome people have mentioned feeling uncomfortable with this though12:35
robcresswellThat too12:35
tsufiev+1, would be great to attend summit at least remotely )12:35
robcresswellIssues also around the technical side (not being able to hear clearly)12:35
david-lyle_I've voiced my concerns before12:35
david-lyle_roundtable meetings are terrible for remote participants12:36
*** piet has joined #openstack-meeting-312:36
robcresswellThe other alternative is to make sure we're documenting discussion better12:36
robcresswellBut I do have some concerns around members of the community missing out12:37
*** annegentle has joined #openstack-meeting-312:37
robcresswellMaybe it would be better if people spent more on dev travel and less on booth swag... *grumbles*12:37
david-lyle_you either need actual room mics, or everyone will have to have hangouts open12:37
robcresswellDo telepresence style mics not work for this kind of discussion?12:38
david-lyle_sure, but the rooms aren't equipped with those12:38
david-lyle_the work rooms have 0 mics12:38
david-lyle_directional or non-directional12:38
robcresswellRight, but not having a mic is a a pretty solvable issue.12:39
*** nelsnelson has joined #openstack-meeting-312:39
david-lyle_a mic is insufficient12:39
*** abalutoiu has joined #openstack-meeting-312:39
david-lyle_anyway, if someone wants to try, more power to them12:40
robcresswellOkay, so we'll need something more elaborate, and thus impractical. Hmm. I'll investigate more.12:40
david-lyle_just realize on the receiving end frustration is likely12:40
robcresswellIf hardware was solved, would anyone have other issues?12:40
david-lyle_which is my main concern12:40
david-lyle_you go to all this effort and it's still not consumable12:41
* david-lyle_ lets it go12:41
david-lyle_#topic open discussion12:42
*** openstack changes topic to "open discussion (Meeting topic: Horizon)"12:42
robcresswellI'm taking the silence as no other issues :)12:42
itxaka+1 from me, seems nice for those that can't attend like me12:42
robcresswellitxaka: \o/12:42
robcresswellI wanted to discuss this meeting time slow (1200UTC)12:43
robcresswelltime slot*12:43
robcresswellIt seems like it doesnt really benefit anyone. Its too early for those in NA, and too last for those in East Asia/ Australia12:43
robcresswellWe could likely shift it to 8/9 UTC, could we not?12:43
tsufiev... Europe is happy though :)12:44
tsufiev9 UTC is also fine12:44
robcresswellha, but we could do 8/9 with no issues really. Everyone but me is UTC +1 or +212:44
david-lyle_gets rid of pesky NA12:44
tsufievdavid-lyle_, so you could sleep well during that time ;)12:45
robcresswellYou're the only person who regularly attends from NA I think. Sometimes doug-fish too.12:45
itxakasounds good from belgium time, better times for lunch are always welcome :D12:45
*** lpetrut has quit IRC12:46
david-lyle_my only concern is you have 7 active cores in NA12:46
tsufievitxaka, I thought you're in Spain :o?12:46
*** lpetrut has joined #openstack-meeting-312:46
david-lyle_you have 4 outside12:46
itxakatsufiev, born in spain, living in belgium, heart in the world :)12:46
*** krtaylor has joined #openstack-meeting-312:46
robcresswellThis is true, but I'm concerned that we're missing out on contributors. There are regularly questions on IRC being posted into the void during east asia work hours.12:47
tsufievitxaka, got it, I learn something new every day here :)12:47
david-lyle_depends on your intent for the meeting, but sure12:47
david-lyle_up to you12:47
robcresswelldavid-lyle_: And as I said, nobody comes to the 1200 UTC meeting anyway from NA, so we'd only miss out on yourself. The 2000UTC meeting would still stand.12:47
david-lyle_robcresswell: true12:47
david-lyle_I never said I did anything right ;-)12:48
*** baoli has joined #openstack-meeting-312:48
robcresswellhaha12:48
robcresswellI'll send out an email12:48
robcresswell*TODO list growing*12:48
* david-lyle_ 's list is shrinking12:49
*** lblanchard has joined #openstack-meeting-312:49
*** mbound has quit IRC12:49
robcresswellLast item I had: I'd like to bring back the Drivers meeting. Early Newton is the best time for blueprint discussion.12:49
wangboIt's better update it in  http://eavesdrop.openstack.org/12:49
robcresswellwangbo: Yes, but the email is for others to chime in. I'm not dictating a meeting time until everyone has had a fair chance to discuss it.12:50
robcresswellAfter that I'll update infra, naturally :)12:50
*** baojg has joined #openstack-meeting-312:50
wangbosure12:50
*** MarkAtwood has joined #openstack-meeting-312:51
david-lyle_any other topics?12:51
*** ddieterly has joined #openstack-meeting-312:52
*** ddieterly is now known as ddieterly[away]12:53
robcresswellI'll run Drivers from next week btw, unless you want to run it tonight david-lyle_ :)12:53
*** mtanino has quit IRC12:53
david-lyle_robcresswell: all yours12:53
robcresswellSure12:54
david-lyle_I just want to say congratulations to robcresswell on being the Horizon PTL for Newton. The community and I personally thank you.12:54
david-lyle_let all of us know what we can do to help12:54
robcresswellHeh. We should be thanking you for being an excellent PTL for the past 2.5 years.12:54
david-lyle_alright let's call it12:55
david-lyle_#endmeeting12:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"12:55
openstackMeeting ended Wed Mar 23 12:55:44 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-03-23-12.00.html12:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-03-23-12.00.txt12:55
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-03-23-12.00.log.html12:55
tsufievcongratulations to both david-lyle_ and robcresswell :)12:55
robcresswellThanks everyone12:55
itxakao/12:55
*** MarkAtwood has quit IRC12:55
*** robcresswell has left #openstack-meeting-312:56
itxakacongrats both!12:56
*** tsufiev has left #openstack-meeting-312:56
*** alexpilotti has joined #openstack-meeting-312:56
*** itxaka has left #openstack-meeting-312:56
*** wangbo has quit IRC12:59
*** k-ishii has left #openstack-meeting-312:59
*** alexpilotti has quit IRC13:00
*** c64cosmin has joined #openstack-meeting-313:00
*** vhoward has joined #openstack-meeting-313:01
claudiub|2hello13:01
atuveniehi all13:01
claudiub|2#startmeeting hyper-v13:01
openstackMeeting started Wed Mar 23 13:01:18 2016 UTC and is due to finish in 60 minutes.  The chair is claudiub|2. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: hyper-v)"13:01
openstackThe meeting name has been set to 'hyper_v'13:01
sagar_nikamHi13:01
c64cosminhello all13:01
claudiub|2ok, I'll try to keep it short.13:01
claudiub|2#topic mitaka releases13:02
*** openstack changes topic to "mitaka releases (Meeting topic: hyper-v)"13:02
claudiub|2so, mitaka is going to be released in early april, meaning that any and all dependencies will have to be released until then too.13:02
claudiub|2that includes networking_hyperv, compute_hyperv, and os-win13:02
*** lpetrut has quit IRC13:03
*** rossella_s has quit IRC13:03
claudiub|2I'm going to cut the stable/mitaka branches on friday / saturday13:03
*** ddieterly[away] has quit IRC13:03
claudiub|2#action claudiub to cut the stable/mitaka branches13:03
*** rossella_s has joined #openstack-meeting-313:03
*** itoader has joined #openstack-meeting-313:04
claudiub|2which means, that if there are any more issues or bugs, this week is going to be a good chance to fix them. :)13:04
claudiub|2if there's anything, let me know13:04
claudiub|2ok, moving on.13:05
claudiub|2#topic hyper-v neutron vif plug event listener on spawn13:05
*** openstack changes topic to "hyper-v neutron vif plug event listener on spawn (Meeting topic: hyper-v)"13:05
claudiub|2so, this was suggested some time ago by the HP folks. The main idea was that the Hyper-V Driver was not waiting for the vNICs to be bound, which was leading to missed DHCP requests.13:06
*** david-lyle_ is now known as david-lyle13:06
claudiub|2we've addressed that issue in compute_hyperv, and it will have to be included in nova as well13:06
claudiub|2#link https://review.openstack.org/#/c/292615/13:06
*** Igor_Iris has quit IRC13:07
claudiub|2#action propose the hyper-v neutron vif plug event listerner commit on nova13:07
claudiub|2from experiments, it seemed to be behaving properly, with little to no decrease in performance, but a rally would be nice to confirm this.13:08
claudiub|2ok, moving on.13:08
claudiub|2#topic Rally performance tests13:09
*** openstack changes topic to "Rally performance tests (Meeting topic: hyper-v)"13:09
claudiub|2abalutoiu: hello. do you have any good news for us? :)13:09
abalutoiuhello13:09
*** banix has joined #openstack-meeting-313:09
abalutoiuso last week we had some results for the spawn / destroy scenario, here are the results for the spawn / destroy scenario including ssh guest access http://46.101.88.127:8888/PyMI_KVM_ssh_Mitaka.html13:10
*** rbak has joined #openstack-meeting-313:10
abalutoiuLiberty ones, for comparison: http://46.101.88.127:8888/PyMI_KVM_ssh_Liberty.html13:11
*** neelashah has joined #openstack-meeting-313:11
*** yamamoto has joined #openstack-meeting-313:12
claudiub|2#link Mitaka Hyper-V vs KVM http://46.101.88.127:8888/PyMI_KVM_ssh_Mitaka.html13:12
sagar_nikamavg time is more in HyperV13:12
claudiub|2#link Liberty Hyper-V vs KVM http://46.101.88.127:8888/PyMI_KVM_ssh_Liberty.html13:13
sagar_nikamkvm - nova.boot_server19.50234.97166.85974.39878.74142.074100.0%10013:13
sagar_nikamhyperv - nova.boot_server32.596120.705147.194155.103177.713109.56598.0%10013:13
abalutoiusagar_nikam: those are the results for Liberty, the old ones, have a look over the Mitaka results13:14
sagar_nikamhas anything changed ? last week we saw almost same result for hyperv and kvm13:14
sagar_nikamok13:14
*** jpomeroy has joined #openstack-meeting-313:14
*** sonu has joined #openstack-meeting-313:14
abalutoiuthe results from last week didn't include ssh guest access13:14
sagar_nikamok, this looks good13:15
sagar_nikamkvm and hyperv almost same13:15
sagar_nikamthe avg time includes ssh access ?13:15
claudiub|2yep.13:15
sagar_nikamok13:15
*** rbak_ has joined #openstack-meeting-313:15
sagar_nikamand how many NICs ?13:15
sagar_nikamper VM13:15
abalutoiuonly one NIC13:16
sagar_nikam?13:16
sagar_nikamand are we trying attaching volumes13:16
*** rbak has quit IRC13:16
*** baoli_ has joined #openstack-meeting-313:16
abalutoiuit's a simple scenario, spin up a VM, add floating ip to it, wait until it becomes active via ssh, then destroy the VM13:17
sagar_nikamok13:17
sagar_nikamthese results are good13:17
sagar_nikamnice work13:17
sonucan we continue our tests without destroying the VM?13:18
abalutoiuwe also have some results for Hadoop workloads13:18
claudiub|2sonu: any reason why?13:18
abalutoiu#link Mitaka Hyper-V vs KVM Hadoop cluster tests http://46.101.88.127:8888/Cluster_Results_Mitaka.html13:18
sonuThe only reason being, the larger the number of ACLs in MI, the more load on the neutron agent.13:19
sonuand more time it takes. And we can measure the times it varies with the number of ACLs.13:19
*** baoli has quit IRC13:19
abalutoiuFlavor for VMs: 2 vCPUs, 6GB RAM, 25GB disk, number of parallel clusters for multi cluster test: 3, input data set for tera jobs: 5.000.000, clusters consists of 4 nodes (1 master + 3 slaves)13:20
*** mbound has joined #openstack-meeting-313:20
claudiub|2sonu: That also depends on the rally scenario. For example, if the scenario says 100 VMs, with 100 VMs per round, for 1 round, it will spawn all 100 VMs. Then destroy them.13:20
sonusure. then we are good.13:21
claudiub|2anyways, looking at abalutoiu's hadoop results, it seems hyper-v is more favorable in this scenario13:21
sonuand we use default security group rules for our tests.13:21
claudiub|2sonu: default + ssh. :)13:22
sonuThank you. We will consume this coming next week and run some scale tests.13:22
claudiub|2sure, sounds good. :)13:22
claudiub|2anything else on this topic?13:23
claudiub|2ok, moving on.13:23
sonuAny chance we can get these improvements backported to L13:23
sonuwe are on L release13:23
sagar_nikamit would be nice if these are backported to L13:23
sonuwe are trying to backport on our local branch - native threading and PYMI and ERPC13:24
*** egallen has joined #openstack-meeting-313:24
claudiub|2sonu: any improvement related to spawning / creating / destroy the vm etc. has been included in compute_hyperv on stable/liberty13:24
sonuthank you13:24
claudiub|2for the networking-hyperv side, I'm afraid not. networking-hyperv is an official project under neutron's governance. The improvements we've done in Mitaka were marked as blueprints, meaning that they can't be backported.13:24
claudiub|2ok, moving on.13:25
claudiub|2#topic OVS agent on Hyper-V13:26
*** openstack changes topic to "OVS agent on Hyper-V (Meeting topic: hyper-v)"13:26
claudiub|2atuvenie: hello. I suppose the agent works fine for Mitaka, right?13:26
atuvenieyeah, we just merged the last patch that was causing some issues, all is fine now13:26
claudiub|2cool.13:27
claudiub|2seems that we're almost done with the work for Mitaka. :)13:27
sonuatuvenie : Do we know the feature parity between OVS for Linux and OVS Windows. Are all features supported as is in OVS.13:27
*** banix has quit IRC13:27
atuveniesonu: I'm not quite sure what you mean. Are you talking about the OVS Agent or OVS itself?13:28
sonuWho participates in OVS forums from within us, who can bring us this info?13:28
sonuOVS itself.13:28
atuveniesonu: I do not work on OVS directly so I'm not up to speed on the topic13:29
claudiub|2AFAIK, no, there shouldn't be any disparity. all network types work the same on Linux and Windows.13:30
sonuThanks. May be we start attending OVS IRC chats to get more info.13:30
claudiub|2but as far as OVS agent is concerned, it works the same on Windows and Linux.13:31
*** jmckind has joined #openstack-meeting-313:31
sonuAnd is there a CI for Microsoft HyperV when a change is done in neutron-openvswitch-agent?13:31
sonubecause it is shared b/w Linux and Windows now :)13:31
claudiub|2not yet, but we're working on it. :)13:32
sonuGreat. Thank you.13:32
*** absubram has joined #openstack-meeting-313:32
claudiub|2ok, moving on13:32
sagar_nikamclaudiub|2: i have a topic13:32
claudiub|2#topic OpenStack Summit13:33
sagar_nikamon certs13:33
*** openstack changes topic to "OpenStack Summit (Meeting topic: hyper-v)"13:33
*** absubram_ has joined #openstack-meeting-313:33
claudiub|2sagar_nikam: sure, I'll get to that soon. :)13:33
claudiub|2anyways, we've requested a worksession at the next OpenStack summit.13:34
claudiub|2in which we can discuss any further improvement and development of os-win and other Hyper-V / Windows related workloads.13:35
sonuWill OVN be part of design discussion?13:35
claudiub|2including new features and so on.13:35
claudiub|2sonu: sure, we are looking into it as well.13:36
claudiub|2so, question: who is going to attend the summit?13:36
sonuI will have one representative from networking team.13:37
*** absubram has quit IRC13:37
*** absubram_ is now known as absubram13:37
*** vgridnev has quit IRC13:37
claudiub|2ok, cool.13:38
*** stanzgy has quit IRC13:38
claudiub|2ok, moving on13:38
claudiub|2# topic certificates13:38
claudiub|2#topic certificates13:38
*** openstack changes topic to "certificates (Meeting topic: hyper-v)"13:38
sagar_nikambased on the meeting discussion last week13:39
sagar_nikamwe tried using certs on the hyperv hosts13:39
sagar_nikamwe copied the .crt file from controller13:39
sagar_nikamto the hyperv host13:39
sagar_nikamand had the correct https and cafile entry in nova.conf13:40
sagar_nikamwe are using python 2.7.10 64 bit on the hyperv host13:40
sagar_nikamwe hit a issue13:40
sagar_nikamwhich is exactly same as described here13:41
sagar_nikamhttp://stackoverflow.com/questions/33140382/troubleshooting-ssl-certificate-verify-failed-error13:41
*** rhochmuth has joined #openstack-meeting-313:41
sagar_nikamthe issue was urllib2.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)13:41
sagar_nikamthis looks like a issue in python 2.7.1013:41
*** egallen has quit IRC13:42
claudiub|2interesting13:42
sagar_nikamsince it uses openssl 1.0.2a13:42
sagar_nikamand we need 1.0.2b or greater13:42
sagar_nikamwhich is available in python 2.7.1113:42
sagar_nikamnow my question13:42
sagar_nikamhow was your tests done using certs13:42
sagar_nikamdid you not hit this issue13:43
sagar_nikam?13:43
sagar_nikamwhat version of python do you use ?13:43
sagar_nikamon hyperv host13:43
*** mtanino has joined #openstack-meeting-313:44
*** piet has quit IRC13:45
claudiub|2the hyper-v compute installers come with python 2.7.913:45
claudiub|2so, we're using that. so, the person that answered your previous email is not here at the moment, but he'll be back later and he'll be able to send you an answer.13:45
*** egallen has joined #openstack-meeting-313:45
sagar_nikamok13:45
sagar_nikamthanks13:46
sagar_nikamnot sure if python 2.7.9 can solve the issue13:46
sagar_nikambut i will wait for the mail13:46
claudiub|2sagar_nikam: although, i am a bit curious, can you check what python version you use on your Openstack controller?13:46
sagar_nikampython 2.7.913:46
sagar_nikamwe had some issues with python 2.7.9 on windows13:47
sagar_nikamand hence used 27.1013:47
sagar_nikamnova code was not getting compiled on 2.7.913:47
claudiub|2what kind of issues did you have with python 2.7.9 on windows?13:47
sagar_nikamsome dependent packages13:47
sagar_nikamwhen we run setup.py13:47
sagar_nikamof nova13:47
sagar_nikampackages were not getting complied13:47
*** klkumar has joined #openstack-meeting-313:48
*** vgridnev has joined #openstack-meeting-313:48
claudiub|2sure, nova and a lot of other projects have linux specific dependencies, which cannot be installed on windows.13:48
claudiub|2which is why we recommend the installer, as we package those dependencies as well13:48
sagar_nikamthe compiled packages --- are they available for others to use13:48
sagar_nikamwhatever you got it compiled ?13:49
claudiub|2plus, there are other dependencies like numpy that has to be compiled. windows doesn't typically come with a compiler and you wouldn't want one on nano or bare hyper-v hosts.13:49
*** njohnsto_ has joined #openstack-meeting-313:49
*** sonu has quit IRC13:49
sagar_nikamwe use mingw for compiling13:50
sagar_nikamand that solved lot of complilation issues13:50
sagar_nikamin 2.7.1013:50
claudiub|2yeah, ofc, but there is no need to compile anything when using the installer, everything is already packaged in the Python folder it installs.13:51
sagar_nikamone question -- all the packages which you have complied13:51
sagar_nikamis that available for others to use13:51
sagar_nikamwe are not using that installer13:52
sagar_nikamhence the question13:52
claudiub|2i'm not against it. :)13:52
sagar_nikamif the compiled files are available, we can use it while we run setup.py13:53
*** slogan has joined #openstack-meeting-313:53
sagar_nikamand that would solve lot of the compilation issues we faced in 2.7.913:53
claudiub|2but we still recomend using the installer. it can be installed in unnattended mode, which is perfect for automations.13:54
slogan#join #openstack-monasca13:54
claudiub|2#topic open discussion13:54
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:54
*** annegentle has quit IRC13:55
claudiub|2so, the Newton branch is open, which means we will start merging patches on master again13:55
claudiub|2one pending patch that we want is the os-win in os-brick patch13:55
claudiub|2that is based on henma's patch13:56
*** piet has joined #openstack-meeting-313:57
sagar_nikamupstream branch open ?13:57
claudiub|2sagar_nikam: hist patch is still WIP. Any news from him?13:57
sagar_nikamfor newton13:57
claudiub|2sagar_nikam: yeah, for most projects.13:57
sagar_nikami can check13:57
sagar_nikamcan you let me know which patch set13:57
sagar_nikamcan we start submitting FC and cluster BPs and patches in N13:57
claudiub|2#link https://review.openstack.org/#/c/275943/513:58
sagar_nikamwe can get review time13:58
sagar_nikamnow13:58
claudiub|2the blueprints have been reapproved for N.13:58
sagar_nikamcan we re-submit code as well13:58
sagar_nikamboth for cluster driver and FC13:58
sagar_nikamit would be nice to get it merged upstream13:58
sagar_nikamin N13:58
*** neelashah1 has joined #openstack-meeting-313:59
claudiub|2anyways, we'll also have to recreate the famous 3 hyper-v patches queue that needs to be reviewed and ready to merge on the etherpad.13:59
claudiub|2ofc. having os-win in os-brick will greatly help on this subject.13:59
claudiub|2#action claudiub to create the nova patches queue on etherpad.13:59
claudiub|2Seems that our time is over14:00
*** davidsha has joined #openstack-meeting-314:00
claudiub|2thanks all for attending!14:00
claudiub|2#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Wed Mar 23 14:00:23 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-03-23-13.01.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-03-23-13.01.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-03-23-13.01.log.html14:00
*** neelashah has quit IRC14:01
*** sigmavirus24_awa is now known as sigmavirus2414:01
ajohi :)14:01
*** absubram has quit IRC14:02
davidshahey14:02
njohnsto_Hey14:02
sloganhi14:02
ajolet me ping rediip14:03
jschwarzhello :)14:03
ajo#startmeeting neutron_qos14:03
openstackMeeting started Wed Mar 23 14:03:46 2016 UTC and is due to finish in 60 minutes.  The chair is ajo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:03
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:03
openstackThe meeting name has been set to 'neutron_qos'14:03
jschwarznjohnsto_, did you see the mail tread I opened for you? :)14:03
*** vtech_ has quit IRC14:03
*** vtech has joined #openstack-meeting-314:04
njohnsto_Yes, and I am very much appreciative!14:04
*** dims has joined #openstack-meeting-314:04
*** dims_ has quit IRC14:04
njohnsto_jschwarz: I'll get the hang of full stack tests yet; I'm just glad I wasn't doing something foolish.14:05
ajohi :-)ok, let's get to that at some point :D14:05
*** sagar_nikam has quit IRC14:05
ajo#topic Features: DSCP14:05
*** openstack changes topic to "Features: DSCP (Meeting topic: neutron_qos)"14:05
jschwarz:)14:05
ajoDSCP got merged for Newton, sadly not for Mitaka, but life goes on,14:05
ajoI'm happy to see it finally merged.14:06
davidsha+114:06
njohnsto_Hallelujah and amen14:06
ajolol14:06
*** neelashah has joined #openstack-meeting-314:06
njohnsto_The docs changes are waiting for the Newton cut offs14:06
ajoTechnologies like SR-IOV support that, and OVS & Linux bridge can be configured to support this type of service. Where in OvS it requires to14:07
ajoWe will have to wait for the dependencies also to finish the fullstack part14:07
*** neelashah1 has quit IRC14:07
*** salv-orl_ has quit IRC14:07
*** alexpilotti has joined #openstack-meeting-314:08
ajo(aka python-neutronclient)14:08
njohnsto_Yes14:08
ajonjohnsto_, you're tracking the docs, right?14:08
*** vijendar has joined #openstack-meeting-314:08
*** openstack has joined #openstack-meeting-314:24
*** ChanServ sets mode: +o openstack14:24
ajoreedip__ not exactly, I mean, how would it work exactly14:24
ajoit's more like an spec what I'm asking probably14:24
reedip__ajo , ok14:24
*** evgenyf has quit IRC14:24
ajoso I wonder if you could just jump into the spec, may be in etherpad format until drivers give you approval14:24
ajobecause from vikram conversation14:25
*** ddieterly is now known as ddieterly[away]14:25
reedip__ajo : Yes, I think I can start the spec on etherpad, and then discuss the same with the drivers in a seprate thread14:25
ajoI understood that you could use the ECN signaling from node to node to throttle the other side bandwidth in OVS14:25
ajowhen ECN is supposed to be E2E14:25
*** annegentle has joined #openstack-meeting-314:27
ajook, we can wait for that, and move on now.14:27
*** sdake has joined #openstack-meeting-314:27
ajo#topic Bugs14:27
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"14:27
ajo#link https://bugs.launchpad.net/neutron/+bug/1507761 qos wrong units in max-burst-kbps option (per-second is wrong)14:27
ajoah, I see slawek is not here14:27
openstackLaunchpad bug 1507761 in neutron "qos wrong units in max-burst-kbps option (per-second is wrong)" [Low,In progress] - Assigned to Slawek Kaplonski (slaweq)14:27
ajoI remember he started work on it14:27
ajobut I see no review linked14:28
ajook14:28
ajo#topic Free discussion14:28
*** openstack changes topic to "Free discussion (Meeting topic: neutron_qos)"14:28
ajoanything that I missed or anybody wants to discuss? :)14:29
davidsha#link https://review.openstack.org/#/c/291633/14:29
ajothanks davidsha , I will manually add it to the bug report.14:29
davidshaajo: np :)14:30
*** toddjoh__ has joined #openstack-meeting-314:30
* njohnsto_ is copacetic. 14:30
davidshajust on neutron classifier, is there a way we could make it use OVS flows? the only way I can think of is to pass in the bridge object, otherwise would it be worth just using it with tc?14:31
*** piet has quit IRC14:31
ajodavidsha, that's a good question, also related to min bw guarantees14:32
ajoso the most "compatible" way with our current openflow rules would be using tc to filter / queue stuff14:32
ajobut it's a bit of a mix up14:32
ajoplease look at this review14:32
ajohttps://review.openstack.org/#/c/284259/13/doc/source/devref/openvswitch_firewall.rst14:32
ajothis is being implemented for jlibosva in the ovs firewall14:32
*** jschwarz_ has joined #openstack-meeting-314:33
ajoit marks the port number in reg5 and local-vlan on reg614:33
ajowe could use that to avoid the "NORMAL" rules for data, and use directed flows14:33
*** abalutoiu has quit IRC14:33
*** toddjohn has quit IRC14:34
*** shinya_kwbt_ has joined #openstack-meeting-314:34
davidshakk, I'm going to be working on the extension-flow management as well so I'll keep an eye on this.14:34
ajoif we had directed flows for the traffic (instead of using NORMAL to send the packet finally to it's destination) we could just use enqueue(port, queue)14:34
ajoI wonder if we could use the set_queue action14:35
ajoat some point14:35
ajoI didn't look at that when I experimented14:35
ajo              set_queue:queue14:36
ajo                     Sets the queue that should be used to queue when packets are output.   The  number  of  supported  queues14:36
ajo                     depends on the switch; some OpenFlow implementations do not support queuing at all.14:36
ajoI wonder if that works with "NORMAL"14:36
ajodavidsha, ^  any idea?14:36
*** sc68cal has quit IRC14:36
davidshaI'm unfamiliar with set_queue, I'll look into it. Also enqueue doesn't actually send the traffic so it can still be resubmitted!14:36
ajodavidsha, it does not?14:36
*** anilvenkata has joined #openstack-meeting-314:37
davidshaajo: no, I'll double check but last time I used it it didn't send packets unless I included the Normal action.14:37
ajodavidsha, it worked in my experiments14:37
ajowithout the normal action, of course :)14:37
*** piet has joined #openstack-meeting-314:38
davidshaI'll double check later, it's probably my mistake then.14:38
ajodavidsha, : https://github.com/mangelajo/ovs-experiments/blob/master/qos/qos_complex_traffic_shapping.sh#L29814:38
*** slogan has quit IRC14:38
ajoif we could use dl_dst=$MAC_A actions=set_queue:N14:38
ajoand then NORMAL obeys that... that'd be awesome14:39
*** MarkAtwood has joined #openstack-meeting-314:39
ajo#action ajo try set_queue to see if it's a way to simplify how to implement traffic_classification and min bandwidth14:39
davidshawas the traffic being received though?14:40
*** andymaier has joined #openstack-meeting-314:40
ajodavidsha, yes14:40
ajodavidsha, and the bandwidth measurements matched what it was expected14:40
*** alexpilotti has joined #openstack-meeting-314:41
ajodavidsha, you can run the script in your machine if you want :)14:41
ajodavidsha, it cleans up at the end.14:41
davidshakk, I think you showed it to me before as well, I'll try it again.14:42
*** zhurong has quit IRC14:42
*** iyamahat has joined #openstack-meeting-314:42
ajook, anything else, or shall we end the meeting for today? :)14:43
*** Swami has joined #openstack-meeting-314:43
*** MarkAtwood has quit IRC14:44
*** kebray has quit IRC14:45
davidshaI'm good, thanks!14:45
ajosoo14:46
ajothanks everybody for joining14:46
ajo#endmeeting14:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:46
openstackMeeting ended Wed Mar 23 14:46:48 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-03-23-14.03.html14:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-03-23-14.03.txt14:46
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-03-23-14.03.log.html14:46
*** njohnsto_ has quit IRC14:46
*** david-lyle_ is now known as david-lyle14:47
davidshaajo: just for object versioning actually, are you supposed to be able to increment an object version?14:47
davidshaso from version 1.0 -> 1.1?14:48
*** sdake_ has joined #openstack-meeting-314:48
ajodavidsha, I think you actually can't, but I'm not sure14:48
ajoI guess you need something like that if you change a field name14:48
ajofor example14:48
ajodavidsha, I'd look at the versionedobjects tests14:48
ajoto see if there's something like that or ask dansmith in #openstack-oslo14:48
*** sdake has quit IRC14:49
davidshaajo: kk, I was testing and it wasn't working, wasn't sure If I'd done it wrong, but it makes sense it wouldn't work.14:49
*** ddieterly[away] is now known as ddieterly14:49
*** hichihara has joined #openstack-meeting-314:51
*** sdake has joined #openstack-meeting-314:52
*** sdake_ has quit IRC14:53
*** atuvenie has quit IRC14:53
reedip__ajo : have we decided on the topics for Austin ?14:54
ajoreedip__, not really, you mean discussion?14:54
reedip__ajo : I hope I am not interrupting .. (??)14:54
reedip__ajo : yes14:54
ajoreedip__ no, but one could be traffic classification14:54
reedip__ajo : I was looking at the etherpad armax set up for Austin14:54
ajoanother about integration with nova / guarantees14:54
ajoreedip__ could you relink me to it?14:55
*** toddjoh__ has quit IRC14:55
*** tomasztrebski has joined #openstack-meeting-314:55
reedip__ajo : and saw QoS , so thought to ask14:55
davidshahttps://etherpad.openstack.org/p/newton-neutron-summit-ideas14:55
reedip__thanks davidsha :)14:55
davidshanp :)14:55
*** sc68cal has joined #openstack-meeting-314:55
*** toddjohn has joined #openstack-meeting-314:55
*** hosanai has joined #openstack-meeting-314:56
*** hosanai has left #openstack-meeting-314:56
*** hosanai has joined #openstack-meeting-314:56
*** slogan has joined #openstack-meeting-314:57
ajoreedip__,  davidsha I updated it14:57
*** bmotz has joined #openstack-meeting-314:58
*** Kamil has joined #openstack-meeting-314:58
reedip__ajo : yup, saw it14:58
davidsha+114:58
*** yamahata has joined #openstack-meeting-314:59
davidshaqould that be related then to the point underneath it?14:59
*** annegentle has quit IRC14:59
*** toddjohn has quit IRC15:00
*** SotK_ is now known as SotK15:00
rhochmuth#startmeeting monasca15:01
openstackMeeting started Wed Mar 23 15:01:16 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: monasca)"15:01
openstackThe meeting name has been set to 'monasca'15:01
shinya_kwbt_o/15:01
rhochmutho/15:01
rbako/15:01
Kamilo/15:01
*** davidsha has left #openstack-meeting-315:01
hosanaio/15:01
bmotzo/15:01
tomasztrebskio/15:02
bkleio/15:02
*** bryan_att has joined #openstack-meeting-315:02
rhochmuthMeeting agenda is posted at, https://etherpad.openstack.org/p/monasca-team-meeting-agenda15:02
rhochmuthAgenda for Wednesday March 23, 2016 (15:00 UTC)15:02
rhochmuth1. Horizon updates for Grafana 215:02
rhochmuthhttps://review.openstack.org/#/c/295983/15:02
rhochmuth3. Periodic metrics15:02
rhochmuth3.1 Initial state for sparse metrics? AlarmState.OK ?15:02
rhochmuth3.2 Value for sparse (period < 0) metrics? Force 1.0 as value, or leave it to be specified elsewhere ?15:02
rhochmuth3.2.1 Using aggregate functions when it comes to sparse metrics? 15:02
*** banix has quit IRC15:02
rhochmuth3.3 Should period be forced to -1 always ?15:02
rhochmuth3.4 Should alarm transition to AlarmState.OK in next cycle in case there were no metrics collected, given that previously it was AlarmState.ALARM? => for sparse only15:02
rhochmuth3.5 SubAlarm#getExpression#getPeriod  - logic behind, could it be somehow reused or is it something different at all?15:02
rhochmuth4, Mitaka release update and tagging15:02
rhochmuth5. InfluxDB 10.X update15:02
*** tgraichen has joined #openstack-meeting-315:03
*** baojg has quit IRC15:03
rhochmuthso, let's start with the grafana 2 update15:03
rhochmuth#topic grafana 215:03
*** openstack changes topic to "grafana 2 (Meeting topic: monasca)"15:03
rbakI don't have too much at the moment.15:03
*** fabiog has joined #openstack-meeting-315:03
rhochmuthi saw the review that you posted15:03
rbakI put up a patch for monasca-ui changes for grafana 2.15:03
rhochmuthi haven't tested, but I think it would be great to convert over15:04
rhochmuthhpe isn't the primary user of the ui anymore15:04
rhochmuthso, this would be up to other orgs to approve15:04
rbakI'm not sure who else is using the ui15:04
rhochmuthalso, your review is referencing your twc repos15:04
rbakYes, since that's where monasca is at the moment.15:04
rhochmuthfujitsu, nec, sap, ...15:04
*** absubram has joined #openstack-meeting-315:05
rbakgrafana, not monasca15:05
*** mrmartin has joined #openstack-meeting-315:05
rhochmuthtrue15:05
rhochmuthi think they are all interested in your grafana changes15:05
rhochmuthbut i'm not sure if they are using15:05
rhochmuthsap seemed very interested15:05
rhochmuthi believe joachim was looking at it15:06
bmotzwe're using it, and interested in the Grafana 2 update at some point - I'll try to have a look at the patch15:06
tgraichenmaybe just a little note from your side: darran hague from our team has added some more functionality to the grafana2 keystone stuff like syncing roles from keystone to grafana15:06
rhochmuththanks bmotz15:06
rhochmuththanks traichen15:06
tgraichenas far as i know ryan also implemented something like this and darran and ryan will try to merge their changes together somehow15:06
rhochmuthshinya, are you looking at grafana 215:07
shinya_kwbt_Sorry not yet15:07
rhochmuththx15:07
rbaktgraichen: Send me an email about those changes.  I think we might have some overlap15:07
*** TomEros has joined #openstack-meeting-315:07
shinya_kwbt_I will try15:07
tgraicheni rbak: arran will contact you i think15:07
rbaksounds good15:07
rhochmuthrbak: have you tested the devstack deploy15:08
rhochmuthwith your ui/grafana changes?15:08
rbakIt passed the testing, but I  haven't tested in devstack.15:08
rhochmuthit would be really nice to see this integrated in devstack15:09
rbakGrafana requires building the packages yourself, so the monasca-ui links aren't going to work by default in devstack.15:09
rhochmuthyou can actually do a build in devstack15:09
rhochmuthwe build the jave projects i beleive15:09
rbakI'll look into it15:10
rhochmuththe last time i tried the devstack build, horizon wasn't working for me15:10
rhochmuthso, it could have been somethign was out-of-sync15:10
rbakmonasca-ui, or horizon in general?15:10
rhochmuthhorizon in general15:10
rhochmuthanyway, i'l kinda anxious to get all this working in-time for the summit15:11
slogandid it generate a traceback or was some functionality just not working quite right?15:11
rhochmuthit generated a django traceback15:11
sloganthat would be nice to see15:11
rhochmuthnot sure what i did with the error15:11
*** jschwarz_ has quit IRC15:12
rhochmuthi'll try again15:12
*** openstackstatus has joined #openstack-meeting-315:12
*** ChanServ sets mode: +v openstackstatus15:12
shinya_kwbtI also want see traceback15:12
*** lpetrut has joined #openstack-meeting-315:12
sloganand some general steps that lead to the traceback if possible (standard stuff I know)15:12
rhochmuthok, i'll try and get one, but can't do right now15:13
sloganearly april I'm going to be putting together demos with broadview that will involve some amount of using monasca-ui grafana, if I see any bugs I'll report them (or fix them)15:14
rhochmuthrbak: do you have any status update on whether they are going to accept your changes?15:14
rhochmuthslogan: thanks15:15
rbakrhochmuth: That's not looking good at the moment.15:15
rhochmuthohh, what happened?15:15
rbakWe had a lot of communication for a while, and had a plan for moving forward, but then they just disappeared.15:16
*** wangbo has joined #openstack-meeting-315:16
rbakI haven't heard anything for a while now.  We're trying to get in touch again.15:16
rbakI'll give an update when I know more.15:17
rhochmuthok, thanks15:17
rhochmuthso, i guess we';; have to use your repos15:17
rbakfor the moment anyway.15:17
rhochmuthwell, anyway, just want to reitterate it would be nice to see this running in the devstack environment...15:19
rhochmuthi guess next topic15:19
rhochmuth#topic Periodic metrics15:19
*** openstack changes topic to "Periodic metrics (Meeting topic: monasca)"15:19
tomasztrebskithat's on me, lots and lots of questions :)15:20
rhochmuthwe might need to schedule a meeting on this one and get Craig involved15:20
rhochmuthi started to review last night15:20
rhochmuthand then craig told me he wasn't sure the direction you were headed was going to work15:20
rhochmuthso, it is probably best to have some one-on-one time with him15:21
rhochmuthbut, you are free to ask away15:21
rhochmuthif it is not too technical15:21
rhochmuthi'm a ptl you know15:21
sloganlol15:21
rhochmuththanks slogan15:21
tomasztrebskiyou're tough :) and my questions are not technical15:21
rhochmuthok15:22
rhochmuthplease proceed15:22
*** jobrs has joined #openstack-meeting-315:22
tomasztrebskimore or less I have couple points where I am not exactly sure where to go with implementation15:22
rhochmuthok15:22
*** askb has quit IRC15:22
tomasztrebskiso, first of all for sparse metric, I've been thinking what should be the initial state the alarm should enter15:22
tomasztrebskitill now it was UNDETERMINED, right ?15:23
rhochmuthcorrect15:23
tomasztrebskibut it was for periodic metrics15:23
rhochmuthright15:23
*** askb has joined #openstack-meeting-315:23
tomasztrebskishould stay the same at least till first measurements are received ?15:23
rhochmuthit probably makes sense that a sparse metric would transition immediately15:23
rhochmuththe alarm doesn't exist until the first metric is received15:24
tomasztrebskiwell, I've been testing it a bit and until first data arrives it stays with initial state UNDETERMINED15:24
rhochmuthin he case of a period metric, it doesn't transition until after it has received some number of metrics15:25
*** kebray has joined #openstack-meeting-315:25
rhochmuthso, the alarm is created when the first metric is received in the undetermined state15:25
sloganlazy instantiation15:25
*** wangbo has quit IRC15:25
rhochmuththen some number of metrics will need to be sent, until the threshold engine "has enough"15:25
rhochmuththen it will transition to ok or alarm15:26
tomasztrebskiyes15:26
*** vishwanathj_ has joined #openstack-meeting-315:26
tomasztrebskiok, IMHO it is better to put this to OK at once15:26
rhochmuthbut in the case of a sparse metric, it should transition when the alarm is created15:27
rhochmuthi agree15:27
rhochmuthat least in the sparse case15:27
rhochmuthit should transiiton to the ok or alarm state15:27
tomasztrebskiyes, because for periodic it should stay the same with one exception (if metric would come with period > 0, that value should be used)15:27
tomasztrebski*the behaviour should stay the same, I mean15:28
rhochmuthcorrect15:28
tomasztrebskiok, so if nobody has any objections, let's move on, I don't want to spend too much time asking ;-)15:28
*** toddjohn has joined #openstack-meeting-315:28
tomasztrebskinext questions is for values of "value" and "period"15:28
rhochmuthok15:29
tomasztrebskifor value I am not sure what should be the value, just make it 1.0 and stick to it or let any agent to set it on its own, but I'd rather think that it should be specified outside of the threshold engine (i.e. monasca-agent)15:29
tomasztrebskiI mean metric['value'] ;-015:30
tomasztrebskiand that's also question for sparse metrics only15:30
rhochmuthi'm not sure i follow15:30
rhochmuththe value is sent for a sparse metric15:30
*** haleyb_ has joined #openstack-meeting-315:30
rhochmuthso the value would normally just be the value of the last metric sent15:31
tomasztrebskimhm, yeah but it was better to ask, I got little lost in threshold engine but I need to come up with something at least testable15:31
rhochmuthi don't think using the avg function is useful for sparse metrics15:32
tomasztrebskimaybe not, I am not sure right now, but if it wouldn't make sense, we would need to modify logic somewhere to store period and in the same time do the same in monasca-ui to display only those functions that make sense15:33
rhochmuththat is a possiblity, but a lot more invasive15:35
rhochmuthi think the usage of the metric is implicit in the metric15:35
rhochmuthnot explicit15:35
tomasztrebskiso the question would be what functions are not suitable, if any...but maybe that's not the right time to debate over this, I will put this in the agenda that will give some time to think over this15:35
*** iyamahat has quit IRC15:35
*** haleyb_ has quit IRC15:36
rhochmuthso for a sparse metric, raking the avg over the last 5 minutes or hour, either doesnt' make sense, ir it is just the last value that was sent,15:36
rhochmuthunless multiple metrics were sent in the last time period15:37
tomasztrebskimaybe if you would like set the metric (as we need in alarm-on-logs) to establish avg amount of logs from entire system, maybe that would make sense15:37
tomasztrebski*set the alarm15:37
*** yamahata has quit IRC15:38
rhochmuthso, i'll talk to craig and will try and setup something with you to discuss implementation details further15:38
rhochmuthdoes that sound ok15:38
*** bpokorny has joined #openstack-meeting-315:38
tomasztrebskiyes, I will keep the rest of the questions for that meeting15:39
rhochmuthok, thanks15:39
rhochmuth#topic mitaka15:39
*** openstack changes topic to "mitaka (Meeting topic: monasca)"15:39
rhochmuthwe are coming up on the mitaka final release15:39
rhochmuthi'll need to apply tags to all the monasca repos over the next few days15:39
rhochmuthwe have a number of reviews in flight, mainly focused on bugs and performance improvmenets15:40
rhochmuthso, i would like to just focus on those for the next few days15:40
rhochmuthin general, our master branch is always in excellent shape15:40
rhochmuthso, i'm planning on moving tags to top of master by the end of the week15:40
rhochmuthplease heop out with reviews and testing if possible15:41
rhochmuthas this is our first major release with monasca15:41
rhochmuthofficial release that is15:41
rhochmuthif anyone knows of anything that needs to be or shoudl be adressed pleae let me know15:41
sloganhow does one gauge the priority of one review over another?15:41
sloganI recall when I was involved with neutron there would be a list somewhere15:42
rhochmuthbugs and performance enhancements are usually priortized above features15:42
rhochmuthwe dont' have an active list like neutron15:42
sloganthis priority is in the bug system (noob question)15:43
rhochmuthpossibly15:43
sloganok15:43
rhochmuthwe also have bugs that are reported by our representative orgs, like hpe15:43
sloganthere is some convention, like the commit message specifies the bug URI, or number?15:44
rhochmuthcorrect, we use that when bugs are reported via launchpad15:44
*** Sukhdev has joined #openstack-meeting-315:44
sloganok, cool15:44
rhochmuthbut sometimes bugs are jsut fixed, without a corresponding launchpad number15:45
rhochmuthi'm probably violating some openstack rule somewhere15:45
sloganI guess then it is a matter of using the mailing list or IRC to get people aware of severity15:45
*** cbouch has joined #openstack-meeting-315:45
rhochmuthyes, that is what we've been doing15:45
rhochmuthit is often teh sequeky whell principle15:45
rhochmuthbut if a review has been sitting around for a while15:46
rhochmuthusually just brining it up here is enoguht to get some attention to it15:46
rhochmuthsometimes reviews sit around a while because they are difficult to test15:46
rhochmuthor don't seem that important15:46
slogannod15:46
rhochmuthor folks are working on there own problems15:46
*** rockyg has joined #openstack-meeting-315:46
rhochmuthbut if it is raised here, usually someone gets to it15:47
sloganjust to be clear, any bugs I file will be priority 1 :-P15:47
rhochmuthi sometimes have to poke people here15:47
rhochmuthhaha15:47
rhochmuthok, hopeflly that is enough on that topic15:47
rhochmuthwe have around 10 minutes15:47
rhochmuthi was going to give an influxdb update15:48
rhochmuthbut if there is something elese that is pressing please let me know15:48
tomasztrebskiinflux is pressing to stop releasing db for free...15:48
rhochmuthtomasz: you can probably merge your review that deprecates the v2.0 log api15:48
*** catherineD has joined #openstack-meeting-315:48
sloganI've sent you e-mail about the summit and we can do that over e-mail if you like, I assume some rooms etc. were approvided15:48
sloganer, approved15:48
rhochmuthslogan: i don't know yet, but i'll get with you over email15:49
rhochmuthi'm still recovering from last week15:49
sloganperfect15:49
rhochmuthmabe i shouldn't take off anymore15:49
sloganI was thinking that...15:49
tomasztrebskiroland: ok, I will try to do this, I have one other thing to commit but once it is ready I'll just publish it15:49
slogan:-)15:49
*** woodster_ has joined #openstack-meeting-315:49
rhochmuthtomasz: cool, i'm just trying to get this into the mitaka release15:49
rhochmuthand time is running out15:50
rhochmuthalthough, we did merge the latest v3.0 code15:50
rhochmuthso that is in good shape15:50
rhochmuthi'll look for your changes15:50
*** anilvenkata has quit IRC15:51
rhochmuth#topic influxdb15:51
*** openstack changes topic to "influxdb (Meeting topic: monasca)"15:51
*** brunssen has joined #openstack-meeting-315:51
rhochmuthso, we had a discussion with them yesterday15:51
rhochmuththey are going to review to see if they come up with anything that would meet the requirement for an open-source ha influxdb15:51
rhochmuthi was wondering what other s thoguht about this announcement15:52
*** lblanchard has quit IRC15:52
rhochmuthand the impact15:52
*** dwalleck has joined #openstack-meeting-315:52
bmotzwe're more concerned about the clustering15:52
rhochmuththat is what i meant by the ha15:53
bmotzah, ok :)15:53
*** slogan is now known as slogan_away15:53
rhochmuthbasically, clustering in influxdb will be closed source15:53
bkleifrom what paul said, the free product without clustering will support HA, and ~400 metrics/sec15:53
bkleisorry -- 400K :)15:53
*** fawadkhaliq has quit IRC15:54
rhochmuthit is poor man's ha15:54
bmotzin the medium term we're looking at scaling to data rates an order of magnitude or three above that...15:54
rhochmuthbasially replication to another influxdb instance15:54
bkleibasically duplicate writes15:54
bkleiyup15:54
rhochmuthwhich we can already do in monasca using kafka and the persister15:54
*** moshele has joined #openstack-meeting-315:54
*** itoader has quit IRC15:54
rhochmuthcorrect, duplicate writes15:55
rhochmuthso, that implies databases coudl get out of sync15:55
bkleifor sure15:55
*** catherineD has left #openstack-meeting-315:55
bkleiyou get what you pay for :)15:55
rhochmuthkafka occers a certain amount of protection,15:55
rhochmuthyeah, i can't argue that15:55
rhochmuthfrom an hpe perspective, vertica is superior to influxdb15:55
fabiogfrom which version the clustering will be close source?15:56
fabiog0.11?15:56
rhochmuthit's only issue was that it is closed source15:56
bmotzand Vertica has a clearer pricing struture!15:56
rhochmuth0.1215:56
*** rbak has quit IRC15:56
*** rbak_ has joined #openstack-meeting-315:56
bkleiand vertica is free up to 1TB?15:56
rhochmuthi'm sure vertica is clearer, and proabbly more expensvie, after the 1TB limit15:56
*** dwalleck has quit IRC15:56
*** gema_ has joined #openstack-meeting-315:57
bkleidoes the free vertica < 1TB allow clustering?15:57
rhochmuthyes15:57
rhochmuthi think it is full featured, just a 1TB limit15:57
bkleithat's pretty good15:57
*** hdaniel has quit IRC15:57
rhochmuthyes, with the encoding, you are getting a significant amount of "compression"15:58
rhochmuthso 1 TB translates proabbly into around 2015:58
fabiogis there any TS opensource database that could fit the bill?15:58
shinya_kwbt_wow15:58
bkleii think the license limit is based on uncompressed ingest15:59
fabioglike OpenTSB or such?15:59
rhochmuthyes, that is true, but i don't think they count the encoding that we use as compression15:59
*** catherineD has joined #openstack-meeting-315:59
rhochmuthwe are still looking at cassandra15:59
*** lpetrut has quit IRC15:59
rhochmuthok, time is up everyone16:00
*** iyamahat has joined #openstack-meeting-316:00
rhochmuthi need to end the meeting16:00
rhochmuthbye16:00
bkleicya16:00
tomasztrebskiso cheers and good luck till next time16:00
Kamilbye16:00
tomasztrebskicya16:00
shinya_kwbt_bye16:00
*** cjvolzka has joined #openstack-meeting-316:00
hosanaithanks & bye16:00
*** bklei has quit IRC16:00
*** vgridnev has quit IRC16:00
rhochmuth#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
*** Kamil has quit IRC16:00
openstackMeeting ended Wed Mar 23 16:00:39 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
*** tomasztrebski has quit IRC16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-03-23-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-03-23-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-03-23-15.01.log.html16:00
*** tgraichen has quit IRC16:00
*** yamahata has joined #openstack-meeting-316:00
eglute#startmeeting defcore16:00
openstackMeeting started Wed Mar 23 16:00:49 2016 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** hosanai has left #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! here is the agenda for today: #link https://etherpad.openstack.org/p/DefCoreRing.1616:01
rockygo/ I'm here and I was early!16:01
*** dwalleck has joined #openstack-meeting-316:01
dwallecko/16:01
catherineDo/16:01
docaedoo/16:01
luzChello16:01
*** fabiog has quit IRC16:01
gema_o/16:01
egluteGood to see everyone here! And if you havent yet, raise your hand o/16:01
hogepodgeo/16:01
eglutePlease review agenda and amend as needed16:01
eglute#chair markvoelker16:02
openstackCurrent chairs: eglute markvoelker16:02
markvoelkero/16:02
brunsseno/16:02
eglute#topic Tempest tests analysis results16:02
*** openstack changes topic to "Tempest tests analysis results (Meeting topic: defcore)"16:02
*** moshele has left #openstack-meeting-316:02
eglutedwalleck did a lot of analysis on current tests, as discussed during the midcycle16:02
eglutedwalleck, go ahead16:02
*** lpetrut has joined #openstack-meeting-316:03
*** bmotz has left #openstack-meeting-316:03
*** ALUVial has joined #openstack-meeting-316:03
dwalleckSo based on feedback from the midcycle, I tinkered a bit the Tempest subunit output and found we could get the steps the test took easily from the output16:03
dwalleckAny HTTP requests that is. SSH or other steps should be possible to16:04
*** jaypipes has quit IRC16:04
*** anilvenkata has joined #openstack-meeting-316:04
dwalleckThis was the result: https://github.com/dwalleck/defcore-tools/blob/master/generated_test_analysis.txt (this was supposed to be markdown, but I had some last minute parsing issues)16:04
*** ALUVial has quit IRC16:05
dwalleckSome tests do some very weird and unexpected things. I'm still looking through the reporting now16:05
*** TomEros has quit IRC16:05
*** shinya_kwbt_ has quit IRC16:05
dwalleckI also did some manual analysis of the tests, which I'll wrap up this week: https://github.com/dwalleck/defcore-tools/blob/master/manual_test_analysis.txt16:05
gema_dwalleck: you generated that report automatically, right?16:06
gema_dwalleck: could you do that for the whole of tempest? or is that all of it?16:06
dwalleckThere's definitely opportunities for refactoring based on what I'm seeing16:06
eglutethis also shows how not-atomic some of these tests are16:07
*** jaypipes has joined #openstack-meeting-316:07
dwalleckgema_: You could do it for all of Tempest. I have links to the code we put together to do this in the etherpad for this week's meeting16:07
gema_dwalleck: awesome, thanks!16:07
dwalleckThe subunit parser: : https://github.com/arithx/subunit-parser and the pretty printer/reporter: https://github.com/dwalleck/defcore-tools/blob/master/process_results.py16:07
gema_yep, got it now, sorry I got carried away by the report16:08
dwalleckThis should live somewhere in an OpenStack repo if this turns out to be useful16:08
dwalleckNo worries!16:08
*** matrohon has quit IRC16:09
rockygmight be good in refstack repo.  or osops16:09
*** egallen has quit IRC16:09
eglutewhat does everyone think of this kind of analysis? I think tempest.api.compute.images.test_images_oneserver.ImagesOneServerTestJSON.test_create_delete_image test is a good example to look at16:09
dwalleckMy goal for next week is to have an etherpad with issues I've encountered that I think we can improve on16:09
rockygIt's a great start and a great tool.16:10
rockygQA could use it to prune/tweak tests to increase coverage and decrease duplication and run times16:11
eglutei agree rockyg16:11
dwalleckSo, to make sure I'm doing the right thing, does what I'm doing match up with what we talked about in Austin?16:11
eglutei also think we can use it for analysis what we want in defcore tests16:11
markvoelkerdwalleck: yes, this looks useful to me16:11
gema_dwalleck: definitely very useful, we can see gaps (not only good/bad test cases)16:12
dwalleckGood deal! Then I'll keep going down that path. I think slowrie and I are pretty close to done16:13
*** rhochmuth has quit IRC16:13
eglutei think this really illustrates the need for defcore to own the tests. perhaps as a defcore tempest plugin. what does everyone think?16:13
hogepodgeeglute: why?16:13
gema_dwalleck: I am a bit worried that some like line 564 don't have output16:13
eglutewhy which part?16:13
gema_dwalleck: not sure how to interpret that16:13
hogepodgeeglute: I don't see how defcore having to "own" the tests follows16:13
dwalleckgema_: If I'm thinking of the right issue, that test may not have any HTTP requests. It may just be doing SSH work16:14
dwalleckIdeally we'd have the asserts in here too, but that's phase 2 :)16:14
gema_dwalleck: ok, will look into it, what if it is using a client, would it show up?16:14
egluteright now we are dependent on these tests, that are part of the gate, etc. if we pull them into our own plugin, we could start fixing them, making them more atomic16:15
gema_eglute: or we could do that leaving them in place also16:15
hogepodgeeglute: the tests aren't broken.16:15
dwalleckeglute: I think with the list of potential refactors in hand, we can have a good conversation with the QA team to see if they find them useful16:15
eglutethe tests are not atomic. and not testing interop.16:15
*** kebray has quit IRC16:15
hogepodgeeglute: and nothing is stopping anyone fron contributing to tempest directly. It's what the tempest team wants16:15
catherineDI see that the auto generated report provides a good statistic on the API usages.  The manual report describes the tests themself.  Both are useful.  How could we scale to generate the manual report for all tests?16:16
rockygdwalleck,16:16
rockyg==16:16
rockyg++16:16
hogepodgeplus, we don't gate on plugins (yet)16:16
hogepodgeso a tempest plugin would not have the advantage of hundreds of tests running every day on every patch. Tempest has that directly16:16
eglutewe could have defcore gate job, no? either voting or non-voting?16:17
dwalleckhogepodge: There's definitely more going on here than interop. Some of them don't even test what they say there's testing (The AutoDisk/ManualDisk config tests don't actually test anything related to disk size and partition schema)16:17
rockygalso to add to what hogepodge says, it makes it very easy for our tests to diverge from tempest/gate tests and functionality16:18
dwalleckWe can try to fix them, but that's assuming the QA team agrees with the aspect of keeping tests atomic16:18
catherineDdwalleck: Is the a plan to auto generate the report this is generated maually ?16:18
dwalleckcatherineD: Yes, but that's a bit more work16:18
hogepodgedwalleck: I'm arguing to not throw away a valuable resource in tempest. If there's a weakness in the test suite, I want it fixed in the most effective way. Throwing away years of work and a highly functioning team is not the way to go about fixing the issues16:18
gema_hogepodge: +116:18
*** kebray has joined #openstack-meeting-316:18
docaedoIf a test is supposed to do something, but it doesn't, we shouldn't we be working on fixing the actual test, not making a different one somewhere else?16:18
dwalleckhodgepodge: I'm not advocating to throw it away. I'm talking about growing it forward16:19
rockygI think QA is swamped and needs help, but right now they are trying to fix framework issues.  If they had people to help with framework, they could review and accept more tests16:19
hogepodgedocaedo: fix the test upstream, or add  a new test to the existing test suite.16:19
eglutehogepodge i am not suggesting we depart from tempest... i am thinking of a tempest plugin, starting with existing tests.16:19
gema_eglute: what is the benefit of that16:19
dwalleckAnd I think that I have to demonstrate at least some examples of the issues I'm discussing for this discussion to have any meaning16:19
gema_vs keeping them in tempest?16:19
docaedohogepodge: yes, I agree - work with tempest directly16:19
hogepodgeeglute: no, that's a fork, and a fork is not in the spirit of open collaboration16:20
catherineDI think that these reports can at the minimum help DefCore to have an in-sight to the tests ...  at least they are useful in the selection of the must-pass tests16:20
docaedooh I typeoed - we SHOULD be working on fixing the actual test I meant16:20
rockygA spec from defcore for how to atomize (heheh) tests that defcore needs would go a long way in broadcasting both our needs and intentions for *tempest* tests16:20
dwalleckrockyg: To rocky's point, if we defined a spec backwards from the tests as is right now, you'd have a lot of noise16:21
gema_dwalleck: we should define the spec regardless of the tests16:21
gema_and then make the tests match the spec16:21
dwalleckIf these tests are the strict guidelines of what defcore is, then they need to be strict and concise16:21
rockygWe need to support Qa, not go aroun it.  At least where it makes sense.  We should fix the tests that are important to us and are in tempest before we go and start a new test project16:21
*** egallen has joined #openstack-meeting-316:21
dwalleckMy concern is that a functional test doesn't always equal a defcore test. I don't want to compromise what we're testing based on functional testing16:22
*** andymaier has quit IRC16:22
dwalleckFor example, the suggestion to remove all negative tests from Tempest16:23
rockygLet's first attempt to refactor/fix what we use, then we can discuss expanding/changing.  I think simply acting on the analysis will take stress off both defcore and QA16:23
gema_I think we are talking how to fix an issue that we don't even know if we have or what the extent of it is until dwalleck finishes the analysis16:23
rockygdwalleck, ++16:23
rockyggema ++16:23
gema_dwalleck: we'll have to talk to them about negative tests then16:24
dwalleckWhich I think now has been tabled, but could have heavily impacted DefCore. For my own sake outside of DefCore or gating, I would've made my own plugin repo because I use those tests16:24
hogepodgedwalleck: I'm not disagreeing that we can't have better api tests. I am disagreeing that we run off on our own with a plugin. It will be met with resistance, and part of our mandate is to be community driven. It's good analysis, but it does not follow that tempest must be abandoned, especially when they want to work with us16:24
catherineDgema_: ++ At the minimum dwalleck: 's complete reports can let DefCore knows the typed of must pass test chosen today16:24
egluteperhaps i misunderstand the tempest plugins. just trying to figure out how we can have better tests without running into various barriers that were brought up during midcycle and other discussions.16:24
rockygI think defcore/QA need a join design summit session16:24
markvoelkerhogepodge: genereally I'm ++ on working with the existing tests when possible.  I really don't want to get into the business of having two definitions for what defines "working" for any given feature.16:25
gema_eglute: we are not running into any barriers afaik we are not writing tests yet16:25
gema_or are we?16:25
dwalleckhogepodge: I'm not arguing that we run off and do something else. I'm saying I want to have this conversation with the QA team based on data and concepts16:25
rockygmarkvoelker, exactly16:25
rockygdwalleck, ++16:25
catherineDdwalleck: we need to identify the set of tests to talk with QA16:26
catherineDand your reports provide that16:26
rockygLet's see if we can schedule a discussion session with QA, then also a working session after to demo what dwalleck is talking about.16:26
dwalleckAt the end of the day, any of my analysis is my opinion. I'm not going to run off and work in a silo. But I think these are things worth discussing16:26
gema_dwalleck: absolutely16:26
eglute+1 on having a session with the QA team.16:27
hogepodgedwalleck: I'm not disagreeing about that16:27
rockygPOC.  any chance we could have a single/few tests refactored based on your tool analysis by summit?16:27
gema_dwalleck: but the more we can engage QA in the discussion and in the improvements / interop requirements, the better16:27
*** MarkAtwood has joined #openstack-meeting-316:27
markvoelkerSo dwalleck: perhaps with the Summit just around the corner that would be a good time to circle up w/QA?16:28
markvoelkerThat would give you some time to wrap up your analysis16:28
markvoelkerAnd for the rest of us to digest it16:28
dwalleckto a lot of people: yes, I'm just talking about the analysis and a few examples to help drive the possible discussion with QA. I think I've talked a lot about of these issues, and I think one or two examples would provide context16:28
catherineDdwalleck: ++16:29
gema_+116:29
rockyg++16:29
luzC++16:29
*** sigmavirus24 is now known as sigmavirus24_awa16:29
eglute#action markvoelker hogepodge eglute dwalleck schedule design session with QA team during the summit16:29
dwalleckAnd if the decision is to do nothing, that's fine :)16:29
catherineDLet single in one or two example and clearly acticulate why DefCore likes and does not like the tests.16:30
eglutei think so far everyone agrees that the analysis is great and want to see it done on all tests16:30
*** tqtran has joined #openstack-meeting-316:30
hogepodgedwalleck: that report is very valuable, it's useful to see the sequence of events that happens in a test. I'm really happy about it16:30
catherineDeglute: yes16:30
eglute+1 catherineD suggestion too16:30
egluteand it sounds like everyone would like a discussion with the QA team as well, correct?16:31
*** fawadkhaliq has joined #openstack-meeting-316:31
dwalleckThanks for the spirited discussion :) I have to duck out, but I'll follow up with an email in a bit16:31
eglutedwalleck has links to scripts on the etherpad16:31
rockygeglute, ++16:31
markvoelkerthanks dwalleck16:31
*** salv-orlando has joined #openstack-meeting-316:31
eglutenow that we ran him off, time for next topic :)16:32
dwalleckthanks folks!16:32
*** dwalleck has quit IRC16:32
eglute#topic scoring16:32
*** openstack changes topic to "scoring (Meeting topic: defcore)"16:32
*** MarkAtwood has quit IRC16:32
eglutemarkvoelker, i will hand this off to you :)16:32
markvoelkerPatches have been posted for Neutron and for moving the existing advisory capabilities to required per discussion at the midcycle16:32
markvoelkerSee etherpad for links16:32
*** haleyb_ has joined #openstack-meeting-316:32
markvoelkerOn the Neutron side, after speaking with the PTL we actually found one test currently in advisory that needs to be dropped as uses admin privs16:33
egluteSubnet pools: #link https://review.openstack.org/#/c/296426/16:33
markvoelkerPatch for that is up and listed in the etherpad too16:33
*** david-lyle has quit IRC16:33
*** wangbo has joined #openstack-meeting-316:33
eglute#link https://review.openstack.org/#/c/295313/ which removes an admin test from advisory16:33
*** david-lyle has joined #openstack-meeting-316:33
markvoelkerI'm actually not going to propose any new capabilities for Neutron this time...we did a pretty big addition last time, so we're fairly "caught up"16:33
*** spzala has quit IRC16:33
markvoelkerThe best candidate was subnet pools, but after investigating it's going to fall short on a couple of criteria.16:34
markvoelkerI've posted a patch the scoring sheet with some of those findings so we'll have the info for next time...I think it's a capability we'll add down the road, just not quite yet.16:34
markvoelkerSo with that: remember that we need to get all remaining scoring patches posted in the next few days!16:35
hogepodgeI'm going to be suggesting new capabilities for object storage/swift. I'll also test the swift plugin to see if it can be run from tempest. I don't think that can land this time around, it seems partially done16:35
*** fawadkhaliq has quit IRC16:35
hogepodgeplus new capabilities for cinder, some things we missed in the last round of scoring. no new information there.16:36
*** kebray has quit IRC16:36
*** fawadkhaliq has joined #openstack-meeting-316:36
markvoelkerhogepodge: thanks.  Let us know when patches are up. =)16:36
markvoelkerI think dwalleck had to step out, but from the etherpad it looks like he's ID'd some possible additions for Nova16:36
catherineDhogepodge: RefStack supports running with tempes plugin now  ... it woudl be great if you use RefStack and let us know if there is issue16:36
markvoelkergema: anything you need help with on Keystone?16:37
*** haleyb_ has quit IRC16:37
hogepodgecatherineD: +116:37
catherineDhogepodge: thx16:37
*** zz_dimtruck is now known as dimtruck16:37
*** hichihara has quit IRC16:37
*** ddieterly is now known as ddieterly[away]16:38
gema_markvoelker: sorry, was commenting on your patch16:38
gema_I have only one question16:38
gema_can I add tests from keystone tempest plugin?16:38
*** salv-orlando has quit IRC16:38
gema_or consider tests, rather16:39
markvoelkergema_: RefStack should support running tests via tempest plugin now16:39
gema_(I see scoring doesn't need fixes to the json just yet, right?)16:39
gema_markvoelker: alright, will do then16:39
*** vishwanathj_away is now known as vishwanathj16:39
gema_consider those capabilities as well :)16:39
*** spzala has joined #openstack-meeting-316:39
markvoelkergema_: Well, that depends...if you have a capability that you think scores high enough to be included, you should also add it to the json in the patch16:39
markvoelkerI didn't for the Neutron one because I don't think it'll make the cut16:40
gema_markvoelker: what is high enough?16:40
gema_(in your experience)16:41
*** ddieterly[away] is now known as ddieterly16:41
markvoelkergema_: WE've generally used 74 as a rough cutoff16:41
*** banix has joined #openstack-meeting-316:42
markvoelkerErrr, >74 that is16:42
*** salv-orlando has joined #openstack-meeting-316:42
gema_alright, will send the patch then soon, please review in depth as I have never done this before16:42
markvoelkergema_: sure thing16:42
gema_markvoelker: thanks!16:42
markvoelkerAnyone else with scoring updates?16:42
markvoelkerOk then.  Let's get those patches in folks. =)16:43
markvoelker#topic Update refstack-client to latest Tempest16:43
*** openstack changes topic to "Update refstack-client to latest Tempest (Meeting topic: defcore)"16:43
markvoelkercatherineD: was this your topic?16:44
catherineDyes16:44
markvoelkerThe floor is yours madame. =)16:44
*** spzala has quit IRC16:44
catherineDthx.  Any recommendation of which SHA we should use?16:44
*** Swami has quit IRC16:44
catherineDor should I just take the latest ... QA has not pulished an official tag version yet16:45
*** dedery has quit IRC16:45
*** oomichi has joined #openstack-meeting-316:45
*** spzala has joined #openstack-meeting-316:45
markvoelkercatherineD: I haven't tested in a few weeks at least so I don't think I have a SHA recommendation at the moment. I usually use latest though, personally.16:46
catherineDOk .. once we identify a SHA I will check the test names against the JSON file ... I expect some changes in the test names16:46
catherineDdo we want to document which SHA is used in DefCore?16:47
rockygyeah, mtreinish already talked about a number of changes16:47
catherineDIs there a place to hold the SHA name?16:47
markvoelkercatherineD: we actually don't have an official SHA to use per the interop site16:47
*** spzala_ has joined #openstack-meeting-316:48
rockygmarkvoelker, being able to have a sha for a working set of tests is good, though16:48
rockygit gives folks with issues a known good place to start debugging their setp16:49
markvoelkerrockyg: Sure.  Whenever I've noticed that the refstack default isn't working for some reason, I've submitted a patch to refstck to update it's default16:49
*** lpetrut has quit IRC16:49
markvoelkerrockyg: See https://review.openstack.org/#/c/203077/ for example16:50
*** spzala has quit IRC16:50
markvoelkerI think what catherineD is asking is whether anyone knows of a reason to update that to something newer right now...which I don't. =)16:50
rockygthanks, markvoelker16:51
eglutenot me. catherineD i trust your decision here16:51
*** alexpilotti has quit IRC16:51
rockygyeah.  wait until scores and capabilities firm up.  we have time16:52
catherineDOk... I will update RefStack to the latest version of Tempest ... our current version is September , 2015 ... time to update16:52
markvoelkercatherineD: I think we have some folks running tests in the next couple of weeks, so I'll ask them to use latest and let me know if they run into any problems. Will relay to you if they find anything.16:53
*** wangbo has quit IRC16:53
*** spzala_ has quit IRC16:53
catherineDmarkvoelker: great ...16:53
gema_catherineD: do you do testing around that?16:53
catherineDgema_: yes16:53
gema_catherineD: ++ thanks!16:53
markvoelkerOk, anything else on this topic?16:54
*** spzala has joined #openstack-meeting-316:54
catherineDI have 3 environment of different OpenStack release to test16:54
catherineDno from me16:54
eglutesounds like we can end a few minutes early16:54
*** salv-orlando has quit IRC16:54
gema_\o/16:54
eglutethanks everyone!!!16:55
eglute#endmeeting16:55
gema_thank you guys16:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:55
catherineDthank you16:55
openstackMeeting ended Wed Mar 23 16:55:07 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-03-23-16.00.html16:55
*** Swami has joined #openstack-meeting-316:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-03-23-16.00.txt16:55
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-03-23-16.00.log.html16:55
rockygthanks!16:55
*** anilvenkata has quit IRC16:56
*** vgridnev has joined #openstack-meeting-316:56
*** spzala_ has joined #openstack-meeting-316:56
*** alexpilotti has joined #openstack-meeting-316:56
*** brunssen has quit IRC16:57
*** spzala has quit IRC16:58
*** cbouch has quit IRC17:00
*** spzala_ has quit IRC17:00
bogdando#startmeeting ha_guide17:00
openstackMeeting started Wed Mar 23 17:00:56 2016 UTC and is due to finish in 60 minutes.  The chair is bogdando. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: ha_guide)"17:00
openstackThe meeting name has been set to 'ha_guide'17:01
bogdandohello17:01
*** catherineD has left #openstack-meeting-317:01
*** lpetrut has joined #openstack-meeting-317:01
*** krtaylor has quit IRC17:01
*** alexpilotti has quit IRC17:01
*** annegentle has joined #openstack-meeting-317:01
*** spzala has joined #openstack-meeting-317:02
bogdandoanyone around?17:02
*** vtech has quit IRC17:03
*** rossella_s has quit IRC17:03
*** rossella_s has joined #openstack-meeting-317:04
*** jlanoux has quit IRC17:04
*** spzala_ has joined #openstack-meeting-317:04
*** MarkAtwood has joined #openstack-meeting-317:04
*** dims_ has quit IRC17:05
*** spzala has quit IRC17:06
*** dims has joined #openstack-meeting-317:06
*** rockyg has quit IRC17:07
*** rhagarty has quit IRC17:07
*** Rockyg has joined #openstack-meeting-317:07
*** ajmiller has quit IRC17:07
*** rhagarty has joined #openstack-meeting-317:08
bogdandoanyone around?17:08
*** spzala_ has quit IRC17:08
*** ajmiller has joined #openstack-meeting-317:08
*** spzala_ has joined #openstack-meeting-317:09
bogdando#endmeeting17:10
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:10
openstackMeeting ended Wed Mar 23 17:10:07 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:10
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ha_guide/2016/ha_guide.2016-03-23-17.00.html17:10
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ha_guide/2016/ha_guide.2016-03-23-17.00.txt17:10
openstackLog:            http://eavesdrop.openstack.org/meetings/ha_guide/2016/ha_guide.2016-03-23-17.00.log.html17:10
*** Rocky_g has joined #openstack-meeting-317:10
*** Rockyg has quit IRC17:10
*** Rocky_g has quit IRC17:10
*** Rockyg has joined #openstack-meeting-317:11
*** krtaylor has joined #openstack-meeting-317:13
*** spzala_ has quit IRC17:13
*** spzala has joined #openstack-meeting-317:14
*** ihrachys has quit IRC17:16
*** jschwarz has quit IRC17:16
*** krtaylor has quit IRC17:17
*** tmazur has quit IRC17:19
*** spzala has quit IRC17:19
*** alexpilotti has joined #openstack-meeting-317:19
*** spzala has joined #openstack-meeting-317:20
*** alexpilotti has quit IRC17:23
*** krtaylor has joined #openstack-meeting-317:24
*** spzala has quit IRC17:25
*** klkumar has quit IRC17:27
*** spzala has joined #openstack-meeting-317:28
*** mkovacik__ has quit IRC17:29
*** vtech has joined #openstack-meeting-317:31
*** lblanchard has joined #openstack-meeting-317:33
*** spzala has quit IRC17:33
*** spzala has joined #openstack-meeting-317:34
*** mbound has quit IRC17:36
*** fawadkhaliq has quit IRC17:36
*** fawadkhaliq has joined #openstack-meeting-317:37
*** mbound has joined #openstack-meeting-317:38
*** spzala has quit IRC17:39
*** fawadkhaliq has quit IRC17:39
*** jmckind has quit IRC17:39
*** fawadkhaliq has joined #openstack-meeting-317:39
*** fawadkhaliq has quit IRC17:41
*** fawadkhaliq has joined #openstack-meeting-317:41
*** ddieterly is now known as ddieterly[away]17:42
*** bpokorny has quit IRC17:43
*** s3wong has joined #openstack-meeting-317:45
*** ivar-lazzaro has joined #openstack-meeting-317:45
*** egallen has quit IRC17:46
*** alexpilotti has joined #openstack-meeting-317:47
*** lpetrut has quit IRC17:47
*** fawadkhaliq has quit IRC17:47
*** yamamoto_ has quit IRC17:47
*** fawadkhaliq has joined #openstack-meeting-317:47
*** lpetrut has joined #openstack-meeting-317:47
*** salv-orlando has joined #openstack-meeting-317:48
*** spzala_ has joined #openstack-meeting-317:48
*** piet has quit IRC17:49
*** mbound has quit IRC17:51
*** bpokorny has joined #openstack-meeting-317:51
*** lpetrut has quit IRC17:52
*** piet has joined #openstack-meeting-317:52
*** spzala_ has quit IRC17:52
*** yamamoto has joined #openstack-meeting-317:52
*** spzala has joined #openstack-meeting-317:54
*** vishwanathj_ has quit IRC17:54
*** kairat_ has joined #openstack-meeting-317:55
*** askb has quit IRC17:55
*** kairat_ has left #openstack-meeting-317:58
*** spzala has quit IRC17:58
*** alexpilotti has quit IRC17:59
*** alexpilotti has joined #openstack-meeting-318:01
*** tellesnobrega is now known as tellesnobrega_af18:01
*** alexpilotti has quit IRC18:01
*** salv-orl_ has joined #openstack-meeting-318:01
*** alexpilotti has joined #openstack-meeting-318:02
*** tellesnobrega_af is now known as tellesnobrega18:02
*** egallen has joined #openstack-meeting-318:03
*** salv-orlando has quit IRC18:04
*** slogan_away has quit IRC18:05
*** Sukhdev has quit IRC18:06
*** sigmavirus24_awa is now known as sigmavirus2418:06
*** spzala has joined #openstack-meeting-318:06
*** alexpilotti has quit IRC18:07
*** vgridnev has quit IRC18:08
*** MarkAtwood has quit IRC18:08
*** piet has quit IRC18:10
*** kzaitsev_mb has joined #openstack-meeting-318:13
*** Aish has joined #openstack-meeting-318:13
*** alexpilotti has joined #openstack-meeting-318:13
*** annegentle has quit IRC18:14
*** alexpilotti has quit IRC18:14
*** alexpilo_ has joined #openstack-meeting-318:14
*** krotscheck has quit IRC18:14
*** krotscheck has joined #openstack-meeting-318:15
*** gabriel-bezerra has quit IRC18:15
*** alexpilo_ has quit IRC18:17
*** alexpilotti has joined #openstack-meeting-318:17
*** mrmartin has quit IRC18:17
*** alexpilotti has quit IRC18:18
*** MarkAtwood has joined #openstack-meeting-318:19
*** alexpilotti has joined #openstack-meeting-318:19
*** annegentle has joined #openstack-meeting-318:19
*** yamamoto has quit IRC18:19
*** vgridnev has joined #openstack-meeting-318:20
*** jobrs has quit IRC18:21
*** yamamoto has joined #openstack-meeting-318:24
*** gabriel-bezerra has joined #openstack-meeting-318:26
*** ihrachys has joined #openstack-meeting-318:26
*** krotscheck has quit IRC18:26
*** krotscheck has joined #openstack-meeting-318:26
*** piet has joined #openstack-meeting-318:28
*** mestery_ has joined #openstack-meeting-318:28
*** jaypipes has quit IRC18:31
*** sambetts is now known as sambetts|afk18:31
*** yamamoto has quit IRC18:33
*** mestery has quit IRC18:33
*** mestery_ is now known as mestery18:33
*** yamamoto has joined #openstack-meeting-318:33
*** yamamoto has quit IRC18:33
*** yamamoto has joined #openstack-meeting-318:34
*** mestery_ has joined #openstack-meeting-318:34
*** haleyb_ has joined #openstack-meeting-318:34
*** vgridnev has quit IRC18:35
*** yamamoto has quit IRC18:37
*** jaypipes has joined #openstack-meeting-318:38
*** krotscheck has quit IRC18:38
*** krotscheck has joined #openstack-meeting-318:39
*** annegentle has quit IRC18:39
*** haleyb_ has quit IRC18:40
*** sdake_ has joined #openstack-meeting-318:41
*** vgridnev has joined #openstack-meeting-318:42
*** ddieterly[away] has quit IRC18:43
*** yamamoto has joined #openstack-meeting-318:44
*** yamamoto has quit IRC18:44
*** sdake has quit IRC18:44
*** yamamoto has joined #openstack-meeting-318:44
*** yamamoto has quit IRC18:45
*** mestery_ has quit IRC18:46
*** sdake has joined #openstack-meeting-318:47
*** sdake_ has quit IRC18:49
*** vgridnev has quit IRC18:50
*** gabriel-bezerra has quit IRC18:51
*** openstack has joined #openstack-meeting-319:23
*** ChanServ sets mode: +o openstack19:23
*** openstackstatus has joined #openstack-meeting-319:23
*** ChanServ sets mode: +v openstackstatus19:23
*** zhiyan_ is now known as zhiyan19:23
*** DuncanT_ is now known as DuncanT19:24
*** sigmavirus24 has joined #openstack-meeting-319:25
*** alexpilotti has joined #openstack-meeting-319:25
*** cjvolzka has left #openstack-meeting-319:25
*** alexpilotti has quit IRC19:26
*** JasonF is now known as JayF19:30
*** annegentle has joined #openstack-meeting-319:34
*** Sukhdev has joined #openstack-meeting-319:39
*** spzala has quit IRC19:40
*** sreshetnyak has quit IRC19:42
*** dims_ has joined #openstack-meeting-319:43
*** spzala has joined #openstack-meeting-319:44
*** dims has quit IRC19:45
*** yamamoto has joined #openstack-meeting-319:45
*** kzaitsev_mb has quit IRC19:46
*** alexpilotti has joined #openstack-meeting-319:46
*** sreshetnyak has joined #openstack-meeting-319:47
*** kzaitsev_mb has joined #openstack-meeting-319:47
*** spzala has quit IRC19:49
*** alexpilotti has quit IRC19:51
*** ducttape_ has joined #openstack-meeting-319:53
*** dims_ has quit IRC19:53
*** yamamoto has quit IRC19:53
*** alexpilotti has joined #openstack-meeting-319:54
*** rocky_g has joined #openstack-meeting-319:54
*** alexpilotti has quit IRC19:55
*** alexpilotti has joined #openstack-meeting-319:55
*** alexpilotti has quit IRC19:56
*** dims has joined #openstack-meeting-319:56
*** alexpilotti has joined #openstack-meeting-319:56
*** alexpilotti has quit IRC19:56
*** TravT has joined #openstack-meeting-319:59
*** ajmiller_ is now known as ajmiller20:00
*** Sukhdev has quit IRC20:01
*** ediardo has joined #openstack-meeting-320:02
*** yamahata has quit IRC20:04
*** ihrachys_ has joined #openstack-meeting-320:04
*** tyr has joined #openstack-meeting-320:04
*** matt-borland_ has joined #openstack-meeting-320:05
*** ihrachys has quit IRC20:05
*** matt-borland_ has left #openstack-meeting-320:07
*** lpetrut has joined #openstack-meeting-320:12
*** e0ne has joined #openstack-meeting-320:17
*** openstack has joined #openstack-meeting-320:33
*** ChanServ sets mode: +o openstack20:33
*** e0ne has quit IRC20:37
*** Sukhdev has quit IRC20:38
*** sdague has quit IRC20:44
*** jmckind has quit IRC20:44
*** liangy has quit IRC20:45
*** jmckind has joined #openstack-meeting-320:47
*** liangy has joined #openstack-meeting-320:48
*** fawadkhaliq has quit IRC20:53
*** fawadkhaliq has joined #openstack-meeting-320:53
*** ivar-lazzaro has quit IRC20:54
*** david-lyle has quit IRC20:59
*** alexpilotti has joined #openstack-meeting-321:01
*** rossella_s has quit IRC21:03
*** rossella_s has joined #openstack-meeting-321:03
*** fawadkhaliq has quit IRC21:04
*** fawadk has joined #openstack-meeting-321:04
*** alexpilotti has quit IRC21:05
*** david-lyle has joined #openstack-meeting-321:05
*** rtheis has quit IRC21:06
*** jaypipes has quit IRC21:06
*** spzala has joined #openstack-meeting-321:06
*** sc68cal has quit IRC21:06
*** matrohon has joined #openstack-meeting-321:06
*** dtardivel has quit IRC21:08
*** alexpilotti has joined #openstack-meeting-321:08
*** spzala has quit IRC21:08
*** spzala has joined #openstack-meeting-321:08
*** nelsnelson has quit IRC21:10
*** nelsnelson has joined #openstack-meeting-321:10
*** alexpilotti has quit IRC21:12
*** vhoward has quit IRC21:13
*** neelashah1 has joined #openstack-meeting-321:15
*** neelashah has quit IRC21:16
*** ivar-lazzaro has joined #openstack-meeting-321:20
*** david-lyle has quit IRC21:21
*** ddieterly has joined #openstack-meeting-321:22
*** alexpilotti has joined #openstack-meeting-321:23
*** alexpilotti has quit IRC21:23
*** alexpilo_ has joined #openstack-meeting-321:23
*** david-lyle has joined #openstack-meeting-321:23
*** ivar-lazzaro has quit IRC21:24
*** Sukhdev has joined #openstack-meeting-321:26
*** sdake has quit IRC21:27
*** llight has joined #openstack-meeting-321:30
*** llight has left #openstack-meeting-321:30
*** gema_ is now known as gema21:33
*** baoli has quit IRC21:36
*** ddieterly is now known as ddieterly[away]21:36
*** lblanchard has joined #openstack-meeting-321:37
*** egallen has joined #openstack-meeting-321:39
*** egallen has quit IRC21:39
*** ddieterly[away] is now known as ddieterly21:40
*** rocky_g has quit IRC21:45
*** rocky_g has joined #openstack-meeting-321:45
*** matrohon has quit IRC21:49
*** banix has quit IRC21:49
*** matrohon has joined #openstack-meeting-321:50
*** doug-fish has quit IRC21:55
*** jmckind has quit IRC21:55
*** sdake has joined #openstack-meeting-321:55
*** ihrachys_ has quit IRC21:56
*** sigmavirus24 is now known as sigmavirus24_awa21:59
*** spzala has quit IRC22:07
*** spzala has joined #openstack-meeting-322:08
*** baoli has joined #openstack-meeting-322:09
*** ducttape_ has quit IRC22:09
*** matrohon has quit IRC22:12
*** spzala has quit IRC22:12
*** baoli has quit IRC22:18
*** dimtruck is now known as zz_dimtruck22:23
*** toddjohn has quit IRC22:29
*** sdake_ has joined #openstack-meeting-322:29
*** toddjohn has joined #openstack-meeting-322:29
*** sdake has quit IRC22:30
*** toddjohn has quit IRC22:33
*** rocky_g has quit IRC22:39
*** spzala has joined #openstack-meeting-322:46
*** fawadk has quit IRC22:53
*** fawadkhaliq has joined #openstack-meeting-322:53
*** yamahata has joined #openstack-meeting-322:54
*** fawadkhaliq has quit IRC22:55
*** lblanchard has quit IRC22:56
*** fawadkhaliq has joined #openstack-meeting-322:56
*** sdake_ is now known as sdake22:59
*** neelashah1 has quit IRC22:59
*** ddieterly has quit IRC23:02
*** toddjohn has joined #openstack-meeting-323:05
*** darrenc_ has joined #openstack-meeting-323:05
*** flwang2 has quit IRC23:06
*** darrenc has quit IRC23:06
*** darrenc_ is now known as darrenc23:07
*** fawadkhaliq has quit IRC23:07
*** fawadkhaliq has joined #openstack-meeting-323:08
*** mickeys has joined #openstack-meeting-323:09
*** mickeys has left #openstack-meeting-323:10
*** jpomeroy has quit IRC23:16
*** lblanchard has joined #openstack-meeting-323:19
*** lblanchard has quit IRC23:19
*** absubram has quit IRC23:21
*** openstack has joined #openstack-meeting-323:24
*** ChanServ sets mode: +o openstack23:24
*** fawadkhaliq has quit IRC23:39
*** fawadkhaliq has joined #openstack-meeting-323:49
*** k-ishii has joined #openstack-meeting-323:50
*** hoangcx has joined #openstack-meeting-323:55
*** galstrom_zzz is now known as galstrom23:57
*** Sukhdev has quit IRC23:57
*** toddjohn has quit IRC23:58
*** toddjohn has joined #openstack-meeting-323:58
*** spzala has quit IRC23:59
*** Sukhdev has joined #openstack-meeting-323:59
*** ajmiller has quit IRC23:59

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