04:00:01 #startmeeting masakari 04:00:02 Meeting started Tue Oct 17 04:00:01 2017 UTC and is due to finish in 60 minutes. The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot. 04:00:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 04:00:05 The meeting name has been set to 'masakari' 04:00:12 hi all for masakari 04:00:13 o/ 04:00:17 Hi 04:00:22 hi all 04:00:37 Hi 04:00:49 let's start 04:01:15 #info Got room for project onboarding in AUS summit 04:01:46 That's good news 04:01:51 please let me know if you are available to speak on this session 04:02:18 hi 04:02:23 let's decide what sessions to be held 04:02:30 It was in hurry, so I ask the session with me as a speaker 04:03:05 I cloud ask to add other as speakers 04:03:29 tpatil: sure, lets talk about this in ML. 04:03:43 samP: Ok 04:03:58 #topic critical bugs 04:04:17 #link https://bugs.launchpad.net/masakari/+bug/1721742 04:04:18 Launchpad bug 1721742 in masakari "Masakari will fail to recovery instances on failure host if instance's task_state is not none" [Undecided,New] - Assigned to takahara.kengo (takahara.kengo) 04:04:59 I heard that Takahara is creating a patch for it. 04:05:00 Kengo has confirmed that reset set the VM_STATE to error and tast_state to none 04:05:10 rkmrHonjo: thanks 04:05:29 sorry for interrupting. 04:05:35 rkmrHonjo: np 04:05:53 rkmrHonjo: you may proceed with original proposal 04:06:02 Any other bugs? 04:06:54 If any, please bring them on AOB at the end of the meeting 04:07:18 #topic Discussion Points 04:07:33 (1) Horizon Plugin (Dashboard) 04:07:47 samP: Need your approval 04:08:04 I read the BP, LGTM 04:08:21 are you plan to implement all at once? 04:09:20 Yes, Niraj has already completed POC, we will manage to implement failover segment and hosts in Queens Release 04:09:34 Yes 04:10:11 If something remains, can by postponed to the next release 04:10:14 tpatil: niraj_singh: great, thanks. Approved 04:10:23 tpatil: sure 04:10:38 samP: Thanks 04:10:39 we might need some help from you to get the new repo for masakari-dashboard 04:10:50 tpatil: sure 04:11:28 tpatil: would you like me to create it? 04:11:30 samP: we will ask for your help on ML or IRC 04:11:37 tpatil: sure, np 04:12:28 Any idea, how many patches we need to submit to create a new repo? 04:12:28 let me know when you need me 04:12:44 tpatil: just one patch to project config 04:12:54 samP: OK 04:13:42 Once the blueprint is approved, we will submit a patch to project config 04:13:50 then infra team will create the repo. Then we have to init it with cookie cutter and start to fill it with code 04:14:41 samP: Ok, Thanks 04:15:17 samP: You have approved the blueprint, Thanks 04:15:29 #link Project creates guide https://docs.openstack.org/infra/manual/creators.html 04:15:39 tpatil: ^^ will help you 04:15:59 samP: Ok, We will refer this guide 04:16:07 tpatil: thanks 04:16:19 (2) Install guide document (in progress) 04:16:25 what should be the repo name? 04:16:35 masakari-dashboard? 04:16:39 tpatil: good question 04:17:58 According to the convention like "mistral-dashboard", "congress-dashboard" I think "masakari-dashboard" seems good to me. 04:18:04 most people named as [project name]-dashboard 04:18:18 Dinesh_Bhor: correct 04:18:44 samP: we will mention this as a project name 04:19:10 you may find this info on openstack-infra/project-config/gerrit/projects.yaml 04:19:16 secondly, are we going to manage all tasks of dashboard in the same masakari Launchpad project? 04:20:20 tpatil: I prefer to have it separate, but what would you think? 04:20:50 normally, one project one bug tracker 04:21:37 samP: I don't see any problems if it's managed in a single project 04:22:15 samP: do you see any problems from release management perspective? 04:23:08 tpatil: Not from release management. However, let me look around and decide 04:23:48 If you some one want to get the packages from LP, then it would be a problem 04:23:58 samP: Sure, In the mean time ,we will go through the guide 04:24:26 tpatil: sure, I will put more details in ML for this 04:24:49 samP: Ok, Thanks 04:24:59 tpatil: thanks 04:25:30 Any other questions on this^^? 04:25:46 samP: I'm good for now 04:26:03 tpatil: thanks, ping me if you need smt 04:26:08 (2) Install guide document (in progress) 04:26:45 I will review these docs today. In the meantime please update the schema 04:26:55 I will finish this in current week 04:27:09 abhishekk: sure, that would be great 04:27:15 abhishekk: thanks 04:27:21 samP: NP 04:27:25 Sorry, monitor document is not updated yet. 04:28:02 But, I and Takahara try it. 04:28:07 rkmrHonjo: np, I only review the details in the doc. you may update it any time 04:28:16 samP: thanks. 04:28:44 rkmrHonjo: abhishekk: thanks again for doc work 04:29:16 (3) recovery method customization 04:29:29 I think spec update in progress now.. 04:29:51 yes 04:30:03 Dinesh_Bhor: great, thanks 04:30:03 samP: correct, we are planning to make each notification type configurable 04:30:40 samP: for example, host failure, you can use mistral workflow driver and for instance failure it should be possible to use the existing task flow driver 04:31:16 tpatil: for each notification type, user may configure different work flow driver 04:31:37 samP: correct 04:31:43 And this will be a config option, right? 04:31:48 yes 04:32:15 excellent 04:32:27 samP: correct, adding all these logic may take more time though 04:32:47 tpatil: understand. 04:32:53 as in the current code, it can only load one driver for all notification types 04:33:49 tpatil: correct, we need to start form there, 04:34:16 allow load multiple drivers according to config values 04:34:18 samP: We will upload specs in couple of days 04:34:28 samP: Sure 04:34:29 tpatil: sure 04:35:26 tpatil: Dinesh_Bhor: abhishekk: Thank you for the proposal and all the work 04:36:09 (4) Find hosts without specifying segments 04:36:46 #link sepc and code https://review.openstack.org/#/q/topic:bp/find-segment-by-host+(status:open+OR+status:merged) 04:37:09 I put a comment on the spec, about creating a another command for this 04:37:28 I prefer to add this feature in to host show command 04:37:50 samP: Thanks. I and Takahara check it and reply. 04:38:23 rkmrHonjo: sure, I put -1 to patch, just to hold it till we fix the spec. 04:38:39 samP: ok. 04:38:59 rkmrHonjo: please consider my comment and let me know what would you think 04:39:15 samP: Sure. In my understanding, this spec says that new sub-command requires only host id or name. 04:39:35 > Create a subcommand in masakariclient to find segment by specifying host name or id. 04:39:41 o/ 04:39:46 rkmrHonjo: true 04:39:50 chason: hi 04:40:19 samP: But, your comment said that "In your current proposal, if user wants to execute segment_host_show, user need to input host name/id and segment name/id.". 04:41:01 samP: I think this comment is based on misunderstanding. Do you think about it? 04:41:27 If this new sub-command doesn't exist, user should run host-list for each segments to know the relation of host and segment. 04:41:28 rkmrHonjo: even if you implement this, user still need to input host name and segment name to host show. 04:42:03 rkmrHonjo: My proposal is to, include this feature into host show command 04:42:17 samP: Ah...I understand your purpose. 04:42:38 rkmrHonjo: sorry, my comment in the spec is not bit messy 04:42:47 samP: OK, I and Takahara rethink about your idea. 04:43:18 rkmrHonjo: sure, if you need more info or help, please let me know 04:43:30 samP: thanks. 04:43:32 samP: So what you are asking is to make failover segment id or name optional in case of host show command, correct? 04:43:56 tpatil: correct 04:44:54 samP: Ok, it makes sense to me 04:45:18 with this feature, we can make segment id/name optional for host show command, and remove in future 04:45:45 samP: I got it. 04:46:29 (5) Queens Work items 04:46:46 I think no update on this. right? 04:46:58 Yes, from my side. 04:46:59 ssl item is complete 04:47:10 tpatil: thanks 04:47:23 rkmrHonjo: thanks 04:47:26 samP: I will make this item as completed in the etherpad 04:47:32 s/make/mark 04:47:51 tpatil: Thanks, that would be nice 04:48:08 (6) BMHA 04:48:20 no update on Masakari side 04:48:30 nova spec in review 04:49:00 #link nova spec for BM node migrate/resize https://review.openstack.org/#/c/449155/ 04:49:36 once it fixed, lets reconsider on this. 04:49:47 #topic AOB 04:49:59 chason: Hi 04:50:09 welcome chason 04:50:10 chason: welcome to Masakari 04:50:37 chason: would you like to introduce your self? 04:51:04 in the meantime, anyone have AOB items? 04:51:10 Yes 04:51:24 tpatil: go ahead 04:51:31 Enable-openstack-proposal-bot and ha-enabled-config-options blueprints are already released in Pike. 04:51:36 Yeah 04:52:11 # link : https://blueprints.launchpad.net/masakari/+spec/enable-openstack-proposal-bot 04:52:25 #link : https://blueprints.launchpad.net/masakari/+spec/enable-openstack-proposal-bot 04:53:05 We will update the status of these blueprints from our side. sam 04:53:22 I am a core of openstack-manuals and have an interest on Masakari project. I can work on our project's documentation. :D 04:53:28 tpatil: sure, it seems some problem with bot 04:53:43 samP: Thanks 04:54:16 chason: That is great. 04:54:20 chason: That will be great, We need documentation experts in our project 04:54:45 chason: Thank you for attending! 04:55:04 currently we are creating some docs, 04:55:10 #link https://review.openstack.org/#/q/topic:docs/operators 04:55:20 #link https://review.openstack.org/#/q/topic:operators_guide 04:55:43 Aha, looking forward to working together with you guys. :P 04:55:59 chason: as we are now official, we are modifying above patches to use openstackdocs theme 04:56:06 samP checking 04:56:21 chason: I would really appreciate it if you could review those doc and give us some feed back 04:56:52 abhishekk Oh, I can do something for it. 04:57:06 chason: if you need any help on masakari, you may find us in #openstack-masakari or ML 04:57:08 chason: I will let you know 04:57:27 chason: Thanks you in advance 04:57:35 chason: right now it will be great if you help in review :D 04:57:45 chason: as I have already started working on it :D 04:58:02 tpatil: I will update the status in LP BPs 04:58:04 samP It's OK. 04:58:12 I think we are running out of time here 04:58:17 samP: Thanks 04:58:44 For further discussions, please use #openstack-masakari or ML 04:59:00 let's finish this meeting 04:59:01 thank you 04:59:10 Thank you all....... 04:59:12 thanks 04:59:16 bye 04:59:22 Thank you all 04:59:27 #endmeeting