Re: [openstack-dev] [monasca] future of thresholder on Storm

2017-03-13 Thread Brandt, Ryan 
Hello Joachim, all,

I’m not aware of an upcoming or existing replacement for the thresholding 
engine, Roland may be able to speak on that, but the Monasca query language is 
currently expected to be implemented in the existing engine.

Thanks,
Ryan

From: "Barheine, Joachim" 
>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Monday, March 13, 2017 at 2:10 AM
To: 
"openstack-dev@lists.openstack.org" 
>
Subject: [openstack-dev] [monasca] future of thresholder on Storm

Hi all,

What are your plans for the Monasca thresholder on Apache Storm, especially 
with respect to the upcoming Monasca query language?

I saw that there is a component monasca-transform that is based on Apache Spark.

Are there plans to build a new alarming engine on Spark that is for example 
supporting mathematical expressions and multiple metrics in alarm rules?

Thanks and regards
Joachim
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Monasca] Monasca devstack installation is failing

2017-01-05 Thread Brandt, Ryan 
I think this is going to require more time and information. Perhaps you could 
open a launchpad bug to track this?

I just brought up a new vagrant successfully yesterday, would you mind checking 
if you have the latest code and trying again? Also, if there is anything else 
relating to storm or monasca-thresh in that last log you provided, could you 
include that as well?

Thanks,
Ryan

From: Pradeep Singh >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Wednesday, January 4, 2017 at 11:33 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [Monasca] Monasca devstack installation is failing


Hello,

I am trying to install Monasca devstack using vagrant file given in monasca-ui 
repo.

And its failing again and again with below error.

Could you please help me, i will really appreciate your help.


==> default: 2017-01-05 06:28:06.125 | ++ functions-common:start_service:2306   
   :   sudo /bin/systemctl start monasca-thresh

==> default: 2017-01-05 06:28:27.440 | Job for monasca-thresh.service failed 
because the control process exited with error code. See "systemctl status 
monasca-thresh.service" and "journalctl -xe" for details.

==> default: 2017-01-05 06:28:27.444 | ++ 
/opt/stack/monasca-api/devstack/plugin.sh:start_monasca_services:235 :   
restart_service monasca-thresh

==> default: 2017-01-05 06:28:27.447 | ++ functions-common:restart_service:2282 
   :   '[' -x /bin/systemctl ']'

==> default: 2017-01-05 06:28:27.450 | ++ functions-common:restart_service:2283 
   :   sudo /bin/systemctl restart monasca-thresh

==> default: 2017-01-05 06:28:47.368 | Job for monasca-thresh.service failed 
because the control process exited with error code. See "systemctl status 
monasca-thresh.service" and "journalctl -xe" for details.

vagrant@devstack:~$ systemctl status monasca-thresh.service

● monasca-thresh.service - LSB: Monitoring threshold engine running under storm

   Loaded: loaded (/etc/init.d/monasca-thresh; bad; vendor preset: enabled)

   Active: failed (Result: exit-code) since Thu 2017-01-05 06:28:47 UTC; 27s ago

 Docs: man:systemd-sysv-generator(8)

  Process: 28638 ExecStart=/etc/init.d/monasca-thresh start (code=exited, 
status=1/FAILURE)


Jan 05 06:28:47 devstack monasca-thresh[28638]: main()

Jan 05 06:28:47 devstack monasca-thresh[28638]:   File 
"/opt/storm/current/bin/storm.py", line 766, in main

Jan 05 06:28:47 devstack monasca-thresh[28638]: (COMMANDS.get(COMMAND, 
unknown_command))(*ARGS)

Jan 05 06:28:47 devstack monasca-thresh[28638]:   File 
"/opt/storm/current/bin/storm.py", line 248, in jar

Jan 05 06:28:47 devstack monasca-thresh[28638]: os.remove(tmpjar)

Jan 05 06:28:47 devstack monasca-thresh[28638]: OSError: [Errno 2] No such file 
or directory: '/tmp/30c1980ed31011e68cd3080027b55b5e.jar'

Jan 05 06:28:47 devstack systemd[1]: monasca-thresh.service: Control process 
exited, code=exited status=1

Jan 05 06:28:47 devstack systemd[1]: Failed to start LSB: Monitoring threshold 
engine running under storm.

Jan 05 06:28:47 devstack systemd[1]: monasca-thresh.service: Unit entered 
failed state.

Jan 05 06:28:47 devstack systemd[1]: monasca-thresh.service: Failed with result 
'exit-code'.


Thanks,

Pradeep



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [monasca]Monasca event handling capabilities

2017-01-04 Thread Brandt, Ryan 
Hello,

Monasca events handling is an early work in progress, see 
https://wiki.openstack.org/wiki/Monasca/Events for some information.

Information on what metrics are available from each plugin can be found at 
https://github.com/openstack/monasca-agent/blob/master/docs/Plugins.md

Custom checks are at 
https://github.com/openstack/monasca-agent/tree/master/monasca_agent/collector/checks_d
Detection plugins are at 
https://github.com/openstack/monasca-agent/tree/master/monasca_setup/detection/plugins

For reference, detection plugins are used to configure check plugins which 
actually collect the metrics. Neutron doesn't have a check plugin, instead it's 
detection plugin configures some standard check plugins to monitor processes 
and http health.

Ryan

From: Pradeep Singh >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Tuesday, January 3, 2017 at 11:01 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [monasca]Monasca event handling capabilities

Hello,

Please excuse  me if i asked this question on wrong mailing list.

I have few queries related to Monasca.

1) How do Monasca collects events releases by other openstack services like 
Nova and Cinder?
2) Can monasca collects the metrics from Neutron and other SDN controllers?

please guide me for any documentation if available.

I will be really thankful to you.

Thanks,
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Monasca]

2017-01-04 Thread Brandt, Ryan 
Apologies for the delay in response, just returning from the holidays.

>From the trace, it would appear the monasca API is unable to authenticate with 
>keystone. The API’s admin credentials may not be valid (either they do not 
>exist in keystone or are configured incorrectly for the API) which would cause 
>the API to be unable to validate tokens on incoming requests. The admin 
>credentials for the python monasca API are under [keystone_authtoken] in 
>‘/etc/monasca/api-config.conf’.

Ryan

From: Sanjana Pai Nagarmat >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Monday, January 2, 2017 at 1:48 AM
To: 
"openstack-dev@lists.openstack.org" 
>
Subject: [openstack-dev] [Monasca]

Hello,


I have a clean install of monasca-api and monasca-log-management plugins with 
devstack on ubuntu 14.04.
However when I try using the monasca CLI, I get HTTP 503:Service Unavailable 
error.
I tried accessing the monasca dashboard in Horizon, but that also throws error.

ubuntu@monasca:~$ monasca metric-list
ERROR (exc:80) exception: {"message": "The server is currently unavailable. 
Please try again at a later time.\n\n\n", "code": "503 Service 
Unavailable", "title": "Service Unavailable"}
HTTPException code=503 message={"message": "The server is currently 
unavailable. Please try again at a later time.\n\n\n", "code": "503 
Service Unavailable", "title": "Service Unavailable"}
ubuntu@monasca:~$


The monasca-api log file has the following contents:
2017-01-02 08:15:20,158 DEBUG [gunicorn.error][GreenThread-2] Closing 
connection.
2017-01-02 08:15:24,952 DEBUG [gunicorn.error][GreenThread-5] GET /v2.0/metrics
2017-01-02 08:15:24,954 DEBUG [keystonemiddleware.auth_token][GreenThread-5] 
Authenticating user token
2017-01-02 08:15:24,957 DEBUG [keystoneauth.identity.v2][GreenThread-5] Making 
authentication request to http://127.0.0.1:35357/v2.0/tokens
2017-01-02 08:15:24,964 INFO 
[requests.packages.urllib3.connectionpool][GreenThread-5] Resetting dropped 
connection: 127.0.0.1
2017-01-02 08:15:27,342 DEBUG 
[requests.packages.urllib3.connectionpool][GreenThread-5] "POST /v2.0/tokens 
HTTP/1.1" 401 114
2017-01-02 08:15:27,343 DEBUG [keystoneauth.session][GreenThread-5] Request 
returned failure status: 401
2017-01-02 08:15:27,345 INFO [keystonemiddleware.auth_token][GreenThread-5] 
Identity server rejected authorization
2017-01-02 08:15:27,346 WARNING [keystonemiddleware.auth_token][GreenThread-5] 
Identity response: {"error": {"message": "The request you have made requires 
authentication.", "code": 401, "title": "Unauthorized"}}
2017-01-02 08:15:27,346 INFO [keystonemiddleware.auth_token][GreenThread-5] 
Retrying validation
2017-01-02 08:15:27,347 DEBUG [keystoneauth.identity.v2][GreenThread-5] Making 
authentication request to http://127.0.0.1:35357/v2.0/tokens
2017-01-02 08:15:27,535 DEBUG 
[requests.packages.urllib3.connectionpool][GreenThread-5] "POST /v2.0/tokens 
HTTP/1.1" 401 114
2017-01-02 08:15:27,536 DEBUG [keystoneauth.session][GreenThread-5] Request 
returned failure status: 401
2017-01-02 08:15:27,536 INFO [keystonemiddleware.auth_token][GreenThread-5] 
Identity server rejected authorization
2017-01-02 08:15:27,536 WARNING [keystonemiddleware.auth_token][GreenThread-5] 
Identity response: {"error": {"message": "The request you have made requires 
authentication.", "code": 401, "title": "Unauthorized"}}
2017-01-02 08:15:27,536 CRITICAL [keystonemiddleware.auth_token][GreenThread-5] 
Unable to validate token: Identity server rejected authorization necessary to 
fetch token data
2017-01-02 08:15:27,539 DEBUG [gunicorn.error][GreenThread-5] Closing 
connection.


Further the AUTH_URL is set
ubuntu@monasca:/var/log/monasca/api$ echo $OS_AUTH_URL
http://127.0.0.1:35357/v3/

I would like to mention the status of services:
ubuntu@monasca:~$ sudo service monasca-log-api status
monasca-log-api start/running, process 7938

ubuntu@monasca:~$ sudo service monasca-api status
monasca-api start/running, process 21465

ubuntu@monasca:~/devstack$ keystone service list
Ignoring domain related config project_domain_name because identity API version 
is 2.0
Ignoring domain related config user_domain_name because identity API version is 
2.0
Ignoring domain related config project_domain_name because identity API version 
is 2.0
Ignoring domain related config user_domain_name because identity API version is 
2.0
Ignoring domain related config project_domain_name because identity API version 
is 2.0
Ignoring domain related config user_domain_name because identity API version is 
2.0
+--+-++
| ID   | Name| Type   |