15:00:24 <witek> #startmeeting monasca
15:00:25 <openstack> Meeting started Wed Jun 20 15:00:24 2018 UTC and is due to finish in 60 minutes.  The chair is witek. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:26 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:29 <openstack> The meeting name has been set to 'monasca'
15:00:34 <dougsz> Hi all
15:00:40 <witek> hello everyone
15:00:43 <witek> hi dougsz
15:00:45 <jgrassler> Hello
15:00:54 <haruki> hi
15:01:36 <witek> #link https://etherpad.openstack.org/p/monasca-team-meeting-agenda agenda
15:02:03 <witek> feel free to add topics if you have some
15:02:13 <witek> #topic python 3 support
15:02:52 <witek> Adrian has made some progress on updating monasca-api to pass unit tests with Python 3
15:03:24 <witek> there are some changes submitted in review
15:03:31 <witek> https://review.openstack.org/#/q/owner:adrian.czarnecki%2540ts.fujitsu.com+status:open
15:04:22 <witek> he also started actually running the components with Py3
15:04:36 <witek> with some success
15:05:12 <witek> the next step will be install everything with Py3 and run tempest tests on zuul
15:05:28 <jgrassler> Nice :-)
15:05:32 <jgrassler> All components or just some?
15:05:46 <dougsz> Yeah, good work Adrian, thanks!
15:06:28 <witek> I think we will submit the zuul conf. when all components are ready
15:06:55 <witek> I wanted to ask about the status of monasca-agent change
15:07:03 <witek> https://review.openstack.org/554304
15:07:35 <witek> sc: are you around?
15:09:01 <witek> Adrian could submit a follow-up change to address the outstanding comments
15:10:37 <witek> I'll try to check with sc, but we should move forward with this code
15:11:52 <witek> regarding Py3, there was a bunch of smaller changes in the last days
15:12:05 <witek> all pep and doc jobs should run with py3
15:13:04 <witek> I think, that's all from me, any other comments?
15:13:27 <dougsz> I'll try to take a look at some of the changes next week.
15:13:38 <witek> thanks dougsz
15:13:39 <joadavis> Any advice on forcing py3 on a devstack, for verification?
15:14:07 <witek> joadavis: what do you mean?
15:14:38 <joadavis> I usually just install using stack.sh, but wonder if there is an option we can set to force it to run all the services as python3
15:14:54 <joadavis> all the monasca services, anyway
15:15:00 <witek> https://review.openstack.org/576100
15:15:18 <joadavis> awesome, thanks :)
15:15:29 <witek> not to be merged for now
15:15:33 <witek> just for testing
15:16:38 <witek> anyway, we should have two sets of jobs in the first phase, py2 and py3
15:17:42 <witek> #topic Kafka issues
15:17:56 <witek> pandy_: is that yours?
15:17:58 <pandy_> Hi, witek.
15:18:06 <pandy_> we are following upstream monasca deployment as like  http://paste.openstack.org/show/723938/
15:18:06 <pandy_> While creating stack with that, getting error with few monasca components which are mainly because of "kafka" see error over here http://paste.openstack.org/show/723939/	Hi
15:18:50 <pandy_> docker monasca components like notification, persister are failed with kafka
15:19:26 <pandy_> Even same issues while using kafka+zookeeper on localmachine and other on docker
15:20:13 <witek> so, you're just cloning monasca-docker repo
15:20:29 <pandy_> witek, would like to know, is there anything wrong in docker-compose file "http://paste.openstack.org/show/723938/
15:20:35 <witek> and run `docker-compose up`
15:21:07 <pandy_> I did "docker stack compose -c docker.yaml monasca"
15:21:26 <nseyvet> that most likely will not work.
15:21:53 <nseyvet> Some of the images (AFAIK) in the docker-compose will not point to the right versions
15:21:57 <pandy_> when i do docker compose up.. getting error "failed to find service kibana "
15:22:51 <pandy_> ERROR: Service 'kibana' depends on service 'keystone' which is undefined.
15:23:21 <witek> kibana is not included in docker-compose.yml
15:23:37 <witek> and should not
15:23:56 <pandy_> actually i am not using keystone in my setup &  "docker-compose -f log-pipeline.yml -f docker-compose.yml up"
15:24:07 <pandy_> do i need to use kibana in docker compose
15:24:31 <dougsz> I wouldn't worry about kibana until you have the basic system up and running
15:24:55 <pandy_> instead of keystone why cant i pass values directly as like in http://paste.openstack.org/show/723938/, where direclty pasing my openrc vairables
15:25:19 <wacuuu_> witek: can you explain shortly why?
15:25:43 <witek> docker-compose.yml includes metric pipeline only
15:26:02 <haruki> can you share `docker logs <container_name>`?
15:26:04 <witek> log-pipeline.yml includes ELK with addons
15:26:20 <pandy_> witek, dougsz my docker-compose i have customised like http://paste.openstack.org/show/723941/ and removed keystone in all places in that file
15:26:42 <pandy_> haruki, here http://paste.openstack.org/show/723939/
15:27:27 <pandy_> to all, whether i can pass my keystone values directly as like my docker-compose file  http://paste.openstack.org/show/723938/ or not ?
15:27:47 <haruki> pandy,  thanks
15:28:02 <pandy_> and the error seems not related to keystone, its trying to reach kafka and failing
15:28:06 <witek> pandy_: yes, as described here: https://github.com/monasca/monasca-docker/blob/master/docs/external_cmps.md#using-external-openstack-keystone
15:29:14 <pandy_> witek, https://github.com/monasca/monasca-docker/blob/master/docs/external_cmps.md#using-external-openstack-keystone think this is applicable for all monasca components like api, persister, notificaiton, alarms
15:29:44 <pandy_> if yes mean, my issue is related to kafka is not ready & unable to connect
15:30:20 <witek> only api, agent and grafana need to communicate with keystone
15:30:30 <pandy_> I have cross checked with indian-openstack group by using this docker-compose
15:31:12 <pandy_> witek, yes only those two only using keystone. but issue is with kafka.
15:32:32 <pandy_> Also noticed by connecting inside monasca-kafka container, where "kafka, zookeeper" service not running, i have started it manually
15:34:19 <witek> I'm pulling new images, we'll try to reproduce with `docker-compose up`
15:34:25 <pandy_> Does this "monasca kafka+zookeeper"  wrote for cluster setup ? because inside container "zookeeper.properties", "kakfa.server.properties" are similar like sinel node setup
15:34:44 <pandy_> witek, ok
15:34:47 <witek> it's single node deployment
15:35:16 <pandy_> okay, I am doing this monasca setup on docker swarm on 3 node setup.
15:36:24 <pandy_> I think for production, 3 node setup is good to go
15:36:40 <witek> would you like to share the configuration in some git repo?
15:37:13 <witek> 3 node is a good start
15:37:22 <pandy_> which configuration you mean, may i know please
15:38:15 <pandy_> witek, may i know which configuration
15:38:50 <witek> of your docker swarm cluster
15:39:25 <pandy_> https://github.com/wurstmeister/kafka-docker.git
15:39:49 <pandy_> the above will do kafka+zookeeper in swarm setup
15:40:21 <pandy_> docker swarm is like normal setup on 3 nodes
15:41:22 <pandy_> witek, followed this to do docker swarm on 3 nodes https://docs.docker.com/engine/swarm/swarm-tutorial/create-swarm/
15:42:08 <pandy_> witek, let me know whether current upstream monasca is for single node setup or it will support cluster node
15:42:47 <witek> all components can be clustered, like e.g. in monasca-helm
15:43:07 <pandy_> okay, how about kafka+zookeeper
15:43:07 <haruki> I also have an experience to see the log which is `pykafka.exceptions.LeaderNotAvailable` in Brandstetter fork in here https://github.com/Brandstetter/monasca-docker (maybe, because I'm in my home and can's see company info), but anyway, I will share my experience with witek (I don't know our issue is same as pandy's)
15:44:12 <witek> pandy_: I refer you to monasca-helm repo
15:45:00 <pandy_> witek, let me know how to use kafka+zookeeper in clustered way in https://github.com/Brandstetter/monasca-docker
15:45:48 <pandy_> am sorry, how to use kafka+zookeeper in clustered setup in https://github.com/Brandstetter/monasca-docker https://github.com/monasca/monasca-docker/blob/master/docker-compose.yml
15:46:06 <witek> monasca-docker is for single node deployment as of now
15:46:25 <witek> you can contribute 3 node configuration if you're interested
15:46:44 <pandy_> https://github.com/monasca/monasca-helm is for kubernetes it seems am right ?
15:47:11 <witek> some high level description of possible approach is here: https://github.com/monasca/monasca-docker/issues/154
15:47:37 <pandy_> we dont have kubernetes and we need to use monasca-docker in clustered setup like 3 nodes
15:47:41 <witek> pandy_: yes, helm is for K8
15:47:59 <witek> can we move on to the next topic?
15:49:03 <pandy_> witek, okay thanks :) I will conclude that current https://github.com/monasca/monasca-docker/blob/master/docker-compose.yml is for single node and need to use helm for clsutered setup if have k8 am i right
15:49:58 <witek> yes, or provide own deployment configuration for 3 nodes
15:50:31 <pandy_> witek, okay thanks got it. I will do setup on 3 nodes and push it to upstream once successfull
15:50:40 <witek> great, thanks
15:50:49 <pandy_> thanks all :)
15:51:05 <witek> you could also have a look on progress in Kolla project
15:51:24 <pandy_> witek, yes had a word with dougsz, sure i will look into that
15:51:36 <witek> #topic Grafana app
15:52:03 <dougsz> So we have an extra pair of hands. Charana has joined our team.
15:52:16 <witek> great to hear :)
15:52:34 <dougsz> Is anyone using the Monasca Grafana App?
15:52:55 <witek> we have looked at it last summer
15:53:08 <witek> I'm not sure about HPE
15:53:15 <dougsz> We had some bugs filed, and Charana was looking at resolving them. He's started by adding a test framework.
15:53:16 <Charana> hey
15:53:34 <witek> hi Charana, nice to meet you
15:53:56 <dougsz> So the workflow on Monasca github is to submit a PR, and then wait for 2 approvals before merging?
15:54:09 <dougsz> We should also add some notes on signing commits.
15:54:10 <Charana> i've written some unit tests for the MonascaClient service and set it up with travis
15:54:26 <Charana> witek :)
15:54:33 <witek> we don't strictly need 2 approvals
15:55:21 <witek> also, the grafana-app project was not really active, so just 1 approval if perfectly fine
15:55:33 <dougsz> Ok, thanks.
15:55:40 <witek> s/if/is
15:56:04 <witek> yes, we should be signing commits
15:56:20 <witek> some layers wanted that
15:56:40 <dougsz> And if anyone with front end experience cares to comment on the PRs, please fire away
15:57:06 <dougsz> It's all new to me!
15:57:15 <witek> should we use the repo in monasca org?
15:57:18 <witek> https://github.com/monasca/monasca-grafana
15:57:40 <dougsz> Yeah - we are looking to move to that.
15:57:48 <witek> thanks, great
15:57:53 <dougsz> I think it might be best to delete the StackHPC repo to avoid confusion.
15:58:00 <dougsz> Ok, thanks witek - that's it from me.
15:58:09 <witek> thanks dougsz and Charana
15:58:22 <Charana> cheers
15:58:55 <witek> ok, our time is up
15:59:02 <witek> thank you all for joining
15:59:11 <witek> see you next week
15:59:12 <dougsz> bye guys
15:59:13 <witek> bye
15:59:18 <jgrassler> See you!
15:59:20 <haruki> bye
15:59:22 <wacuuu_> Bye
15:59:41 <witek> #endmeeting