[openstack-dev] [Monasca]

2017-01-02 Thread Sanjana Pai Nagarmat
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   |
+--+-++
| 301f29e503c845828ce4a24d61924ded | cinderv3| volumev3   |
| 36ee63e1df644d4780cc2f16e93bc379 | monasca | monitoring |
| 448e665048314cc2af41bbfc99bdf7af | cinderv2| volumev2   |
| 68db6f5f85be4007b0c6550b3fd8468e | neutron | network|
| 7b9313963b094fa0986016adbd6b92fd | cinder  | volume |
| 7fccd72315ba4f6cbd400274054a5c88 | keystone| identity   |
| 8cd5c25a911e468797bad4d709ff1adf | glance  | image  |
| b4c2a0986f674a93b7636d18ef4e81cb | nova| compute|
| f19e24d3633141c4892d10cdead98f20 | nova_legacy | compute_legacy |
+--+-++

Please let me know how I can fix this issue. I want to use monasca logging 
service for my openstack environment.
Thanks in advance.



--Sanjana





__
OpenStack Development Mailing List 

Re: [openstack-dev] [Aodh] Ordering Alarm severity on context

2016-06-13 Thread Sanjana Pai Nagarmat

From: Sanjana Pai Nagarmat
Sent: Tuesday, June 14, 2016 9:46 AM
To: openstack-dev@lists.openstack.org
Subject: [Aodh]

Hi All,

This is with respect to the bug  https://launchpad.net/bugs/1452254 , which 
orders the severity of alarms based on context rather than sorting it 
alphabetically. My code is out for review at 
https://review.openstack.org/#/c/328230 .
I would like to know your opinion, on the approach I have followed to solve the 
bug.



Regards,
Sanjana

__
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


[openstack-dev] [Aodh]

2016-06-13 Thread Sanjana Pai Nagarmat
Hi All,

This is with respect to the bug  https://launchpad.net/bugs/1452254 , which 
orders the severity of alarms based on context rather than sorting it 
alphabetically. My code is out for review at 
https://review.openstack.org/#/c/328230 .
I would like to know your opinion, on the approach I have followed to solve the 
bug.



Regards,
Sanjana

__
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


[openstack-dev] "OpenStack-dev" mailing list

2016-06-13 Thread Sanjana Pai Nagarmat
Email : sanj...@hitachi.co.in

Thanks and Regards,
Sanjana


-Original Message-
From: openstack-dev-requ...@lists.openstack.org 
[mailto:openstack-dev-requ...@lists.openstack.org] 
Sent: Tuesday, June 14, 2016 8:52 AM
To: Sanjana Pai Nagarmat
Subject: Welcome to the "OpenStack-dev" mailing list

Welcome to the OpenStack-dev@lists.openstack.org mailing list!

To post to this list, send your email to:

  openstack-dev@lists.openstack.org

General information about the mailing list is at:

  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

If you ever want to unsubscribe or change your options (eg, switch to or from 
digest mode, change your password, etc.), visit your subscription page at:

  
http://lists.openstack.org/cgi-bin/mailman/options/openstack-dev/sanjana%40hitachi.co.in


You can also make such adjustments via email by sending a message to:

  openstack-dev-requ...@lists.openstack.org

with the word `help' in the subject or body (don't include the quotes), and you 
will get back a message with instructions.

You must know your password to change your options (including changing the 
password, itself) or to unsubscribe.  It is:

  Hitachi1

Normally, Mailman will remind you of your lists.openstack.org mailing list 
passwords once every month, although you can disable this if you prefer.  This 
reminder will also include instructions on how to unsubscribe or change your 
account options.  There is also a button on your options page that will email 
your current password to you.

__
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