15:02:18 <bklei_> #startmeeting monasca
15:02:19 <openstack> Meeting started Wed Dec 16 15:02:18 2015 UTC and is due to finish in 60 minutes.  The chair is bklei_. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:02:22 <openstack> The meeting name has been set to 'monasca'
15:02:28 <bklei_> o\
15:02:34 <witek> hi bklei_
15:02:42 <bklei_> good morning!
15:02:45 <witek> thank you for taking over
15:02:49 <tgraichen> hi
15:02:53 <bklei_> agenda at https://etherpad.openstack.org/p/monasca-team-meeting-agenda
15:02:57 <bklei_> pretty light
15:03:01 <witek> :)
15:03:18 <bklei_> #topic Any updates on cassandra support?
15:03:19 <rbak> o/
15:03:22 <bmotz> o/
15:03:29 <ddieterly> o/
15:03:40 <bklei_> anyone have an update on ^^?
15:03:40 <ddieterly> there's a blueprint up for the data model
15:03:44 <bklei_> haven't heard much
15:04:01 <ddieterly> https://blueprints.launchpad.net/monasca/+spec/monasca-cassandra
15:04:41 <ddieterly> expecting to have implementation done by end of Jan 2016
15:04:48 <bklei_> do we need feedback on the blueprint?
15:04:59 <ddieterly> that would be appreciated
15:05:31 <bklei_> that's great, any sense on how it's performing?
15:06:47 <bklei_> or are we not that far in the implementation...
15:07:10 <ddieterly> need to implement it first :-)
15:08:17 <bklei_> ok, cool, will look at the blueprint
15:08:52 <ddieterly> if anyone knows anything about cassandra and can give the blueprint a critical look, that would be very helpful
15:09:04 <bklei_> looking forward to trying it, would like to start on our puppet module to install cassandra as soon as there's something to play with
15:09:26 <bklei_> anything else on that topic?
15:09:31 <ddieterly> since we are new to cassandra, we could use some babysitting
15:10:10 <bklei_> well, twc can help with testing for sure, and giving perf/stability feedback
15:10:31 <bklei_> very interested in how it performs concurrently
15:11:07 <ddieterly> the implementation will be in python, so please factor that into your expectations for performance
15:11:23 <bklei_> sure
15:11:30 <bklei_> you working on it?
15:11:33 <ddieterly> yes
15:11:39 <bklei_> then it'll be perfect
15:11:49 <ddieterly> ah, shucks...
15:11:52 <bklei_> ok, next topic
15:12:07 <bklei_> #topic Grafana 2.0 update
15:12:14 <bklei_> rbak, any updates?
15:12:23 <rbak> Only a couple
15:12:41 <rbak> I added some new features to the plugin to help with dimension splitting
15:13:06 <rbak> You can find descriptions in the blueprint or the plugin.
15:13:31 <rbak> And I'm starting to free up enough to start working on the keystone integration.
15:13:52 <tgraichen> cool
15:13:52 <rbak> I'm off for the next couple weeks but hopefully I'll have an update for that in January.
15:14:07 <rbak> That's it for me.
15:14:24 <witek> Is horizon integration planed?
15:14:48 <rbak> Depends on what you mean.
15:15:06 <witek> integration with monasca-ui
15:15:20 <rbak> It should be launchable from inside horizon, but I don't thinks it's realistic to display grafana within horizon.
15:16:01 <witek> ok
15:16:01 <rbak> It would just add another border that would reduce the space for viewing the graphs.
15:16:26 <bklei_> you think we'll get single sign on rbak?
15:16:31 <bklei_> token passing...
15:16:40 <rbak> Not sure about that yet.
15:16:45 <rbak> I hope so.
15:16:47 <bklei_> ditto
15:17:03 <bklei_> baby steps maybe
15:17:24 <bklei_> or if you get the keystone plugin working, maybe witek can pitch in with sso
15:18:19 <rbak> The difficulty is that if we want sso and grafana to not stop working when the token expires, we'll have to pass the username/password
15:18:47 <bklei_> hopefully not in clear text
15:18:59 <rbak> definitely not in clear text
15:19:27 <bklei_> yeah, giving grafana the ability to stay logged in would be great
15:19:56 <rbak> We should be able to do that.  The question is if we can do that with sso.
15:20:24 <bklei_> gotcha
15:21:08 <bklei_> other discussion on 2.0 grafana?
15:21:43 <bklei_> or any other topics?  that's it for the agenda
15:22:28 <pradipm> May I please ask a simple, novice query related to the setup of monasca through vagrant? If this is possible here to ask
15:23:01 <bklei_> ok, with me, we're out of things to discuss
15:23:18 <ddieterly> i was wondering if any progress on https://review.openstack.org/#/c/226733/ was planned
15:23:50 <witek> oh, that's Tomasz
15:24:33 <ddieterly> looks like some tempest tests are failing
15:25:01 <witek> ddieterly: :(
15:25:18 <witek> I'll tell Tomasz to take a look
15:25:27 <ddieterly> ok, thanks
15:25:42 <pradipm> may I proceed with my query, if allowed?
15:25:50 <bklei_> go
15:26:28 <pradipm> After the vagrant setup, how can one changes the Monasca code and then re-run the same to deploy to the vagrant mini-mon?
15:26:40 <ddieterly> pradipm: good question
15:27:00 <pradipm> like in other OS services, I can just restart the service and it's get started automatically
15:27:03 <ddieterly> you need to login into the vm using 'vagrant ssh'
15:27:26 <ddieterly> then, make your code changes in the /opt/monasca-api repo or whatever repo you want to change
15:28:12 <ddieterly> then you can run the devstack commands from inside the vm to tear down devstack and then rebuild devstack
15:28:52 <ddieterly> since you already have the repos inside the vm, devstack will not overwrite them
15:29:04 <pradipm> thanks  ddieterly.
15:29:16 <ddieterly> welcome
15:29:24 <bklei_> i had one more
15:29:32 <pradipm> Inside the /opt/monasca/ - I can see the *.jar files.
15:30:11 <bklei_> https://review.openstack.org/#/c/241906/ looks good to me code-wise, haven't had time to test, can m hoppal take a look?
15:30:12 <ddieterly> pradipm: are you using mini-mon or devstack
15:30:37 <pradipm> ddieterly: I am inside mini-mon
15:30:40 <ddieterly> if you are using mini-mon, you will have to copy jars into mini-mon and restart the services
15:31:40 <ddieterly> so, copying is easy
15:32:24 <pradipm> ddieterly: So inside mini-mon it's Java, whereas inside "devstack" VM it is python implementation of monasca components?
15:32:36 <ddieterly> if you are using mini-mon then /vagrant_home is mapped to your home folder in the host OS, so copying is easy
15:33:23 <ddieterly> devstack can use java or python, but devstack checks out all the repos and builds the components from top of tree
15:33:55 <ddieterly> mini-mon currently uses java and uses jars from a repo
15:34:02 <pradipm> ddieterly: I see. So that checking out includes Monasca components too?
15:34:16 <ddieterly> yes, all the components
15:34:55 <pradipm> ddieterly: Then one can just play it inside the "devstack" VM itself like any other OS services. ... (screen -x etc. etc.)
15:35:18 <ddieterly> yes
15:35:31 <pradipm> ddieterly: Thank You very much.
15:35:56 <pradipm> thanks a lot to the moderator also for giving me permission to ask my queries.
15:36:05 <bklei_> np, i'm a temp
15:36:19 <bklei_> so wondering about https://review.openstack.org/#/c/241906/
15:36:21 <ddieterly> have a look at https://github.com/openstack/monasca-api/tree/master/devstack
15:37:02 <bklei_> pradipm: plug for devstack, in my opinion, easier than mini-mon, but that's just me
15:39:13 <pradipm> ddieterly: thank you. just like another (bunch) of services like Cinder,Manilla etc.
15:39:25 <ddieterly> yes
15:39:36 <ddieterly> the vagrant file is the easies thing to use
15:40:17 <pradipm> bklei_: thanks.
15:40:36 <bklei_> np -- is hoppal around?
15:42:28 <bklei_> perhaps not, hoping to get other eyes on the alarm def modification change
15:42:34 <bklei_> will ping him offline
15:42:55 <bklei_> ok, anything else to discuss?
15:43:03 <bklei_> i'll be out for a couple weeks, likely others
15:43:16 <ddieterly> yea, i'm out for the next 2 weeks as well
15:43:43 <bklei_> sounds like rhochmuth is too
15:43:58 <witek> me as well
15:44:22 <pradipm> ddieterly: If I follow  https://github.com/openstack/monasca-api/tree/master/devstack - then the Monasca components and the other devstack service will/might run on the same VM (say very simple setup). Right am I?
15:44:22 <bklei_> sounds like we skip, unless someone else grabs the reigns
15:45:14 <ddieterly> right
15:45:30 <ddieterly> just run 'vagrant up'
15:45:59 <pradipm> ddieterly: thanks
15:46:17 <ddieterly> bklei_: yes, let's skip
15:46:40 <bklei_> agreed, not sure the formal process for cancelling an irc weekly
15:46:56 <ddieterly> we can just let it run
15:47:15 <ddieterly> if anyone wants to jump in and use the meeting, they can
15:47:27 <witek> i think Roland should write an email on mailing list
15:47:43 <bklei_> +1
15:47:48 <ddieterly> roland is out for the next 3 weeks
15:48:18 <bklei_> what's the email alias?  i forget
15:48:21 <ddieterly> well, this week and the next 2
15:49:01 <ddieterly> i can email him and tell him to cancel
15:49:22 <witek> monasca@lists.launchpad.net
15:49:38 <bklei_> thx #witek
15:50:16 <bklei_> pradipm: can use ^^ email to get questions answered too
15:50:31 <bklei_> as well as #openstack-monasca channel
15:51:09 <bklei_> ok, other topics?
15:51:26 <pradipm> Thanks bklei_. We are in #openstack-monasca and shall query on monasca@lists.launchpad.net (if required). Thanks a lot.
15:51:48 <bklei_> cool, thx ddieterly for fielding questions
15:51:53 <ddieterly> sure
15:52:04 <bklei_> ok, last call
15:52:28 <bklei_> #endmeeting