09:03:16 <nishanth> #startmeeting check-in_20170201
09:03:17 <zodbot> Meeting started Wed Feb  1 09:03:16 2017 UTC.  The chair is nishanth. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:03:17 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
09:03:17 <zodbot> The meeting name has been set to 'check-in_20170201'
09:03:45 <nishanth> #topic team updates
09:04:08 <nishanth> anmol, can you update on the monitoring please?
09:04:15 <anmol> nishanth, sure
09:04:17 <anmol> Following patches got merged yesterday:
09:04:17 <anmol> * https://github.com/Tendrl/commons/pull/140 -- Flow fixes
09:04:17 <anmol> * https://github.com/Tendrl/performance-monitoring/pull/35 -- object tree, flows and namespaces changes
09:04:17 <anmol> * https://github.com/Tendrl/performance-monitoring/pull/33 -- object tree, flows and namespaces changes
09:04:18 <anmol> * https://github.com/Tendrl/performance-monitoring/pull/34 -- Performance monitoring docs
09:04:20 <anmol> * https://github.com/Tendrl/commons/pull/148 -- Add null check for sds sync thread which can be optional
09:04:25 <anmol> Today:
09:04:27 <anmol> 1. Continuing work on:
09:04:29 <anmol> * Incoporating namespace changes into alerting
09:04:31 <anmol> 2. Once done with [1] will start on:
09:04:33 <anmol> * Logging framework related changes to alerting including the alert proporgation related stuff impacting on this.
09:04:36 <anmol> Waiting for:
09:04:38 <anmol> 1. 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:04:41 <anmol> requirement. This is required for tendrl/api to expose apis for alerting related configuration and others.
09:04:44 <anmol> that's it from my end
09:05:07 <nishanth> anmo, all the monitoring related patches are in?
09:05:15 <nishanth> anmol^^
09:05:23 <anmol> nishanth, yes all performance-monitoring patches are in
09:06:03 <anmol> nishanth, i.e, all patches that give monitoring datapoints for host listing are in
09:06:21 <nishanth> anmol, what about the packaging?
09:06:41 <nishanth> are all the packages are built on copr?
09:06:46 <nishanth> anmol^^
09:06:50 <anmol> nishanth, I'll sync up with t1m1 on
09:06:53 <anmol> that
09:07:14 <anmol> t1m1, ^^
09:07:20 <t1m1> anmol, ok
09:07:23 <nishanth> t1m1, what is status of rpms for monitoring rpms?
09:08:20 <t1m1> i have to update the rpm spec
09:08:40 <anmol> nishanth, also although the implementation prs are in one spec is not yet merged https://github.com/Tendrl/specifications/pull/81 it is approved although
09:08:58 <t1m1> anmol, whether all the patches are merged now?
09:09:09 <anmol> t1m1, yes
09:09:24 <t1m1> anmol, ok
09:09:30 <nishanth> t1m1, you have to work with anmol complete that today
09:09:39 <t1m1> nishanth, ok
09:09:53 <anmol> nishanth, I think api needs to sync again
09:10:06 <anmol> nishanth, I had sent a mail to noop
09:10:08 <nishanth> anmol, once that is done please work with k4n0 and tag your git and release it
09:10:22 <anmol> nishanth, I am waiting for anoops response
09:10:35 <nishanth> anmol. what is the issue with APIs?
09:11:26 <anmol> nishanth, post object changes, I wanted api to reverify some of the config related stuff because api depends on config in etcd to determine performance monitoring api details
09:11:40 <anmol> nishanth, earlier we used to dump it as json
09:11:58 <anmol> nishanth, but now its an object so the way its stored in etcd is changed
09:12:13 <nishanth> anmol, does it require any changes in api?
09:12:42 <anmol> nishanth, yes the way api parses config for performance-monitoring api server details changes
09:13:00 <nishanth> #accept all the monitoring related patches are reviewed and merged
09:13:25 <nishanth> anmol ,please work with noopq and close it today
09:13:34 <anmol> nishanth, ok
09:14:15 <anmol> nishanth, there's 1 more thing I wanted to share
09:14:21 <nishanth> #action, anmol and t1m1 to work together and complete the packaging of monitoring rpms today
09:14:37 <anmol> nishanth, as we had seen before in skyring, collectd takes some time to put out all metrics
09:14:54 <anmol> nishanth, and hence it takes some time for all metrics to be available in graphite
09:15:12 <anmol> nishanth, should I create an issue for this and we call it a known issue?
09:15:14 <nishanth> #action anmol to co-ordinate with k4n0 to tag and release monitoring modules
09:16:03 <anmol> nishanth, but I have anyway already taken care of the steps that we took last time(updated at field)
09:16:14 <anmol> nishanth, probably ui needs to be made aware of it
09:16:29 <nishanth> #action anmol to work with noopq to sort out any changes required in api with respect to the latest changes in monitoring
09:17:51 <nishanth> anmol, we need to find a solution to this problem. Last time we beaten up on this. Now we have time and lokk forward to fix it
09:18:02 <anmol> nishanth, ok
09:18:49 <nishanth> anmol, is there any progress on the logging stuff you are supposed to do?
09:19:24 <anmol> nishanth, I reviewed gowtham's prs and asked for input on his common's pr
09:19:33 <anmol> nishanth, input from everyone
09:19:39 <nishanth> ok
09:19:57 <anmol> also I am working on incoporating namespace changes in alerting module
09:20:17 <anmol> so only once that's done I'll be able to accomdate new changes to alerting module
09:20:25 <nishanth> anmol, did ankush provided the data points required for dashboard?
09:20:27 <anmol> required due to logging changes
09:20:39 <anmol> nishanth, nope I didn't receive it
09:20:48 <anmol> ankush, ^^
09:21:50 <nishanth> #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.
09:21:59 <nishanth> anmol anything else?
09:22:07 <ankush> nishanth, I going to sit with neha today regarding collection of data points
09:22:16 <anmol> nishanth, nope
09:22:22 <anmol> I am done
09:22:29 <nishanth> ankush, thanks
09:23:34 <nishanth> gowtham. what are you upto?
09:24:05 <gowtham> nishanth, i have modified all the log statements in ceph-integration
09:24:17 <gowtham> nishanth, https://github.com/Tendrl/ceph-integration/pull/103
09:24:30 <gowtham> nishanth, review required for this PR
09:24:59 <gowtham> nishanth, now i am documenting all the messages which is used in ceph-integration
09:25:55 <gowtham> nishanth, review required for https://github.com/Tendrl/node-agent/pull/178
09:26:05 <gowtham> nishanth, logging implementation
09:26:21 <gowtham> nishanth, https://github.com/Tendrl/commons/pull/134
09:26:47 <gowtham> nishanth, status: good not blocked
09:28:53 <nishanth> #accept gowtham making progress on the logging implementation
09:30:09 <nishanth> #action, brainfunked, k4n0, nishanth to review the logging patches - https://github.com/Tendrl/ceph-integration/pull/103,  https://github.com/Tendrl/node-agent/pull/178, https://github.com/Tendrl/commons/pull/134
09:30:46 <nishanth> gowtham, you got all the required information from anmol on logging?
09:31:09 <gowtham> nishanth, yes
09:31:14 <nishanth> cool
09:31:52 <nishanth> anmol_s, what is your progress on logging?
09:34:02 <nishanth> k4n0, any updates?
09:34:31 <k4n0> nishanth, yes
09:35:01 <k4n0> nishanth, working on the import cluster flow post the tagged release, been reviewing PRs, not blocked
09:36:46 <nishanth> #action k4n0 is working on import cluster flow and complete the reviews
09:36:48 <nishanth> thanks
09:37:13 <nishanth> ndarshan, updates?
09:39:01 <ndarshan> working on: https://github.com/Tendrl/specifications/issues/49 (wrapper for gdeploy)
09:39:01 <ndarshan> Sent a Spec PR for same: https://github.com/Tendrl/specifications/pull/129 --> please review,
09:39:01 <ndarshan> Have some questions about deployment of gdeploy : https://github.com/Tendrl/specifications/issues/49#issuecomment-276606702 ---> nishanth, shubhendu, mrugesh please comment
09:39:01 <ndarshan> Had some dsicussion with gdeploy team to clarify fe things. Started working on implementation now
09:39:37 <Shu6h3ndu> k4n0, what is pending on import cluster flow. is it being captured under some issue/spec?
09:40:16 <nishanth> #accept ndarshan send the initial version of provisioning wrapper spec for review
09:41:24 <nishanth> #action k4n0, shu6h3ndu,brainfunked, nishanth to review  https://github.com/Tendrl/specifications/pull/129
09:41:53 <nishanth> #action  k4n0, shu6h3ndu,brainfunked, nishanth to comment on  https://github.com/Tendrl/specifications/issues/49#issuecomment-276606702
09:43:34 <k4n0> Shu6h3ndu, it is here https://github.com/Tendrl/specifications/issues/54#issuecomment-269947580
09:43:55 <nishanth> ndarshan, naything else?
09:44:02 <nishanth> anything*
09:44:13 <ndarshan> that's all from me
09:45:07 <nishanth> Shu6h3ndu, any update on the calamari tests you have done?
09:45:28 <Shu6h3ndu> nishanth, Gregory has not replied the mail or github issue
09:45:52 <Shu6h3ndu> nishanth, I have added required details asked by Mrugesh on that and sent a spec PR today
09:46:08 <Shu6h3ndu> nishanth, my update overall as below
09:46:09 <Shu6h3ndu> worked on https://github.com/Tendrl/node-agent/issues/193 yesterday. Changes PR https://github.com/Tendrl/node-agent/pull/196 merged
09:46:09 <Shu6h3ndu> sent a spec PR for https://github.com/Tendrl/specifications/issues/126
09:46:09 <Shu6h3ndu> nishanth, k4n0, ndarshan, noopq, brainfunked to review spec PR
09:46:09 <Shu6h3ndu> https://github.com/Tendrl/gluster-integration/pull/129 merged. We need https://github.com/Tendrl/commons/pull/145 fot it to work
09:46:10 <Shu6h3ndu> trying to make existing ceph crud flow working post namespace changes
09:48:49 <nishanth> #accept Shu6h3ndu PR ->  https://github.com/Tendrl/node-agent/pull/196  merged
09:49:55 <nishanth> Shu6h3ndu, there is BZ on calamari, please update the questions there
09:50:18 <nishanth> will PM you the bz link offline
09:50:31 <Shu6h3ndu> nishanth, running calamari on all mon nodes ?
09:50:39 <nishanth> yeah
09:51:09 <Shu6h3ndu> nishanth, BZ#1401936 I feel
09:52:53 <nishanth> #action Shu6h3ndu to work with calamari team and sort out the questions related to the CRUD operations
09:54:09 <nishanth> #action brainfunked, k4n0, nishanth to review the spec PR for CRUD operations ->  https://github.com/Tendrl/specifications/issues/126
09:54:24 <Shu6h3ndu> nishanth, also I have asked on the spec issue if calamari is the way to go ahead. plz review and comment
09:54:40 <Shu6h3ndu> I would request all to check and reply on  https://github.com/Tendrl/specifications/issues/126
09:55:13 <nishanth> #action  brainfunked, k4n0, nishanth to comment on  https://github.com/Tendrl/specifications/issues/126
09:55:27 <nishanth> Shu6h3ndu , anything else?
09:56:05 <Shu6h3ndu> nishanth, please review https://github.com/Tendrl/specifications/pull/130
09:56:07 <anmol_s> nishanth, sry I did not see the message .
09:56:32 <Shu6h3ndu> nishanth, k4n0, ndarshan, noopq, brainfunked to review spec PR https://github.com/Tendrl/specifications/pull/130
09:57:19 <nishanth> anmol_s, go ahead
09:57:58 <anmol_s> nishanth, working on code pr for https://github.com/Tendrl/specifications/pull/127
09:59:05 <anmol_s> nishanth, commons changes are almost complete .. will work on gluster_intergration and node_agent next
09:59:18 <nishanth> anmol_s, ok, do you have PR?
09:59:19 <anmol_s> nishanth, that's all from my side
09:59:40 <anmol_s> nishanth, will send send the pr pr as soon as i complete
10:00:13 <nishanth> #action  brainfunked, k4n0, nishanth to review  https://github.com/Tendrl/specifications/pull/127
10:01:01 <nishanth> #action anmol_s to send a PR on log message changes(commons)
10:01:14 <Shu6h3ndu> #action nishanth, k4n0, ndarshan, noopq, brainfunked to review spec PR https://github.com/Tendrl/specifications/pull/130
10:01:26 <nishanth> noopq, updates?
10:01:27 <Shu6h3ndu> nishanth, please add this :)
10:01:56 <nishanth> Shu6h3ndu, already added
10:02:15 <Shu6h3ndu> nishanth, ok. thanks
10:03:13 <nishanth> t1m1, please update your status
10:03:32 <t1m1> nishanth, working on cetosci for tendrl
10:03:52 <t1m1> working on performance-monitoring, node-monitoring rpm spec change
10:04:04 <t1m1> stuck on merge conflict fixing them now
10:04:29 <t1m1> https://github.com/Tendrl/performance-monitoring/pull/32
10:04:45 <t1m1> https://github.com/Tendrl/performance-monitoring/pull/30
10:05:12 <t1m1> need to split pull 30 because it contains changes for both performance-monitoring and alerting
10:05:23 <nishanth> ok
10:05:39 <t1m1> sent patch for fix dependency issue for dashboard : https://github.com/Tendrl/dashboard/pull/119
10:06:08 <t1m1> also working on https://github.com/Tendrl/alerting/pull/34 and
10:06:24 <t1m1> https://github.com/Tendrl/alerting/pull/28
10:06:42 <t1m1> that's all from my side
10:06:53 <nishanth> #action t1m1 to work on building packages for performance monitoring and node monitoring
10:07:19 <nishanth> t1m1, alerting is not high priority compared to other items
10:07:25 <t1m1> sure
10:07:42 <t1m1> first i will complete performance monitoring and node monitoring today
10:08:23 <nishanth> #action t1m1 working on fixing the dependency issue for dashboard(https://github.com/Tendrl/dashboard/pull/119)
10:08:57 <nishanth> what is the update on CI ?
10:09:10 <nishanth> t1m1^^
10:09:14 <t1m1> currently centos ci is on hold
10:09:23 <t1m1> jenkins ci is up and running
10:10:12 <nishanth> so you will continue on centos ci after the package related work is done right?
10:10:17 <nishanth> t1m1?
10:10:32 <t1m1> yes
10:10:42 <nishanth> thanks
10:10:45 <t1m1> centos ci will be little dificult for dashboard
10:10:50 <t1m1> we will discuss later
10:10:53 <nishanth> ok
10:11:20 <nishanth> neha, updates please
10:13:17 <nishanth> dahorak, updates?
10:13:59 <nishanth> fbalak, updates?
10:14:21 <fbalak> #action fbalak Testing new packages.
10:14:22 <fbalak> #action fbalak Reviewing new api documentation: https://github.com/Tendrl/api/pull/65
10:14:24 <fbalak> #action fbalak Working on https://github.com/Tendrl/usmqe-tests/issues/20
10:14:25 <fbalak> #action fbalak Status: good
10:15:41 <nishanth> thanks fbalak
10:16:07 <nishanth> ltrilety, updates
10:16:39 <ltrilety> #info no update from ltrilety, blocked by https://github.com/Tendrl/dashboard/issues/117
10:17:09 <dahorak> nishanth: slowly working on migration of the "jenkins jobs for triggering Tendrl builds in copr " to CentOS CI (till now just checking requirements and possibilities in CentOS CI
10:17:21 <dahorak> otherwise nothing related to Tendrl
10:18:04 <nishanth> dahorak, please work with t1m1 on this
10:18:20 <dahorak> nishanth: sure
10:18:42 <nishanth> ankush, neha, can you guys look into https://github.com/Tendrl/dashboard/issues/117 ?
10:20:43 <ankush> nishanth, sure
10:21:34 <nishanth> ltrilety, have you tested this with the latest builds? I have a freshly installed setup and didn't see this issue
10:22:58 <ltrilety> nishanth: I think so, I installed my machines Yersterday and I didn't see any new build today, so it should be latest
10:24:02 <nishanth> ltrilety, there are new builds last night
10:24:08 <ltrilety> nishanth: I could try that again
10:24:14 <nishanth> #action ltrilety to test https://github.com/Tendrl/dashboard/issues/117 against the latest builds and update
10:24:32 <nishanth> ankush^^
10:24:40 <nishanth> mkudlej, updates
10:25:48 <ltrilety> nishanth: mkudlej's out, he will be back about an hour later
10:25:52 <nishanth> ok
10:26:16 <nishanth> #endmeeting