monasca team mailing list archive

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

I can see that the keystone_url, keystone_user and keystone_password are
defined and sent. I checked keystone manually and can get a token using
mini-mon and password.

I wonder whether there are some prerequisites that are not written in the
README. Do  i need to define a keystone_project variable also for ex?
Somewhere in the role, it is empty.


On Thu, Sep 3, 2015 at 6:57 PM, Kuhlman, Tim <tim.kuhlman@xxxxxxx> wrote:

> That error is in the Ansible module for setting up Monasca notifications.
> It is basically saying it is unable to connect to keystone with the
> credentials it has. That would be this role,
> https://github.com/hpcloud-mon/ansible-monasca-default-alarms and the
> variables it is looking for are keystone_url, keystone_user,
> keystone_password. In the monasca vagrant setup they come group the group
> and host vars, looks like the url is in group_vars/all and the credentials
> in host_vars/mini-mon
>
> FWIW that is very near the end, so the system should basically be up,
> after that is just the experimental events code and the smoke test.
> --
> Tim Kuhlman
> Monitoring
> HPCloud
>
> From: Oğuz Yarımtepe <oguzyarimtepe@xxxxxxxxx>
> Date: Thursday, September 3, 2015 at 9:18 AM
>
> To: Tim Kuhlman <tim.kuhlman@xxxxxxx>
> Cc: "Bryant, Craig W (HP Cloud Service)" <craig.bryant@xxxxxxx>, "
> monasca@xxxxxxxxxxxxxxxxxxx" <monasca@xxxxxxxxxxxxxxxxxxx>
> Subject: Re: [Monasca] question about monasca-agent installation
>
> The explanation helped. But this is what i got when i am applying mini-mon
> yml
>
> Here is how i apply it:
>
> > python /usr/bin/ansible-playbook --limit=mini-mon -T 30 -e
> pipelining=True --inventory-file=/home/oguzy/foo/monasca/inventory
> --extra-vars '{"database_type":"influxdb"}' mini-mon.yml -vv
>
>
> PLAY [Define default alarms]
> **************************************************
>
> TASK: [monasca-default-alarms | Setup default notification method]
> ************
> <10.100.11.46> REMOTE_MODULE monasca_notification_method type=EMAIL
> address= keystone_password=password keystone_project=mini-mon keystone_url=
> http://10.107.3.147:35357/v3 keystone_user=mini-mon name='Default Email'
> failed: [mini-mon] => {"failed": true, "parsed": false}
> No handlers could be found for logger "monascaclient.exc"
> Traceback (most recent call last):
>   File
> "/home/oguz/.ansible/tmp/ansible-tmp-1441292893.74-221640242027909/monasca_notification_method",
> line 1815, in <module>
>     main()
>   File
> "/home/oguz/.ansible/tmp/ansible-tmp-1441292893.74-221640242027909/monasca_notification_method",
> line 1811, in main
>     notification.run()
>   File
> "/home/oguz/.ansible/tmp/ansible-tmp-1441292893.74-221640242027909/monasca_notification_method",
> line 1764, in run
>     notifications = {notif['name']:notif for notif in
> self.monasca.notifications.list()}
>   File
> "/opt/monasca/lib/python2.7/site-packages/monascaclient/v2_0/notifications.py",
> line 55, in list
>     headers=newheaders)
>   File
> "/opt/monasca/lib/python2.7/site-packages/monascaclient/common/http.py",
> line 277, in json_request
>     resp = self._http_request(url, method, **kwargs)
>   File
> "/opt/monasca/lib/python2.7/site-packages/monascaclient/common/http.py",
> line 223, in _http_request
>     raise exc.HTTPUnauthorized("Authentication failed. Please try"
> monascaclient.exc.HTTPUnauthorized: Authentication failed. Please try
> again with option --include-password or export MONASCA_INCLUDE_PASSWORD=1
>
> OpenSSH_6.7p1 Ubuntu-5ubuntu1.3, OpenSSL 1.0.1f 6 Jan 2014
> debug1: Reading configuration data /home/oguzy/.ssh/config
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: /etc/ssh/ssh_config line 19: Applying options for *
> debug1: auto-mux: Trying existing master
> debug1: mux_client_request_session: master session id: 16
> Shared connection to 10.100.11.46 closed.
>
>
> FATAL: all hosts have already failed -- aborting
>
> PLAY RECAP
> ********************************************************************
>
> ERROR: could not create retry file. Check the value of
> the configuration variable 'retry_files_save_path' or set
> 'retry_files_enabled' to False to avoid this message.
>
> mini-mon                   : ok=153  changed=10   unreachable=0
> failed=1
>
>
> I didn't had the idea of the reason of the error. Any idea?
>
>
> On Wed, Sep 2, 2015 at 6:23 PM, Kuhlman, Tim <tim.kuhlman@xxxxxxx> wrote:
>
>> The devstack.yml is really intended just for getting the devstack
>> environment in monasca-vagrant to work. The Ansible roles which are in
>> their own repos are more generally usable. If you already have openstack
>> running all Monasca needs is the right keystone account setup none of the
>> other bits need to be done. I would either use the monasca-keystone ansible
>> role to setup keystone users for Monasca or do so manually and avoid
>> running the monasca-devstack role. The other role you may want to run is
>> the monasca-ui role to setup the horizon plugin but that can be done
>> independently if you want.
>>
>> --
>> Tim Kuhlman
>> Monitoring
>> HPCloud
>>
>> From: Oğuz Yarımtepe <oguzyarimtepe@xxxxxxxxx>
>> Date: Wednesday, September 2, 2015 at 9:06 AM
>> To: Tim Kuhlman <tim.kuhlman@xxxxxxx>
>> Cc: "Bryant, Craig W (HP Cloud Service)" <craig.bryant@xxxxxxx>, "
>> monasca@xxxxxxxxxxxxxxxxxxx" <monasca@xxxxxxxxxxxxxxxxxxx>
>>
>> Subject: Re: [Monasca] question about monasca-agent installation
>>
>> 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
>>
>>
>
>
> --
> Oğuz Yarımtepe
> http://about.me/oguzy
>
>


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