04:01:00 #startmeeting masakari 04:01:01 Meeting started Tue Dec 20 04:01:00 2016 UTC and is due to finish in 60 minutes. The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot. 04:01:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 04:01:04 The meeting name has been set to 'masakari' 04:01:09 hi all 04:01:19 o/ 04:01:20 samP: hi 04:01:22 hi 04:01:32 hi 04:01:46 #topic Critical bugs 04:01:57 any bus to discuss? 04:02:05 sorry, bugs 04:02:41 if no then, we can jump in to next topic 04:03:43 if you have any, then we can discuss them later in this meeting 04:03:48 #topic Discussion points 04:04:09 First, pypi packaging 04:04:48 when we create the repo, I didn't add pypi jobs. so, there are no pypi packages for masakari 04:05:05 Today I manually add v2.0.1 to pypi 04:05:42 #link https://pypi.python.org/pypi/masakari/2.0.1.dev19 04:06:08 I can do same for masakari-monitors and python-masakari-client 04:06:54 samP: Please do it. 04:06:56 I think we should add pypi jobs for gate to automatically update the pypi 04:07:10 Hi 04:07:13 hi 04:07:33 Having problem connecting from my mac, so connected from windows 04:08:04 tpatil_: ok, no problem. you are live now.. 04:08:13 Yes ,finally 04:08:53 we are discussing about adding pypi packages for masakari/monitors/client 04:09:06 ok 04:09:49 I will update the project config for add pypi jobs for masakari/monitors/client. 04:10:05 however, monitors would be bit tricky. 04:10:47 rkmrhj: how are we doing with adding setup script for shell scripts in monitors? 04:12:31 anyway, I will work with masakari and client first. 04:12:52 #action samP add pypi jobs to project config of masakari and client and monitors 04:13:25 samP: Thanks. 04:13:28 next, I would like to discuss about documentation 04:14:35 The reason is, some ppl are start to try masakari and Im flooded with emils 04:15:01 what kind of documentation are you expecting to start with? 04:15:04 apis? 04:15:39 In first step, how to install and then APIs 04:16:10 I think we do have japanese doc for how to install and configure 04:17:13 please forward all Japanese documentation to us and we will try to translate in English. 04:17:20 samP: https://github.com/openstack/masakari/tree/master/devstack, here it is mentioned how you can install masakari 04:18:01 abhishekk: thanks 04:19:02 abhishekk: we need to document this from how setup from the start, start with creating pacemaker cluster for compute nodes 04:19:32 samP: ok, got it 04:20:15 tpatil_: I will try to translate this to some level. could you please brush it up? 04:20:26 samP: Sure 04:20:38 and the next question is, where we can host this? 04:21:00 since we can not use openstack.doc, one option is to use http://pythonhosted.org/masakari 04:21:29 or we can host it in git with masakari source 04:22:03 samP: I think git is fine to start with 04:23:19 tpatil_: sure, then I will push the initial draft 04:23:54 Does the document contains installing steps of masakari-monitors? 04:25:01 rkmrhj: good question, I am thinking to put them all in one document. 04:25:24 In general, it should include all services needed to run masakari in multi node environment. 04:25:26 rkmrhj: any suggestions? 04:26:06 tpatil_: sure 04:26:53 sampP: Sorry, no suggestions. I planned to write installing steps of masakari-monitors after implementing blueprints. But my plan doesn't contain masakari. 04:26:57 abhishekk: thanks for the BP.. 04:27:21 samP: WC 04:28:07 rkmrhj: That would be fine. I will write the basic steps to install them. you can update it. 04:29:02 samP: OK, sure. 04:29:07 #action samP add "how to install masakari" docs 04:29:21 OK, I will add them soon 04:29:46 next topic is sepc repo 04:29:53 #link https://review.openstack.org/#/c/412376/ 04:31:14 its under review now, hopefully we will get it soon. Then I will cookiecut it and will be ready to go. 04:31:18 After this patch is merged, we will start pushing specs for all action items in last meeting 04:31:57 all action items discussed in last meeting 04:31:58 tpatil_: user, but wait for cookicut. 04:32:24 tpatil_: not "user", sure 04:32:54 you mean once this project is available in github, correct? 04:33:44 tpatil_: after it available in github, first patch would be the cookicut, which make the structure for the repo 04:34:06 samP: Ok, I got it 04:35:03 tpatil_: I will puch this patch wright after repo available on github 04:35:49 ok 04:36:15 OK then, that was all the items I added to agenda. Any thing else to discuss? 04:37:03 Nothing from my side for now 04:37:17 samP: Please check the blueprint, once it is approved we ill submit patches against it 04:37:18 tpatil_: thanks 04:37:37 abhishekk: sure, thank you 04:37:48 thanks 04:38:10 #topic AOB 04:38:19 bye 04:38:23 wait 04:38:37 oh, sorry. 04:38:46 I am gonna take early vac from 12/26 04:39:50 Ok, are you available for the next meeting? 04:40:05 so, not gonna be able to host next IRC till 1/10 04:40:44 Ok 04:41:05 Sure. 04:41:08 because its new year, I think most of us are not available on 1/3 04:42:32 Let's keep in touch for important matter on mailing list till then 04:42:32 any volunteer to host the meeting on 12/27? or we can skip 12/27 and 1/3 04:43:59 tpatil_: sure 04:44:48 IMO, we can skip meeting on 12/27 and 1/3 and as said above we can use mailing list to discuss on important agenda 04:44:49 I agree to skip 12/27 and 1/3. 04:44:59 OK, lets skip the IRC for 12/27 and 1/3, however post to ML for any important matters. 04:45:21 tpatil_: rkmrhj thanks 04:45:45 Is there any other things to discuss? 04:46:14 if no then, lest finish... thank you all 04:46:27 Not discuss, but I have a request. Please review https://review.openstack.org/#/c/397064/ 04:47:16 rkmrhj: I will check this patch soon 04:47:25 #action Review https://review.openstack.org/#/c/397064 04:47:31 tpatil_: Thanks a lot! 04:47:36 rkmrhj: me too will check 04:48:40 samP: tanks, too. 04:48:49 ok then, bye all "Merry Christmas And Happy New Year" 04:48:57 NG: tanks Correct: thanks 04:49:13 samP: same to you, thanks to all 04:49:22 Happy New year to everyone in advance 04:49:52 #endmeeting