Thursday, 2014-10-23

*** cindyo has quit IRC00:05
*** theresa_ has quit IRC00:08
*** theresa_ has joined #openstack-monasca00:08
*** theresa_ has quit IRC00:38
*** theresa_ has joined #openstack-monasca00:39
*** ddieterly has joined #openstack-monasca00:42
*** kuhlmant has quit IRC02:04
*** kuhlmant has joined #openstack-monasca02:06
*** theresa_ has quit IRC03:19
*** garyh has quit IRC04:09
*** openstack has joined #openstack-monasca06:12
*** openstack has quit IRC06:59
*** openstack has joined #openstack-monasca14:17
ogzysamuelms: what should i do to install monasca manually?14:18
*** openstackstatus has joined #openstack-monasca14:18
*** ChanServ sets mode: +v openstackstatus14:18
samuelmsHi ogzy14:19
ogzysamuelms: hi14:19
samuelmsogzy, so you'd like to deploy your own monasca :-)14:19
ogzysamuelms: i will either try running vagrant on 8GB host or will install manually14:19
ogzysamuelms: whichever works is what i want14:20
samuelmsogzy, using vagrant is the easier way on 8gb host14:20
ogzysamuelms: ok i will try to find a 8GB 64bit machine if not i will ask here again14:20
ogzysamuelms: is there any email list of monasca?14:21
samuelmsogzy, yes .. not sure if it should be openstack-dev@lists.openstack.org tagging your email as [monasca] ..14:22
samuelmscould anyone confirm this ? ^14:22
kuhlmantogzy: The email for monasca is  monasca@lists.launchpad.net14:22
ogzykuhlmant: and what should i do to register it? sending empty mail?14:22
samuelmskuhlmant, thanks14:22
kuhlmantRegarding the 8GB host for monasca, it is really the devstack box that is the big memory hog, it was increased so you could make vms on it and test monitoring it. If you run devstack or at least keystone somewhere else you can run just the mini-mon vm and it will fit in 8GB14:23
*** rhochmuth has joined #openstack-monasca14:24
ogzykuhlmant: maybe i can find 2 4GB machine14:24
kuhlmantFor registering for the email I am not exactly sure, it is in launchpad somewhere, rhochmuth: Any other info?14:25
ogzyhttps://launchpad.net/~monasca should i join the team?14:28
ogzydo i need to be an active developer?14:28
ogzyi think the email registration is done after joining the team14:28
openstackgerritRob Raymond proposed a change to stackforge/monasca-ui: One more place to remap attribute  https://review.openstack.org/13055514:32
samuelmskuhlmant, from your old split cookbook setup, I updated some configs and now I'm able to deploy monasca on different VMs (as it was already being done with VBs ones) on an OpenStack cloud ..14:33
samuelmskuhlmant, so I have 6 VMs for the monasca components themselves .. and 1 for devstack14:33
samuelmskuhlmant, my question is about connecting a second devstack up there .. I'm not sure if just pluging it on and setting the new monasca-agente to send info to the existing API will work ..14:35
kuhlmantIf you attach a different keystone, you need the right users setup in that keystone and need to point the agents and the api boxes to the right keystone endpoint.14:36
rhochmuthogzy Sure you can join the team. I think if you go to this link, https://launchpad.net/~monasca, you can register.14:36
kuhlmantThe right keystone users/endpoints for monasca-vagrant are here, https://github.com/stackforge/monasca-vagrant/blob/master/cookbooks/devstack/recipes/keystone.rb14:36
rhochmuthWe haven't been active on the email list, but it should work and if you have questions we should all get an email and someone will respond14:37
rhochmuthOr you can ask in here14:37
rhochmuthIRC that is14:37
rhochmuthYou don't need to be an active developer14:37
kuhlmantAlso FWIW, I am working on converting from chef to Ansible for monasca-vagrant. That should be a bit easier to start with, chef is more complicated if you have never used it before. https://review.openstack.org/#/c/127999/14:39
samuelmskuhlmant, if I need to point the agents and the api boxes to the right keystone endpoint ... how can I connect 2 clouds at the same time ?14:39
ogzykuhlmant: +1 to ansible14:40
kuhlmantYou can't connect to two at the same time, just one or the others. You can of course monitor one cloud from another but the system can only use one keystone at a time.14:40
kuhlmantI guess if you want to you could have two apis and point them to different keystone and different agents pointing to the the different apis, but no one really designed for that situation.14:41
samuelmskuhlmant, could you gimme a bit more info on how I can monitor 1 cloud from another? any link?14:41
samuelmskuhlmant, hmm .. cool ..14:42
kuhlmantNo link, just install, monasca-agent on the cloud machines you want to monitor but in the config for monasca-agent point it at the keystone for the other cloud.14:42
openstackgerritA change was merged to stackforge/monasca-ui: One more place to remap attribute  https://review.openstack.org/13055514:47
samuelmskuhlmant, so in that case .. metrics from the second cloud would be stored associated with an existing tenant from the first cloud?14:50
kuhlmantYes14:51
htrutarhochmuth: just joined the team :)14:51
samuelmskuhlmant, cool... got it .. I'm going to try it out, thanks14:51
kuhlmantyour welcome, let us know if you encounter issues.14:51
samuelmskuhlmant, sure14:56
*** dschroeder has joined #openstack-monasca14:57
rhochmuthogzy you are registered and can send emails to the Monasca list.14:57
*** cindyo has joined #openstack-monasca14:57
ogzyrhochmuth: how did you guess my username?14:58
ogzyrhochmuth: really i am registered, thank you :)14:58
*** eglynn-office is now known as eglynn15:00
ogzyleaving for now15:00
*** ogzy has quit IRC15:00
rhochmuthogzy I searched or ogzy and it returned with your name. Bye-bye15:01
samuelmsrhochmuth, I also submitted a membership request :)15:02
samuelmsrhochmuth, thanks15:03
rhochmuthsamuelms, i approved15:06
*** openstackgerrit has quit IRC15:07
*** theresa_ has quit IRC15:33
*** krtaylor has quit IRC15:58
*** openstack has joined #openstack-monasca16:01
*** craigbr has joined #openstack-monasca16:07
*** eglynn is now known as eglynn-office16:08
*** krtaylor has joined #openstack-monasca16:11
*** craigbr has quit IRC16:25
*** craigbr has joined #openstack-monasca16:32
*** openstackgerrit has joined #openstack-monasca16:49
*** garyh has quit IRC16:55
*** garyh has joined #openstack-monasca16:56
samuelmsrhochmuth, yeah I saw .. thanks :-)17:29
*** openstackgerrit has quit IRC17:48
*** openstackgerrit has joined #openstack-monasca17:49
*** craigbr has quit IRC17:59
*** theresa_ has joined #openstack-monasca18:16
*** theresa_ has quit IRC18:20
*** theresa_ has joined #openstack-monasca18:21
*** th_ has joined #openstack-monasca18:23
*** cindyo has quit IRC18:26
*** theresa_ has quit IRC18:27
htrutarhochmuth, kuhlmant: hello again. Is there an easy way to start monasca-api from a code that I changed?18:49
rhochmuthyes19:03
rhochmuthdid you develop in Python or Java19:04
rhochmuthalso, are you running the monasca-vagrant development env19:04
*** craigbr has joined #openstack-monasca19:04
openstackgerritCraig Bryant proposed a change to stackforge/monasca-api: Fix the path in the alarm_definition link  https://review.openstack.org/13058319:05
openstackgerritGary Hessler proposed a change to stackforge/monasca-agent: Updating metrics names and dimensions to be consistent  https://review.openstack.org/13006319:06
rhochmuthgary do you need a new tag for the agent?19:11
garyhrhochmuth I will once the latest review is merged.19:20
htrutarhochmuth: in both, but a bit more experienced in Java. Yes, I'm running the monasca-vagrant env19:22
htrutasorry, misunderstood. developed in java :P19:23
rhochmuthso, what we usually do is develop the api locally on our client system.19:25
rhochmuthwe'll also disable the monasca-api running in the vagrant environent19:25
rhochmuthvagrant ssh mini-mon19:26
rhochmuthwill ssh into the "mini-mon" system19:26
rhochmuthThe stop the monasca api19:26
rhochmuthsudo stop monasca-api19:26
rhochmuthThen start the monasca-api locally supplying the same config file that is in the mini-mon vm19:27
rhochmuthyou can copy /etc/monasca/api-config.yaml to your local system19:28
rhochmuthFor any service that we develop we usually develop locally. We all use MacBooks.19:29
rhochmuthAnd just disable the service that we are developing in the mini-mon vm19:29
*** cindyo has joined #openstack-monasca19:33
htrutarhochmuth: nice. I use Ubuntu. I think it may work too19:36
*** sandywalsh_ has joined #openstack-monasca19:37
htrutaso, you basically generate the jar and run something like "/usr/bin/java -Xmx8g -cp /opt/monasca/monasca-api.jar:/opt/monasca/vertica/vertica_jdbc.jar monasca.api.MonApiApplication server /etc/monasca/api-config.yml" locally?19:37
*** sandywalsh has quit IRC19:39
*** craigbr has quit IRC19:40
rhochmuthcorrect19:46
rhochmuthalthough using intellij I don't have to type that command in.19:47
*** theresa_ has joined #openstack-monasca20:12
*** th_ has quit IRC20:12
*** theresa_ has quit IRC20:33
*** theresa_ has joined #openstack-monasca20:36
*** th_ has joined #openstack-monasca20:44
*** th_ has quit IRC20:46
*** theresa_ has quit IRC20:46
*** theresa_ has joined #openstack-monasca20:47
*** rbak has quit IRC20:49
htrutarhochmuth: nice. I'll try that. Thanks21:00
*** theresa_ has quit IRC21:03
*** theresa_ has joined #openstack-monasca21:06
*** rbak has joined #openstack-monasca21:10
*** craigbr has joined #openstack-monasca21:18
*** th_ has joined #openstack-monasca21:21
*** theresa_ has quit IRC21:23
*** rhochmuth has quit IRC21:56
*** craigbr has quit IRC22:08
*** rhochmuth has joined #openstack-monasca22:20
*** rhochmuth has quit IRC22:21
openstackgerritCindy O'Neill proposed a change to stackforge/monasca-api: Notifications resource support, helpers.py link functions  https://review.openstack.org/13039722:39
*** theresa_ has joined #openstack-monasca22:43
*** th_ has quit IRC22:45
*** ddieterly has quit IRC22:58
*** dschroeder has quit IRC23:29

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!