08:00:20 <ifat_afek> #startmeeting vitrage
08:00:21 <openstack> Meeting started Wed Nov 29 08:00:20 2017 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:00:22 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:00:24 <openstack> The meeting name has been set to 'vitrage'
08:00:30 <ifat_afek> Hi :-)
08:01:21 <yujunz> Hi
08:02:10 <Liat> Hi
08:02:17 <eyalb> (ό‿ὸ)ﾉ
08:02:39 <idan_hefetz> hi
08:05:30 <ifat_afek> Today’s agenda:
08:05:38 <ifat_afek> •	Status and Updates
08:05:44 <ifat_afek> •	Open Discussion
08:05:50 <ifat_afek> #topic Status and Updates
08:06:05 <ifat_afek> The next PTG will be in Dublin, on February 26 – March 2.
08:06:14 <ifat_afek> We should announce by next week whether we would like Vitrage to participate in the PTG, or whether we prefer to have a virtual PTG as we did last time. Let me know if you have any preference.
08:06:28 <ifat_afek> Sometime in the near future we should release the first Queens version of Vitrage.
08:06:37 <ifat_afek> We should decide when is the right time for that. Personally, I prefer to finish the changes for Mistral first, as they will affect the template format.
08:06:44 <ifat_afek> Any other considerations?
08:06:56 <ifat_afek> My updates: I created a spec for refactoring the execute-mistral action.
08:07:01 <ifat_afek> #link https://review.openstack.org/#/c/523396/
08:07:10 <ifat_afek> And I started working on the first task, which is to introduce versions to the Vitrage templates.
08:07:12 <ifat_afek> That’s it for me
08:07:35 <ifat_afek> Anyone else?
08:07:43 <yujunz> Does such release results in a feature frozen for a period?
08:07:54 <ifat_afek> No
08:08:24 <ifat_afek> They want every project ot have a release at least once. I’m not sure why. But it will not be our final release
08:08:52 <ifat_afek> Some projects follow the cycle-with-milestones release model, and they are about to make their second release (m2)
08:08:57 <yujunz> OK. "They" mean OpenStack governance?
08:09:07 <ifat_afek> We *can*, if we want, decide on a feature freeze. Do you think we should?
08:09:09 <ifat_afek> Yes
08:09:27 <yujunz> I don't think feature frozen is necessary.
08:09:29 <ifat_afek> I actually feel that we should use the final Queens release and not intermediate releases
08:09:34 <ifat_afek> Ok
08:09:38 <yujunz> Since few projects depends on Vitrage
08:09:45 <ifat_afek> Right
08:10:02 <ifat_afek> But we need to find a time that we feel that the release is relatively stable
08:10:16 <ifat_afek> And run some checks, of course
08:10:40 <yujunz> Agree.
08:11:41 <yujunz> My updates: proactive RCA blueprint got approved, gonna work on the sub blueprint the week after next
08:12:00 <yujunz> I am busy preparing for OPNFV PlugFest which is coming next week
08:12:21 <ifat_afek> Good luck, what are you presenting?
08:12:37 <yujunz> I will fly to Portland this Saturday to present benchmarking service for OPNFV community
08:12:55 <yujunz> The presentation is next Wedneday
08:13:15 <ifat_afek> Enjoy
08:13:29 <ifat_afek> Anyone else wants to update?
08:13:39 <yujunz> For next PTG, I will discuss with ZTE team and let you know our preference.
08:13:47 <yujunz> That's all.
08:13:54 <ifat_afek> Ok, thamks
08:14:03 <dwj> My updates: integrate Vitrage with doctor using Devstack env, means local installer in doctor.
08:14:44 <dwj> But I have some issues about using keystone client to get Vitrage endpoint. Troubleshooting about this.....
08:15:06 <ifat_afek> You mean integration that is currently done in the Doctor code, right?
08:15:23 <ifat_afek> Let us know if you need some help
08:15:48 <dwj> Not done yet. #link https://gerrit.opnfv.org/gerrit/#/c/47835/
08:16:31 <ifat_afek> I meant “being one” :-)
08:16:36 <ifat_afek> done
08:17:28 <idan_hefetz> I will update
08:17:49 <idan_hefetz> i have pushed a few tests to tempest
08:17:59 <idan_hefetz> Adding basic tests to actions
08:18:11 <idan_hefetz> including the new mark down for instances
08:18:27 <idan_hefetz> Also testing overlapping template actions
08:18:56 <idan_hefetz> Another thing, we have found out is that these actions no longer work in python 3.5
08:19:26 <idan_hefetz> THis is probably due to the multiprocessing added in the parallel evaluation blueprint
08:19:38 <nivolas> hey
08:19:58 <yujunz> Why it is related to Python 3.5?
08:20:29 <idan_hefetz> I'm not sure, but in 3.5 it causes an exception
08:20:46 <idan_hefetz> I have yet to investigate this
08:20:58 <idan_hefetz> Eyal and i have been discussing replacing this queue with rabbit
08:21:17 <dwj> You mean don't send the notification to notifier, which we found the bug before?
08:21:18 <ifat_afek> I think the issue is that prior to this change we just didn’t have these tempest tests, so we didn’t know about the problem
08:21:19 <idan_hefetz> I mean the evaluator queue
08:21:44 <idan_hefetz> the one between the evaluator workers and the processor
08:21:57 <dwj> Ok
08:22:11 <idan_hefetz> That my update
08:22:49 <nivolas> I added/fixed some tempest tests, so I think before about 11 tests were running and now around 23 tests are running
08:23:04 <eyalb> +1
08:23:07 <ifat_afek> +1
08:23:18 <yujunz> +1
08:24:04 <idan_hefetz> btw There are more tests in the datasources execution
08:25:17 <ifat_afek> Ok. Any other updates?
08:25:25 <peipei> I will update.
08:26:40 <peipei> Code of snmp_parsing service has been finished, and I am preparing environment to run test cases.
08:27:09 <peipei> The code will be submmitted recently.
08:27:15 <idan_hefetz> Cool!
08:27:19 <ifat_afek> Great
08:27:29 <peipei> : -)
08:27:55 <yujunz> "recently" you mean "soon"?
08:28:26 <peipei> Yes, should be this week
08:28:40 <yujunz> Great
08:28:41 <ifat_afek> Great
08:29:17 <ifat_afek> Anyone else?
08:30:38 <ifat_afek> Moving on
08:30:40 <ifat_afek> #topic Open Discussion
08:30:52 <ifat_afek> Another issue is i18n support in Vitrage.
08:31:07 <ifat_afek> Someone from Italy sent me a question and attached some screenshots. I noticed that some of the titles were in Italic (Topologia, Informazioni :-)) while others were in English.
08:31:17 <ifat_afek> AFAIK we don’t have any i18n support in Vitrage, so I opened a blueprint for this purpose:
08:31:25 <ifat_afek> #link https://blueprints.launchpad.net/vitrage/+spec/support-i18n
08:31:32 <ifat_afek> Not sure about the urgency
08:31:37 <yujunz> This is mainly for vitrage-dashboard right?
08:31:56 <ifat_afek> I think so, but I didn’t check it really
08:32:18 <ifat_afek> Maybe it is relevant only to the error messages
08:32:44 <yujunz> It should be quite easy to do i18n in django.
08:33:21 <ifat_afek> There is a common way to handle it in OpenStack, it’s just a matter of learning how
08:33:41 <yujunz> Will you consider supporting Hebrew?
08:33:47 <ifat_afek> :-)
08:33:59 <yujunz> Does OpenStack support UI reading from right to left?
08:34:02 <ifat_afek> I don’t think it’s a priority
08:34:27 <ifat_afek> Our customers don’t expect Hebrew
08:34:50 <yujunz> Italian should be easy since nothing special in the letters or encodings, I suppose.
08:34:52 <ifat_afek> I have no idea about right to left :-)
08:36:58 <ifat_afek> Any other open issue?
08:37:26 <yujunz> Nope
08:37:39 <ifat_afek> Ok, so let’s close the meeting
08:37:53 <eyalb> bye
08:37:57 <ifat_afek> Bye
08:37:59 <dwj> bye
08:38:01 <peipei> bye
08:38:08 <ifat_afek> #endmeeting