09:23:15 #startmeeting check-in_20170131 09:23:15 Meeting started Tue Jan 31 09:23:15 2017 UTC. The chair is brainfunked. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:23:15 Useful Commands: #action #agreed #halp #info #idea #link #topic. 09:23:15 The meeting name has been set to 'check-in_20170131' 09:23:39 brainfunked: hi we have new blocker for ui https://github.com/Tendrl/dashboard/issues/117 09:24:57 mkudlej, please provide more details 09:25:56 anyway, looks like it's an API doc issue 09:26:05 I'll get to it during the check-in 09:26:19 ltrilety: ^ 09:26:57 #topic team updates 09:27:04 anmol, what's your status? 09:27:14 I was on PTO yesterday(30 Jan) 09:27:14 Today: 09:27:14 1. Reviewed https://github.com/Tendrl/commons/pull/134, https://github.com/Tendrl/node-agent/pull/178/ 09:27:14 2. Reviewing https://github.com/Tendrl/specifications/pull/94/ 09:27:15 3. Will start on: 09:27:15 * Incoporating namespace changes into alerting 09:27:17 * Logging framework related changes to alerting including the alert proporgation related stuff impacting on this. 09:27:20 Blocked on: 09:27:24 1. Incoporated comments from @shtripat and @r0h4n on: 09:27:26 * https://github.com/Tendrl/commons/pull/140 -- Flow fixes 09:27:28 * https://github.com/Tendrl/performance-monitoring/pull/35 -- object tree, flows and namespaces changes 09:27:31 * https://github.com/Tendrl/performance-monitoring/pull/33 -- object tree, flows and namespaces changes 09:27:34 * https://github.com/Tendrl/performance-monitoring/pull/34 -- Performance monitoring docs 09:27:36 Awaiting further reviews. 09:27:38 2. I would like to request @anivargi and @brainfunked to review https://github.com/Tendrl/specifications/pull/124 which is spec to detail alerting apis 09:27:41 requirement. This is required for tendrl/api to expose apis for alerting related configuration and others. 09:28:01 that's it from my end 09:30:20 #action noop to review and contribute to anmol's alerting API specification to make the alerting API is part of the core API: https://github.com/Tendrl/specifications/issues/123 09:33:28 anmol, did you push the changes requested by rohan? 09:33:44 brainfunked, yes the PR is in latest state 09:33:51 and was updated on Saturday 09:33:59 with comments incoporated 09:34:02 ok 09:34:42 #action rohan to review anmol's PRs regarding namespace change fixes for the performance monitoring codebase: https://github.com/Tendrl/performance-monitoring/pull/35 https://github.com/Tendrl/performance-monitoring/pull/33 https://github.com/Tendrl/performance-monitoring/pull/34 09:35:53 also currently the process of invoking flow to configure collectd is happening from code as it happens w/o user intervention 09:36:04 we might need an api to do the same 09:36:09 exposed by tendrl/api 09:36:18 brainfunked, ^^ 09:37:00 so by "happening within code" I mean job loaded to etcd by performance monitoring on any newly managed nodes or already managed nodes 09:37:05 ok, let's take that discussion offline, post check-in 09:37:08 ok 09:38:25 #action anmol to work on the alerting module to incorporate the namespace changes and changes based on the updates to the logging specification https://github.com/Tendrl/specifications/pull/94/ 09:38:49 gowtham, you were working on the logging stuff, what's your status? 09:39:28 brainfunked, i am now modifying all log statements in ceph and anmol_s is modifying common 09:39:52 gowtham, are you documenting each and every message in a single place as I'd asked? 09:39:56 brainfunked, anmol gave some comment on logging patch i am correcting that also 09:40:22 brainfunked, yes i am documenting in google sheet 09:41:35 brainfunked, once i completed for ceph i will share that sheet with all team members 09:41:37 gowtham, ok, once your changes are in, we need to move the messages to the documentation wiki 09:41:53 brainfunked, ok 09:43:23 brainfunked, anmol pu some comment on github about alert logging please see and give your suggestion 09:44:31 *put 09:44:40 gowtham, why do none of your pull requests ever link back to the original specification issue 09:45:18 brainfunked, spec link is there 09:45:30 brainfunked, i will add issue link also 09:45:54 brainfunked, apologies for that i will add it 09:46:05 gowtham, I don't see a link on https://github.com/Tendrl/node-agent/pull/178#issuecomment-275651442 09:47:09 brainfunked, tendrl-spec: logging_implementation is there, i missed issue link only 09:47:17 I'm aware 09:47:17 brainfunked, i will add it now 09:47:20 I'm talking about the link 09:47:51 gowtham, I'm creating a new branch against which your changes have to come in 09:48:01 brainfunked, ok 09:48:06 gowtham, it may be necessary to close the existing pull requests and send them against a new branch again 09:49:01 brainfunked, ok 09:51:53 #undo 09:51:53 Removing item from minutes: ACTION by brainfunked at 09:38:25 : anmol to work on the alerting module to incorporate the namespace changes and changes based on the updates to the logging specification https://github.com/Tendrl/specifications/pull/94/ 09:52:01 #chair nishanth 09:52:01 Current chairs: brainfunked nishanth 09:52:11 #action rohan to review anmol's PRs regarding namespace change fixes for the performance monitoring codebase: https://github.com/Tendrl/performance-monitoring/pull/35 https://github.com/Tendrl/performance-monitoring/pull/33 https://github.com/Tendrl/performance-monitoring/pull/34 09:52:22 #action gowtham and anmol are working on the log messages based on the logging specification https://github.com/Tendrl/specifications/issues/28 09:52:41 ndarshan, status on the gdeploy wrapper? 09:53:32 * Spent some time testing the node_agent build. 09:53:33 * Started working on: https://github.com/Tendrl/specifications/issues/49 (wrapper for gdeploy) 09:53:33 spent time going throught gdeploy docs, gdeploy-tendrl integration doc. Will start coding today 09:54:06 ndarshan, did you confirm the validity of the document with Sachs? 09:54:17 ndarshan, btw, please do put the contents of the doc as part of the specification 09:54:54 brainfunked, I requested him to review the doc. He said he will do it 09:55:14 ndarshan, ok, would be good to have him involved in the specification review 09:55:22 brainfunked, sure 09:55:35 ndarshan, just put the contents of the doc in the specification PR and tag him for a review there 09:55:52 okay, will do that 09:56:33 #action ndarshan to put the gdeploy flow details in the gluster provisioning wrapper specification https://github.com/Tendrl/specifications/issues/49 and start working on it 09:56:55 ndarshan, btw, he had made updates to the logging for us, but I wasn't able to get the details from him 09:57:18 please ask him to provide any details or a demo to you so that the wrapper can parse the logs from gdeploy 09:57:41 the logs will lead to operation updates 09:57:57 brainfunked, okay 09:58:24 #action nishanth is working on pullin the from-packages installation documentation to the documentation wiki 09:59:00 nishanth, will you be working on the ceph-installer wrapper post the documentation? 09:59:15 brainfunked, yes 09:59:21 I will start on that 09:59:39 ack, thanks 10:00:07 #action nishanth will be working on the ceph provisioning wrapper https://github.com/Tendrl/specifications/issues/48 10:02:42 #action noop to push the finalised API documentation for the 1.2 build. This should address (at least partly) the issue raised by ltrilety at https://github.com/Tendrl/dashboard/issues/117. 10:04:02 #action noop will be working on authentication https://github.com/Tendrl/specifications/issues/128 and the implementation of the alerting API as part of the core API https://github.com/Tendrl/specifications/issues/123 10:04:42 #action Shu6h3ndu is working on some fixes to the ceph cluster detection: https://github.com/Tendrl/node-agent/pull/196/ 10:04:52 Shu6h3ndu, any update on the Ceph CRUD operations? 10:05:22 brainfunked, I have to start on spec for the same 10:05:29 ack 10:05:32 brainfunked, no response the issue though from gregory 10:06:20 Shu6h3ndu, ack, I'll look towards escalating it 10:07:04 #action Shu6h3ndu is working on the ceph crud flows https://github.com/Tendrl/specifications/issues/126 and has raised some questions regarding calamari, which need to be responded to by Gregory Meno 10:07:12 t1m1, your status? 10:07:47 Fixed Service start failure due to environment variable issue 10:07:47 https://github.com/Tendrl/node-agent/issues/185 10:07:47 https://github.com/Tendrl/ceph-integration/issues/98 10:07:47 https://github.com/Tendrl/gluster-integration/issues/131 10:07:48 Fixed python-six dependency issue: 10:07:48 https://github.com/Tendrl/commons/issues/146 10:07:50 Jenkins is currently configured to do a "sed" command. Working on enhancing jenkins CI 10:07:54 Working on enabling automatic build, nightly build for performance-monitoring and node-monitoring 10:07:56 Will update rpm spec file once performance-monitoring patches are merged 10:09:23 t1m1, which jenkins is this? 10:10:01 http://10.70.42.16:8080/ 10:10:10 for our tendrl projects 10:10:57 Currently tendrl-api, ceph, gluster integration, dashboard, node-agent are configured 10:12:42 this jenkin server will initiate fedora copr to start the build on nightly and every patch merge 10:12:49 ok 10:12:56 will this be a permanent setup 10:13:00 yes 10:13:24 i will also add api support for this later 10:13:26 ok, would it not be possible to migrate to centos ci once it's working? 10:13:51 sure, i will check it out 10:14:18 t1m1: cold you please talk with dahorak about CentOS CI, please? 10:14:20 brainfunked, t1m1, it should go there. We cannot really maintain the server infra 10:14:38 ack 10:15:07 mkudlej, sure, i will do it! 10:15:10 dahorak: ^^ 10:15:27 #action t1m1 is working on build automation on an internal ci instance, he'll be communicating with dahorak to move the setup to centos ci 10:15:53 #topic UI updates 10:16:07 friday and monday i spent time with verification of ui code with new api response format and updated version as 1.2 in spec files 10:16:07 today looking into all CRUD operation for pool/volume etc, and making note of, what are items pending and than will take up now if anything is pending. 10:16:08 mkudlej, currently kendreyer is helping me reviewing our jenkins setup 10:17:07 #action ankush will be working on the dahsboard UI. He'll be specifying the data end points required for the dashboard and communicating them to anmol. 10:17:56 kaverma, neha and you were supposed to get back to me yesterday evening regarding the feasibility of working on both the crud and the create cluster flows simultaneously. I haven't heard anything yet. 10:20:03 brainfunked, yesterday i was spent time for verifying the api stuff with current code .. because i was on sick leave on last friday ...and i am making of note for all pending items for CRUD operation and will send mail or sync up with you 10:20:20 ok 10:21:23 #action kaverma and neha to work on the crud and create cluster flows 10:21:29 #topic testing updates 10:21:46 mkudlej, dahorak, ltrilety, fbalak, any updates you'd like to share? 10:22:05 #action fbalak Testing new packages. 10:22:06 #action fbalak Working on https://github.com/Tendrl/usmqe-tests/issues/20 10:22:08 #action fbalak Status: good 10:22:26 brainfunked: I work on tasks unrelated to Tendrl 10:23:00 #info fbalak is testing the new packages and working on the import cluster tests https://github.com/Tendrl/usmqe-tests/issues/20 10:23:38 #info nishanth and noopq are working on updating the documentation 10:24:21 I am working on https://github.com/Tendrl/usmqe-tests/issues/12, for now I am blocked by https://github.com/Tendrl/dashboard/issues/117 10:26:51 brainfunked: is there any decision about rules for building API? like for example REST verbs 10:27:14 brainfunked: https://github.com/Tendrl/documentation/issues/70 10:27:40 mkudlej, yes, noopq and I have discussed this and we want to use the verbs correctly, but the action oriented APIs don't lend themselves well to it 10:27:49 RESTful APi structure is much better suited to this 10:28:08 in any case, there's some work to be done on the flows to enable the verbs correctly 10:28:23 the flows need to be tagged with the type of action, which will lead to the appropriate verb being used 10:28:27 brainfunked: great, I'm looking for pulls requests 10:28:47 mkudlej, I'll highlight in subsequent check-ins when this is picked up for implementation 10:29:43 ltrilety, I've made a comment on the dashboard issue, need your response 10:30:14 #action ltrilety is working on gluster import tests https://github.com/Tendrl/usmqe-tests/issues/12 10:30:59 #info ltrilety is blocked by an API response change raised in an issue https://github.com/Tendrl/usmqe-tests/issues/12. brainfunked has requested more info on the issue, while noopq is working on pushing the updated API documentation. 10:31:06 #endmeeting