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