08:00:18 <ifat_afek> #startmeeting vitrage
08:00:19 <openstack> Meeting started Wed Jul 26 08:00:18 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:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:00:22 <openstack> The meeting name has been set to 'vitrage'
08:00:24 <ifat_afek> Hi :-)
08:00:33 <danoffek> Hi Guys
08:00:49 <annarez> Hi
08:01:48 <yujunz> jhi
08:01:59 <nivolas> hey
08:02:30 <sevenmode> hi
08:02:43 <ifat_afek> Today’s agenda:
08:02:53 <ifat_afek> •	Pike Feature Freeze
08:02:57 <ifat_afek> •	Status and Updates
08:03:03 <ifat_afek> •	Open Discussion
08:03:12 <ifat_afek> #topic Pike Feature Freeze
08:03:27 <ifat_afek> Reminder about the release dates:
08:03:37 <ifat_afek> Client libraries final releases (i.e. python-vitrageclient): July 27 — tomorrow!
08:03:43 <ifat_afek> Pike-3 milestone (and Feature freeze): July 27
08:03:48 <ifat_afek> Final Pike release: August 30
08:03:59 <ifat_afek> Tomorrow is the release date for python-vitrageclient. I plan to tag the release today or tomorrow. If someone has a change that must enter, please tell me ASAP.
08:04:05 <adary> hi
08:04:21 <yujunz> When will stable/pike be branched?
08:04:30 <yujunz> I mean for vitrage repo
08:04:49 <ifat_afek> I see that we need to close the following changes: doc migration and os profiler
08:05:14 <ifat_afek> For Vitrage we can decide when, it can be anytime until the final release date
08:05:46 <ifat_afek> projects that follow the cycle-with-milestones mode, should branch soon. We work by cycle-with-intermeidary, so it’s up to us to decide
08:06:02 <ifat_afek> But the client libraries must all branch this weekend
08:07:05 <ifat_afek> yujunz: Regarding the os profiler, all you have left in the python-vitrageclient is the small change of moving the help message?
08:07:24 <yujunz> Yes, unless we found some bug in it.
08:07:37 <yujunz> No other modification is planned on my side
08:08:19 <ifat_afek> Ok, thanks
08:08:25 <yujunz> BTW, is there a full list of the frozen features?
08:08:36 <yujunz> Can I trust https://blueprints.launchpad.net/vitrage/pike or it needs updating?
08:09:59 <ifat_afek> Seems like not all of the blueprints will enter pike. 	aodh-support-more-alarm-types and alarm-counts-api will probably be left out
08:10:31 <ifat_afek> I’ll have to ask idan_hefetz about the parralel-evaluation
08:11:11 <ifat_afek> The rest of the features should be in. support-python35 is a must, and the integration with Mistral is practically done, I just need to add tests
08:12:41 <ifat_afek> If any of you wants to introduce new specs, they should enter Queens version and be written under specs/queens/approved
08:13:00 <ifat_afek> Anything else regarding the release?
08:13:36 <ifat_afek> #topic Status and Updates
08:14:14 <ifat_afek> My updates:  I’m working on three tasks in parallel…
08:14:23 <ifat_afek> Doc-migration: the OpenStack documentation team decided about a re-org of the documents. I completed the relevant changes in our projects.
08:14:28 <ifat_afek> #link https://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html
08:14:33 <ifat_afek> #link https://review.openstack.org/#/q/projects:openstack/vitrage+branch:master+topic:doc-migration
08:14:41 <ifat_afek> #link https://review.openstack.org/#/q/projects:openstack/python-vitrage+branch:master+topic:doc-migration
08:14:49 <ifat_afek> In addition, I’m working on supporting the python-35 Pike goal
08:14:55 <ifat_afek> #link https://governance.openstack.org/tc/goals/pike/python35.html
08:15:01 <ifat_afek> #link https://review.openstack.org/#/c/486591
08:15:14 <ifat_afek> Our code already supports python35, but our tempests are still running on a python27 devstack. I’m trying to add jobs for running them on python35 devstack.
08:15:23 <ifat_afek> Last task: finish the integration with Mistral. I am basically done, but need to add tests
08:15:29 <ifat_afek> #link https://review.openstack.org/#/c/461265/
08:15:39 <ifat_afek> That’s it for me
08:16:08 <yujunz> Will py35 devstack become voting?
08:16:21 <yujunz> I saw in the commit message it is non-voting for now
08:17:44 <ifat_afek> It should be voting, but right now it’s not working. I changed it to “experimental” mode
08:18:17 <yujunz> OK.
08:18:18 <ifat_afek> That’s defined as a community-goal for Pike
08:18:22 <ifat_afek> So it’s a must
08:18:41 <ifat_afek> Why, is there any issue you can think of?
08:18:54 <yujunz> Nothing, just curious on the commit message :-)
08:19:09 <ifat_afek> I’m thinking about the fact that it will double our gate time… but I see no other alternative
08:19:20 <yujunz> Double?
08:19:33 <yujunz> Isn't it running in parallel? py27 and py35?
08:19:40 <ifat_afek> Instead of running the tempest tests on py27, we will run on both envs
08:19:50 <ifat_afek> At list I think we need to run on both envs...
08:20:11 <ifat_afek> Maybe we can do one of them only at the gate and not in the first check phase
08:20:44 <ifat_afek> Yes, maybe it runs in parallel. I actually didn’t think about it :-)
08:22:14 <ifat_afek> idan_hefetz: I see you are in. Do you expect the parallel-evaluation blueprint to end in Pike?
08:22:48 <ifat_afek> (yujunz asked about the list of blueprints that are marked for pike)
08:23:27 <idan_hefetz> Parallel evaluation is in progress, what’s left is to resolve an issue regarding overlapping-templates feature and add some testing.
08:24:41 <idan_hefetz> I am thinking to commit the initial code (that will be disabled in configuration) in the coming days
08:25:03 <ifat_afek> Ok, thanks
08:25:20 <idan_hefetz> Also
08:25:39 <idan_hefetz> I just stumbled upon a bug with the static datasource
08:26:30 <idan_hefetz> edges created by it are deleted after some time, that is after the second get_all
08:27:20 <idan_hefetz> I should open a bug in lunchpad
08:27:45 <idan_hefetz> launchpad :)
08:28:41 <ifat_afek> Ok
08:28:47 <ifat_afek> Anyone else wants to update?
08:28:53 <yujunz> My update: finishing up the blueprint osprofiler
08:29:44 <yujunz> #link https://review.openstack.org/#/q/branch:master+topic:bp/osprofiler-support
08:29:53 <ifat_afek> And what about the implementation? I saw there are some changes in gerrit, do they cover everything or is there some more work to be done?
08:30:49 <yujunz> Yes, I suppose it is all that is required for integration. But we may add more trace point when we tackle a performance issue in future
08:31:36 <ifat_afek> Ok, adding more trace points will be trivial, I guess
08:31:47 <yujunz> I meant finish the implementation of the blueprint
08:32:08 <ifat_afek> Right
08:32:19 <yujunz> Another trivial update on healthcheck api
08:32:29 <yujunz> #link https://review.openstack.org/#/c/485991/
08:32:41 <ifat_afek> Can you explain the change?
08:33:13 <yujunz> A conversion of the healthcheck was hardcoded
08:33:33 <yujunz> A conversion of healthcheck result
08:33:49 <yujunz> I think it would be better to display as it is
08:34:03 <yujunz> Better for compability
08:34:50 <yujunz> That's all for me
08:34:59 <ifat_afek> Ok, I’ll have a look
08:35:08 <ifat_afek> Anyone else wants to update?
08:37:29 <ifat_afek> Thanks everyone, see you next week :-)
08:37:36 <yujunz> Bye
08:37:36 <adary> bye
08:37:38 <danoffek> bye
08:37:48 <annarez> bye
08:38:03 <ifat_afek> #endmeeting