16:00:41 #startmeeting Mistral 16:00:41 Meeting started Mon Nov 16 16:00:41 2015 UTC and is due to finish in 60 minutes. The chair is rakhmerov. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:42 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:46 The meeting name has been set to 'mistral' 16:00:51 hi everyone! 16:00:55 hi, please name yourself! ) 16:00:57 hi 16:00:58 hi there 16:01:00 hi 16:01:11 I am Nastya 16:01:51 Hi all 16:01:52 oops, you meant different 16:01:53 akuznetsova: we know that! :) 16:01:56 hi Limor 16:02:24 1 min... 16:03:38 ok, I'm here 16:04:04 ^Gal^: hi, I approved https://review.openstack.org/#/c/245773/ but please fix a couple minor style issues with your next patches 16:04:10 ok 16:04:19 there's no special agenda for today actually 16:04:24 #topic Review Action items 16:05:01 1. rakhmerov: create Mitaka series and milestone in python-mistralclient LP 16:05:08 #action rakhmerov: create Mitaka series and milestone in python-mistralclient LP 16:05:09 :) 16:05:25 2. melisha: Write docs about https://blueprints.launchpad.net/mistral/+spec/mistral-async-actions-doc in M-1 16:05:27 :) 16:05:45 this should not be evaluated now, we'll be tracking it in LP 16:05:56 3. rakhmerov, melisha: design "Mistral HA" and "Multi-region sport" during M-1 16:06:13 not done, I'll keep it for records 16:06:21 #action rakhmerov, melisha: design "Mistral HA" and "Multi-region support" during M-1 16:06:34 4. rakhmerov: ping melisha and look at the bugs together 16:06:35 done 16:06:49 #topic Current status (progress, issues, roadblocks, further plans) 16:06:58 let's share our statuses quickly 16:07:14 one by one 16:07:22 specifically, I'm interested if you have any roadblocks preventing you fro moving forward 16:07:34 xylan_kong: go ahead 16:07:36 1. [ready for review] complete the implementation of 'mistral workflow sharing as a reference implementation of resource sharing feature', https://review.openstack.org/244155 16:07:43 2. [ready for review] complete integration of mistral client and openstack client, https://review.openstack.org/245034 16:07:51 3. [merged] a good news! The mistral-spec repo has been merged in mistral namespace, please see https://github.com/openstack/mistral-specs 16:07:57 4. [in progress] add reno support in mistral, which I'm also trying to understand its mechanism 16:08:02 5. [always] review work 16:08:10 awesome! 16:08:20 my status: review, made a couple of minor patches, thinking about what do next 16:08:20 xylan_kong: I'll review your patches tomorrow 16:08:35 for mistral-specs, I'll make some initial changes and write a detailed introduction about the new process later on. 16:08:39 xylan_kong: let's talk about this new process today later 16:08:47 rakhmerov: oik 16:08:51 my status : working on internal alcatel issues and we need to start testing mistral this week 16:09:01 <_gryf> Today was a first meeting for openstack-ha. Here is the link for the minutes: http://eavesdrop.openstack.org/meetings/ha__automated_recovery_from_hypervisor_failure/2015/ha__automated_recovery_from_hypervisor_failure.2015-11-16-09.00.html 16:09:05 my status: fixed work mistralclient with unverified keystone cert (SSL/TLS), fixing async actions to send callback url for sending result back to Mistral 16:09:21 also a lot of review today 16:09:34 <_gryf> the reason I'm rising it on mistral miting is the fact, that people are very interested in proposed mistral solution for evac task 16:09:49 _gryf: glad to hear that 16:09:53 my status: mostly doing reviews and bug review 16:10:23 _gryf, very interesting... 16:10:25 _gryf: i'll take a look to see how we can help for that 16:10:30 <_gryf> cool! 16:10:35 _gryf: I know that, I talked to a bunch of people about that at the summit (5-6) 16:11:05 #action rakhmerov: review http://eavesdrop.openstack.org/meetings/ha__automated_recovery_from_hypervisor_failure/2015/ha__automated_recovery_from_hypervisor_failure.2015-11-16-09.00.html 16:11:19 ok, we'll see what they discussed 16:11:54 ok, thanks 16:12:02 any serious roadblocks? 16:12:15 xylan_kong: can we already start using spec repo? 16:12:26 for our new big BPs 16:12:47 rakhmerov: not for now, need to put a template file and some directories 16:13:05 ok, let us know when it's done 16:13:10 but i think it will not be very late 16:13:11 ok 16:13:16 sure 16:13:22 #topic Open Discussion 16:13:36 xylan_kong: can you briefly tell us about this reno thing? 16:13:46 and changes to maintaining stable branches 16:14:07 rakhmerov: hehe, i 'm also trying to understand well about reno 16:14:08 these are 2 things I'm interested in (since you are a liason now) 16:14:24 what were you able to understand so far? :)) 16:14:26 not much? 16:14:33 for now, i just copy something from the examples Doug have given 16:14:46 to make sure we are far behind it 16:14:51 not 16:15:08 any details? 16:15:34 ok, then let's talk about that offline once you get enough details 16:15:42 sorry for the dumb question but what is reno? 16:16:03 I saw that there was a bunch of info on that but I didn't have a chance to get familiar with it 16:16:05 in my undersdanding, reno will track the features or bugs made to mistral automatically 16:16:15 LimorStotland: yes, that's what I'm asking too 16:16:18 but you need add patches for the feature and bug description 16:16:31 ok 16:16:45 xylan_kong : right, reno will organize the notes you add, but you have to write them yourself 16:16:45 LimorStotland: http://lists.openstack.org/pipermail/openstack-dev/2015-November/078301.html 16:17:02 dhellmann: ooh, you're here 16:17:07 Thanks xylan_kong 16:18:02 dhellmann: ok, we'll pick that up 16:18:02 rakhmerov, nmakhotkin_ , you can ask dhellmann for your questions, i think nobody understand reno better than him 16:18:03 thanks 16:18:09 dhellmann :-) 16:18:15 sure, thanks 16:18:39 and i will understand it by myself 16:19:13 ok, sure. I just don't want to ask dhellmann about that (knowing that he's extremely busy) until I read something (or ask you) that was sent out in ML 16:19:33 sure, if you have deep questions please post as a follow-up to that mailing list thread so everyone can benefit from the answers 16:19:37 rakhmerov: ok, no problem 16:19:52 dhellmann: we will 16:20:05 rakhmerov : thanks! 16:22:02 rakhmerov: you can add an action for me 16:22:05 so team, I don't have much else to discuss today. We're deeply in M-1 now 16:22:11 about reno 16:22:16 xylan_kong: you can add yourself :) 16:22:23 ok, let me do that 16:22:37 #action xylan_kong: learn about reno and share with the team 16:22:43 #action xylan_kong: understand better about reno 16:22:46 :) 16:22:51 double action! 16:22:52 :-) 16:22:58 that's fine 16:23:15 ok, so, I thank all of you, I see a lot of patches on review. I'll try to do a better job on reviewing them 16:23:21 and encourage everyone to do so 16:23:30 lots of good bugfixes 16:23:46 yes, i have put more efforts on code works these days 16:23:55 Moshe's patch about CT is about to get merged, I'm really looking forward to see it done 16:24:01 ok 16:24:13 I have a question 16:24:17 yep 16:24:21 go ahead 16:24:46 Moshe is working on functional tests 16:25:02 I want to start work on doing our dsvm gates voting 16:25:07 LimorStotland: IMO it should be a separate patch 16:25:31 before it I want to make some refactoring in mistral devstack scripts and functional tests 16:25:37 Ok i will let him know 16:25:46 akuznetsova: we can't technically do it before we figure out how to solve a cycle problem 16:25:52 betwee mistral and client 16:26:05 akuznetsova: yep 16:26:06 sure 16:26:17 I don't like your suggestion 16:26:21 agree with rakhmerov 16:26:48 how do we solve this cyclic dependency problem? 16:26:55 I think that it will be better to make all perfect and only after it make it voting :-) 16:27:00 don't know yet 16:27:15 akuznetsova: the problem is deeper than that :) 16:27:35 such situations will pop up anyway 16:27:44 when we have to break the gate 16:27:54 I remember about cycle problem, I am going to think about it too 16:28:10 rakhmerov, nmakhotkin_ what's the problem you mean? i am not sure i know that... 16:28:16 actually whenever we make incompatible API changes for example (e.g. if we're working on a new API and it's not ready yet) 16:28:23 need to investigate how other project live with it 16:28:33 akuznetsova: yes 16:28:43 xylan_kong: let me explain it tomorrow :))) 16:28:49 rakhmerov: fine 16:28:49 it's going to be a long conversation :)) 16:28:52 I guess other projects don't launch client tests in main repo 16:28:52 xylan_kong, we run CLI tests on every commit to mistral 16:28:58 rakhmerov :-) 16:29:06 akuznetsova: yes 16:29:32 akuznetsova: are you sure you want to tell the story now? 16:29:34 :-) 16:29:54 xylan_kong, let me explain it later, I will send an email with our current situation and possible descision 16:30:06 akuznetsova: appreciate that 16:30:41 ok, let's save some time and end the meeting now 16:30:47 is that ok? 16:30:58 a lot of things to do :) 16:31:05 sure, nothing from my side 16:31:09 thanks! bye! 16:31:10 ok, sure 16:31:13 keep coding and reviewing 16:31:17 bye 16:31:18 alright! 16:31:18 bye! 16:31:20 #endmeeting