04:05:03 <rkmrHonjo> #startmeeting masakari
04:05:04 <openstack> Meeting started Tue Aug  1 04:05:03 2017 UTC and is due to finish in 60 minutes.  The chair is rkmrHonjo. Information about MeetBot at http://wiki.debian.org/MeetBot.
04:05:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
04:05:07 <openstack> The meeting name has been set to 'masakari'
04:05:17 <rkmrHonjo> OK, let's start.
04:05:39 <rkmrHonjo> #topic High priority items
04:05:51 <rkmrHonjo> Do you have any items to discuss?
04:06:19 <rkmrHonjo> ok, let's go to next topic.
04:06:30 <rkmrHonjo> #topic Bugs (stuck/critical)
04:07:50 <rkmrHonjo> Do you have any bugs(bug fixes) to discuss?
04:08:52 <tpatil_> # link : https://review.openstack.org/#/c/469029/
04:09:00 <tpatil_> #link: https://review.openstack.org/#/c/469029/
04:09:20 <tpatil_> Needs review
04:09:49 <rkmrHonjo> Sorry, I'll review it.
04:10:06 <Dinesh_Bhor> rkmrHonjo: thanks
04:10:16 <tpatil_> This patch fixes multiple LP bugs
04:10:52 <rkmrHonjo> Yeah. I think this is important.
04:12:20 <rkmrHonjo> Do you have any other items?
04:13:03 <rkmrHonjo> #link https://review.openstack.org/#/c/481509/
04:13:35 <rkmrHonjo> This patch was created by samP. This requires one more +2.
04:14:26 <tpatil_> I will review this patch today
04:14:34 <rkmrHonjo> tpatil: thank you!
04:16:33 <rkmrHonjo> Can we go to next topic?
04:17:18 <tpatil_> yes
04:17:46 <rkmrHonjo> #topic Discussion points
04:18:43 <rkmrHonjo> I skip "Application for become OpenStack oficial project". Because samP is not there.
04:19:07 <rkmrHonjo> "Install guide document"
04:19:35 <rkmrHonjo> Should we write installation documents for each distributions now? Ubuntu, Debian package is not prepared now.
04:20:25 <abhishekk> yes that's the reason I have kept workflow -1
04:20:40 <tpatil_> We will need to check how to submit patches in Ubuntu to publish Debian package
04:20:45 <abhishekk> on patch, https://review.openstack.org/486972
04:20:51 <abhishekk> #link https://review.openstack.org/486972
04:21:24 <rkmrHonjo> abshihekk: Can you split the patch? I afraid that public package will take long time.
04:21:57 <abhishekk> rkmrHonjo: I can remove installation guide for now
04:22:57 <rkmrHonjo> abhishekk: Can you leave common steps? e.g. Write configuration file
04:23:11 <tpatil_> Also, let's split patches for developer guide, architecture and operators guides
04:23:30 <abhishekk> ok
04:23:42 <rkmrHonjo> tpatil, abhishekk: thanks.
04:24:58 <rkmrHonjo> By the way, takahara wrote installation documents for masakari-monitors. I'm reviewing it.
04:25:02 <rkmrHonjo> #link https://review.openstack.org/#/c/489095/
04:26:17 <rkmrHonjo> I think that this document may be help to create devstack plugin of masakari-monitors.
04:27:25 <Dinesh_Bhor> rkmrHonjo: ok, thanks. I will check this
04:27:38 <rkmrHonjo> Dinesh: thanks!
04:27:40 <rkmrHonjo> OK, let's go to next item.
04:28:01 <rkmrHonjo> "Make nova "on_shared_storage" option configurable for evacuate API"
04:28:54 <rkmrHonjo> Oops, this was already merged.
04:28:57 <rkmrHonjo> #link https://review.openstack.org/#/c/483313/
04:29:08 <rkmrHonjo> I'll remove this item next week.
04:30:10 <rkmrHonjo> Next item is..."
04:30:10 <rkmrHonjo> Instance gets auto-confirmed(uses new flavor) if masakari evacuates an instance which was partially resized(resize-confirm is not performed)"
04:30:36 <rkmrHonjo> Are there any updates?
04:30:51 <abhishekk> No updates yet
04:31:42 <rkmrHonjo> OK. Next item is "recovery method customization"
04:33:11 <abhishekk> We will update the specs based on the recent PoC we have done
04:33:13 <tpatil_> Abhishek will update specs https://review.openstack.org/#/c/458023/ based on the POC done to register actions in mistral service
04:34:15 <tpatil_> There is no need to make any changes in mistral service to add new actions as it support RestFul api to register actions using admin credentials
04:34:38 <tpatil_> but there is one caveat, you need to restart mistral service in order to run those action in a workflow
04:35:13 <tpatil_> we are checking how we can auto-register these newly added actions in mistral without restarting the mistral service
04:35:37 <tpatil_> but for this to work, we may have to submit patch in mistral
04:36:04 <tpatil_> Abhishek: Have you already updated the specs?
04:36:57 <abhishekk> not yet
04:37:11 <tpatil_> abhishekk: Ok
04:37:37 <rkmrHonjo> tpatil: Should we restart mistral only once? or every time?
04:38:38 <Dinesh_Bhor> rkmrHonjo: Whenever you add new actions and want them to be registered in mistral you need to restart mistral services
04:39:00 <tpatil_> rkmrHonjo: you need to restart mistral service every time you register a new action, but in our case, we will register all required actions once, so you will need to restart mistral service only one time
04:39:23 <Dinesh_Bhor> yes
04:39:31 <rkmrHonjo> Dinesh_Bhor, tpatil: Thanks. I understood.
04:40:03 <rkmrHonjo> tpatil, abhishekk: When will you update?
04:41:02 <abhishekk> rkmrHonjo: in a day or two
04:41:14 <rkmrHonjo> abhishekk: Great. thank you.
04:42:07 <rkmrHonjo> OK. Can I go to next item?
04:42:52 <tpatil_> yes, please
04:42:57 <rkmrHonjo> "Auto compute node registration"
04:43:09 <rkmrHonjo> #link https://review.openstack.org/#/c/486483/
04:43:51 <rkmrHonjo> This feature automatically create host in specified segment. This will help operators.
04:44:06 <rkmrHonjo> Takahara submit spec, please review it.
04:44:17 <rkmrHonjo> s/submit/submitted/
04:44:36 <tpatil_> In the notification request, there is no information about failureover_segment, it contains host name
04:44:56 <rkmrHonjo> tpatil: Right.
04:45:00 <tpatil_> Are you planning to add a failover_segment in the notification request?
04:45:45 <rkmrHonjo> tpatil: No. This feature add failover_segment id to masakari-monitors configuration file. And it will be used for host registration.
04:46:00 <rkmrHonjo> This feature doesn't change notification API.
04:46:27 <tpatil_> Ok, so masakari-monitors will call Add host Restful API to add this host in a particular failover_segment, correct?
04:46:42 <rkmrHonjo> tpatil: correct.
04:47:17 <tpatil_> rkmrHonjo: Make sense
04:48:01 <rkmrHonjo> tpatil: thanks.
04:48:35 <rkmrHonjo> By the way, implementation was already submitted.
04:48:37 <rkmrHonjo> #link https://review.openstack.org/#/c/486484/
04:49:10 <rkmrHonjo> OK, let's go to next item.
04:49:29 <rkmrHonjo> Next item is..."masakari-manage db purge": support for purging notification records"
04:50:38 <tpatil_> Specs are approved, implementation patch is up for review
04:50:59 <tpatil_> #link: https://review.openstack.org/#/c/487430/
04:51:56 <rkmrHonjo> Dinesh_Bhor: I wrote some comments for that patch. Please check it.
04:52:37 <Dinesh_Bhor> rkmrHonjo: yes, I will, thanks
04:53:41 <rkmrHonjo> OK. Any other items?
04:54:54 <Dinesh_Bhor> To enable Openstack proposal bot for masakari project, first we need to make all masakari projects python 3.5 compatible: https://git.openstack.org/cgit/openstack/requirements/tree/README.rst#n265.
04:55:21 <Dinesh_Bhor> So for this I have submitted below patches in python-masakariclient and masakari-monitors: https://review.openstack.org/#/c/489118/, https://review.openstack.org/#/c/489117/
04:55:39 <tpatil_> Dinesh_Bhor: I will review these patches
04:55:47 <rkmrHonjo> Dinesh_Bhor: thanks. I'll review these, too.
04:56:14 <Dinesh_Bhor> tpatil_, rkmrHonjo: thanks you
04:56:51 <rkmrHonjo> Let's go to AOB.
04:56:58 <rkmrHonjo> #topic AOB
04:57:15 <rkmrHonjo> Do you have items to discuss?
04:57:29 <tpatil_> Do you think adding a horizon plugin for masakari project will be useful for operator?
04:57:51 <tpatil_> In this plugin, it should be possible to add entities like failover segment, host etc.
04:58:17 <rkmrHonjo> I think that will be useful.
04:58:22 <Dinesh_Bhor> and check notification statuses
04:58:32 <tpatil_> but most importantly, we should display the failover segment in graphical representation which will help operator to know if any of the hosts is in failed state
04:59:49 <tpatil_> if it's in failed state, on click on that node, it will show all information about the current status of the notification to the operator
05:00:04 <rkmrHonjo> By the way...Some operators said that finding host is hard when they forgot relationships.
05:00:13 <rkmrHonjo> oops, time is over.
05:00:52 <rkmrHonjo> If you want to continue discussion, please talk it in ML or openstack-masakari channel.
05:01:00 <rkmrHonjo> thank you for all...
05:01:02 <tpatil_> ok
05:01:28 <rkmrHonjo> #endmeeting