monasca team mailing list archive

[Oğuz Yarımtepe <oguzyarimtepe@xxxxxxxxx>]

I tried to install monasca to a seperat vm by using vagrant dev environment
ymls. It seems keystone side requires to be configured first so i decided
to apply devstack.yml to my current openstack test environment but i
realized the role monasca-devstack and it seems it is changing the rabbitmq
and mysql configuration. I am not sure whether is really equired and will
it broke my openstack installation since it creates come exchanges with the
same name that i already have like nova.

Any precautions that i should take into considerations?

On Fri, Aug 21, 2015 at 6:09 PM, Kuhlman, Tim <tim.kuhlman@xxxxxx> wrote:

> Yes you can use those Ansible roles to install to another node. This is
> what the Monasca Vagrant <https://github.com/stackforge/monasca-vagrant>
> dev environment does, it creates two VMs one with devstack and the UI and
> the other with everything else on it. I would suggest using that.
>
> If for some reason you want to install apart from those VMs to another
> node, the vagrant environment can at least be used as a guide for how to
> use the Ansible. The mini-mon.yml file is the playbook that installs the
> Monasca stack. It pulls its variables from the host and group vars, some of
> which will have to be modified to set the right ips etc.
> --
> Tim Kuhlman
> Monitoring
> HPCloud
>
> From: Oğuz Yarımtepe <oguzyarimtepe@xxxxxxxxx>
> Date: Friday, August 21, 2015 at 7:54 AM
> To: "Bryant, Craig W (HP Cloud Service)" <craig.bryant@xxxxxx>
>
> Cc: Tim Kuhlman <tim.kuhlman@xxxxxx>, "monasca@xxxxxxxxxxxxxxxxxxx" <
> monasca@xxxxxxxxxxxxxxxxxxx>
> Subject: Re: [Monasca] question about monasca-agent installation
>
> If i want to install Monasca to my test environment, except from UI part,
> will i use and install all cookbooks listed here
> https://github.com/search?utf8=%E2%9C%93&q=ansible-monasca to another
> node as a monitoring node?
>
> On Fri, Aug 21, 2015 at 4:38 PM, Bryant, Craig W (HP Cloud Service) <
> craig.bryant@xxxxxx> wrote:
>
>> 60 seconds is currently the minimum period.
>>
>> Craig Bryant
>> HPCloud Monasca
>> From: Oğuz Yarımtepe <oguzyarimtepe@xxxxxxxxx>
>> Date: Friday, August 21, 2015 at 7:25 AM
>> To: Microsoft Office User <craig.bryant@xxxxxx>
>> Cc: Tim Kuhlman <tim.kuhlman@xxxxxx>, "monasca@xxxxxxxxxxxxxxxxxxx" <
>> monasca@xxxxxxxxxxxxxxxxxxx>
>>
>> Subject: Re: [Monasca] question about monasca-agent installation
>>
>> Hi,
>>
>> I removed the times part and it worked as expected. Is there a
>> possibility to lower the default 60 seconds evaluation period?
>>
>>
>>
>> On Fri, Aug 21, 2015 at 4:12 PM, Bryant, Craig W (HP Cloud Service) <
>> craig.bryant@xxxxxx> wrote:
>>
>>> The alarm expression “ avg(cpu.user_perc) > 5 times 2” requires that the
>>> threshold value be exceeded for at least two minutes before the alarm goes
>>> to the ALARM state. The default period is 60 seconds and the “times 2”
>>> means two 60 second periods. How long does it take for it to change? It
>>> should be between two and three minutes given that expression.
>>>
>>> Craig Bryant
>>> HPCloud Monasca
>>>
>>> From: Oğuz Yarımtepe <oguzyarimtepe@xxxxxxxxx>
>>> Date: Friday, August 21, 2015 at 6:27 AM
>>> To: Tim Kuhlman <tim.kuhlman@xxxxxx>
>>> Cc: "monasca@xxxxxxxxxxxxxxxxxxx" <monasca@xxxxxxxxxxxxxxxxxxx>
>>> Subject: Re: [Monasca] question about monasca-agent installation
>>>
>>> I followed the pip method and set the monasca agent manually at one of
>>> my vms and used the monasca docker instance  also for keystone url and
>>> monasca api url.
>>> I also created an alarm: avg(cpu.user_perc) > 5 times 2
>>>
>>> I run the below command to create a
>>> cpu load stress --cpu 2 --timeout 600
>>>
>>> I can see the alarms are created but there is a latency. Takes some
>>> minutes to see the alarm. How can i make it more real time or am i missing
>>> something?
>>>
>>> I checked the times of the two machines and they are same at tha docker
>>> side and at my vm.
>>>
>>>
>>> On Thu, Aug 20, 2015 at 6:36 PM, Kuhlman, Tim <tim.kuhlman@xxxxxx>
>>> wrote:
>>>
>>>> You have some options on how you install the agent. You can certainly
>>>> install with just pip install the Ansible role actually does this but in
>>>> addition runs monasca-setup for you. Using pip is discussed on this page,
>>>> https://github.com/stackforge/monasca-agent/blob/master/docs/Agent.md#installing
>>>>
>>>> The Ansible role can make things even easier in particular if you have
>>>> Ansible installed. The playbook you call this from can be quite simple,
>>>> here is one I use:
>>>>
>>>> - *name*: Installs the Monasca Agent
>>>>
>>>>
>>>>
>>>>   *hosts*: monasca
>>>>
>>>>
>>>>
>>>>   *sudo*: yes
>>>>
>>>>
>>>>
>>>>   *vars*:
>>>>
>>>>
>>>>
>>>>     *monasca_agent_check_frequency*:15
>>>>
>>>>
>>>>
>>>>   *roles*:
>>>>
>>>>
>>>>
>>>>     - {*role*: monasca-agent, *tags*:[agent]}
>>>>
>>>> The key thing to be aware of is that the requirements for the role
>>>> which are all listed in the README.md at
>>>> https://github.com/hpcloud-mon/ansible-monasca-agent
>>>> In the above example those requirements are defined in the group_vars.
>>>> --
>>>> Tim Kuhlman
>>>> Monitoring
>>>> HPCloud
>>>>
>>>> From: Monasca <monasca-bounces+tim.kuhlman=hp.com@xxxxxxxxxxxxxxxxxxx>
>>>> on behalf of Oğuz Yarımtepe <oguzyarimtepe@xxxxxxxxx>
>>>> Date: Thursday, August 20, 2015 at 8:07 AM
>>>> To: "monasca@xxxxxxxxxxxxxxxxxxx" <monasca@xxxxxxxxxxxxxxxxxxx>
>>>> Subject: [Monasca] question about monasca-agent installation
>>>>
>>>>
>>>> What is the right way to install monasca-agent? Using
>>>> https://github.com/hpcloud-mon/ansible-monasca-agent or pip install?
>>>>
>>>> How will the ansible cookbook be used? There is no main.yml to run the
>>>> cookbook. Anyone can give me an example?
>>>>
>>>> --
>>>> Oğuz Yarımtepe
>>>> http://about.me/oguzy
>>>>
>>>>
>>>
>>>
>>> --
>>> Oğuz Yarımtepe
>>> http://about.me/oguzy
>>>
>>>
>>
>>
>> --
>> Oğuz Yarımtepe
>> http://about.me/oguzy
>>
>>
>
>
> --
> Oğuz Yarımtepe
> http://about.me/oguzy
>
>


-- 
Oğuz Yarımtepe
http://about.me/oguzy