[openstack-dev] [Monasca] "The server is currently unavailable. on Monasca service

[Pradip Mukhopadhyay]

Hello,


I am seeing the following issue after installing Monasca recently as a
devstack environment"


stack@scsor0002143001-pradipm:~/devstack$ 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"}


stack@scsor0002143001-pradipm:~/devstack$ openstack user list
+--+---+
| ID   | Name  |
+--+---+
| f29f1814fbc34855ba684a2810434580 | admin |
| a9c0c928caff4345b2aa266a30397487 | demo  |
| f172a9e25d2542c895fbc43d73164a9d | alt_demo  |
| 6cfdec260fe94c4487071f9e7915b359 | nova  |
| 1a66c71e946442f2a061c88cef566c30 | glance|
| bdb1aed519504b249cffd27a2c05f0fa | cinder|
| 5c9cf5cedcb244dbafbe272f691eaf2f | mini-mon  |
| a349c41c99fa447b96d1d2a56b12c3d4 | monasca-agent |
+--+---+


Here is the local.conf that I have used:



# BEGIN DEVSTACK LOCAL.CONF CONTENTS

[[local|localrc]]
ADMIN_PASSWORD=netapp
MYSQL_PASSWORD=$ADMIN_PASSWORD
DATABASE_PASSWORD=$ADMIN_PASSWORD
RABBIT_PASSWORD=$ADMIN_PASSWORD
SERVICE_PASSWORD=$ADMIN_PASSWORD
GUEST_PASSWORD=$ADMIN_PASSWORD
MYSQL_HOST=127.0.0.1
MYSQL_USER=root
RABBIT_HOST=127.0.0.1
SERVICE_TOKEN=111222333444

LOGFILE=$DEST/logs/stack.sh.log
LOGDIR=$DEST/logs
LOG_COLOR=False
SCREEN_LOGDIR=$DEST/logs/screen
LOGDAYS=1

# The following two variables allow switching between Java and Python for
the implementations
# of the Monasca API and the Monasca Persister. If these variables are not
set, then the
# default is to install the Python implementations of both the Monasca API
and the Monasca Persister.

# Uncomment one of the following two lines to choose Java or Python for the
Monasca API.
#MONASCA_API_IMPLEMENTATION_LANG=${MONASCA_API_IMPLEMENTATION_LANG:-java}
MONASCA_API_IMPLEMENTATION_LANG=${MONASCA_API_IMPLEMENTATION_LANG:-python}

# Uncomment of the following two lines to choose Java or Python for the
Monasca Pesister.
#MONASCA_PERSISTER_IMPLEMENTATION_LANG=${MONASCA_PERSISTER_IMPLEMENTATION_LANG:-java}
MONASCA_PERSISTER_IMPLEMENTATION_LANG=${MONASCA_PERSISTER_IMPLEMENTATION_LANG:-python}

MONASCA_METRICS_DB=${MONASCA_METRICS_DB:-influxdb}
# MONASCA_METRICS_DB=${MONASCA_METRICS_DB:-vertica}

# This line will enable all of Monasca.
enable_plugin monasca-api git://git.openstack.org/openstack/monasca-api







--pradip
__
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] Alarm generation from a sequence of events

[Pradip Mukhopadhyay]

Thanks, Roland. Makes sense. I agree.


Just tossing the idea: is there a way to validate a temporal causal
relationship among events such that in case e1, followed by e2, followed by
e3 *implies *a condition C to fail/pass - and generates an alarm.


Thanks,
Pradip



On Tue, Feb 16, 2016 at 8:52 PM, Hochmuth, Roland M <roland.hochm...@hpe.com
> wrote:

> Hi Pradip, The focus of that blueprint is to create metrics from logs in
> the LogStash component and then publish them to the Kafka metrics topic.
> The Monasca Threshold Engine can then be used to alarm on the metrics. For
> example, if the number of errors in a log file exceeds some amount, alarm
> and send a notification.
>
> Regards --Roland
>
> From: Pradip Mukhopadhyay <pradip.inte...@gmail.com pradip.inte...@gmail.com>>
> Reply-To: OpenStack List <openstack-dev@lists.openstack.org openstack-dev@lists.openstack.org>>
> Date: Monday, February 15, 2016 at 9:58 AM
> To: OpenStack List <openstack-dev@lists.openstack.org openstack-dev@lists.openstack.org>>
> Subject: [openstack-dev] [Monasca] Alarm generation from a sequence of
> events
>
> Hello,
>
>
> We come across the following interesting BP in the last weekly meeting:
> https://blueprints.launchpad.net/monasca/+spec/alarmsonlogs
>
>
> Understood how the non-periodic nature of log events to be taken care of
> (by introducing period = -1 in value-meta).
>
>
> Just wondering can it be possible to use this to satisfy the following
> usecase:
> Given a causal or non-causal sequence of events a, b, c – can we determine
> that a condition ‘p’ has occurred and alarm on that.
>
>
>
> Thanks,
> Pradip
>
>
>
> __
> 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 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] [Installation] RHEL-7 devstack installation failed in bootstrap_keystone

[Pradip Mukhopadhyay]

Hello,

In a RHEL-7, getting this error:

2016-02-05 11:08:00.385 | Discovering versions from the identity service
failed when creating the password plugin. Attempting to determine version
from URL.
2016-02-05 11:08:00.385 | Could not determine a suitable URL for the plugin
2016-02-05 11:08:00.403 | +
/opt/stack/devstack/lib/keystone:bootstrap_keystone:L617:   token_id=
2016-02-05 11:08:00.403 | +
/opt/stack/devstack/lib/keystone:bootstrap_keystone:L1:   exit_trap
2016-02-05 11:08:00.403 | + ./stack.sh:exit_trap:L474:   local r=1
2016-02-05 11:08:00.404 | ++ ./stack.sh:exit_trap:L475:   jobs -p
2016-02-05 11:08:00.404 | + ./stack.sh:exit_trap:L475:   jobs=
2016-02-05 11:08:00.404 | + ./stack.sh:exit_trap:L478:   [[ -n '' ]]
2016-02-05 11:08:00.404 | + ./stack.sh:exit_trap:L484:   kill_spinner
2016-02-05 11:08:00.404 | + ./stack.sh:kill_spinner:L370:   '[' '!' -z ''
']'
2016-02-05 11:08:00.404 | + ./stack.sh:exit_trap:L486:   [[ 1 -ne 0 ]]
2016-02-05 11:08:00.404 | + ./stack.sh:exit_trap:L487:   echo 'Error on
exit'
2016-02-05 11:08:00.404 | Error on exit
2016-02-05 11:08:00.404 | + ./stack.sh:exit_trap:L488:   generate-subunit
1454670313 167 fail
2016-02-05 11:08:00.670 | + ./stack.sh:exit_trap:L489:   [[ -z
/opt/stack/logs ]]
2016-02-05 11:08:00.670 | + ./stack.sh:exit_trap:L492:
/opt/stack/devstack/tools/worlddump.py -d /opt/stack/logs
2016-02-05 11:08:00.955 | + ./stack.sh:exit_trap:L498:   exit 1


[stack@scson0001301001 devstack]$ uname -a
Linux scson0001301001.nb.openenglab.netapp.com 3.10.0-229.el7.x86_64 #1 SMP
Thu Jan 29 18:37:38 EST 2015 x86_64 x86_64 x86_64 GNU/Linux



Any idea how to overcome it?


Thanks,
Pradip
__
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] [Monasca] alarm-definition-list is failing with "service unavailable"

[Pradip Mukhopadhyay]

Hello,


Seeing the alarm-definition-list is returning "service unavailable" for
admin user:


stack@ubuntu:~/devstack$ monasca --os-username admin --os-password
secretadmin --os-project-name admin alarm-definition-list
ERROR (exc:65) exception: {
"title": "Service unavailable",
"description": ""
}
HTTPException code=500 message={
"title": "Service unavailable",
"description": ""
}


However can see other APIs like notification listing etc. working fine.

stack@ubuntu:~/devstack$ monasca --os-username admin --os-password
secretadmin --os-project-name admin notification-list
+---+--+---++
| name  | id   | type  |
address|
+---+--+---++
| pradipm_email | bf60996d-d500-4b59-b42f-a942e9121859 | EMAIL | email_id |
+---+--+---++



The following changes we did to make it work for 'admin' user:

Do the following changes:
1. /opt/stack/monasca-api/java/src/main/resources/api-config.yml  --- add
'admin' in 'defaultAuthorizedRoles'
2./etc/monasca/api-config.conf  --- add 'admin' in default_authorized_roles
3. sudo service monasca-api restart
4. sudo service monasca-thresh restart
5. sudo service monasca-agent restart




Any help will be appreciated.



Thanks,
Pradip
__
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] [Horizon][Monasca] Launching Graphana UI from Monitoring tab in Monasca plugin for Horizon

[Pradip Mukhopadhyay]

Hello,


We followed the https://github.com/openstack/monasca-ui/ to integrate the
plugin for Horizon. The Monitoring tab is coming in left side navigation
perfectly and working as expected. Only problem is: when we're trying to
launch the Graphana UI, it is failing with the following trace:


Page not found (404)
Request Method: GET
Request URL: http://10.74.150.152:8000/grafana/index.html

Using the URLconf defined in openstack_dashboard.urls, Django tried these
URL patterns, in this order:

   1. ^$ [name='splash']
   2. ^api/
   3. ^home/$ [name='user_home']
   4. ^i18n/js/(?P\S+?)/$ [name='jsi18n']
   5. ^i18n/setlang/$ [name='set_language']
   6. ^i18n/
   7. ^jasmine-legacy/$ [name='jasmine_tests']
   8. ^jasmine/.*?$
   9. ^identity/
   10. ^admin/
   11. ^developer/
   12. ^project/
   13. ^settings/
   14. ^monitoring/
   15. ^auth/
   16. ^static\/(?P.*)$
   17. ^media\/(?P.*)$
   18. ^500/$

The current URL, grafana/index.html, didn't match any of these.



Any pointer of how to solve it, if any, would be highly appreciated.




Thanks in advance,
Pradip
__
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] [keystone] URLs are not reported in the endpoint listing

[Pradip Mukhopadhyay]

Hello,


I did a stacking recently, noticing a behavior:

eystone --os-username admin --os-password secretadmin --os-tenant-name
admin --os-auth-url http://host:5000/v2.0 endpoint-list

Returns null URLs for public/internal/admin.


+--+---+---+-+--+--+
|id|   region  | publicurl | internalurl |
adminurl |service_id|
+--+---+---+-+--+--+
| 169f7f5090ea442c8ae534d6cd38c484 | RegionOne |   |
|  | 8d30999ba36943359b4e7c4ae4f0a15c |
| 255f7316074d4aecb34b69e3f28309c1 | RegionOne |   |
|  | f26931e1fa43438da4c32fe530f33796 |


Some of the keystone CLIs are not working. e.g. user-list is working. But
not the others, say service-list/role-list. It is returning : The resource
could not be found. (HTTP 404) (Request-ID:
req-b52eace0-b65a-4ba3-afb9-616689a0833e)


Not sure what I have messed up.


Any help would be solicited.




--pradip
__
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] [keystone] URLs are not reported in the endpoint listing

[Pradip Mukhopadhyay]

Thanks. openstack commands are working fine.

I am trying with Monasca which is using keystone v3 for auth.


--pradip





On Tue, Feb 2, 2016 at 6:13 PM, Matt Fischer <m...@mattfischer.com> wrote:

> I've seen similar odd behavior when using the Keystone client to try to
> list endpoints created using the v3 API (via puppet). Try using the
> openstack client  and the v3 endpoint. Be sure to set --os-api-version 3.
> On Feb 2, 2016 3:06 AM, "Pradip Mukhopadhyay" <pradip.inte...@gmail.com>
> wrote:
>
>> Hello,
>>
>>
>> I did a stacking recently, noticing a behavior:
>>
>> eystone --os-username admin --os-password secretadmin --os-tenant-name
>> admin --os-auth-url http://host:5000/v2.0 endpoint-list
>>
>> Returns null URLs for public/internal/admin.
>>
>>
>>
>> +--+---+---+-+--+--+
>> |id|   region  | publicurl | internalurl
>> | adminurl |service_id|
>>
>> +--+---+---+-+--+--+
>> | 169f7f5090ea442c8ae534d6cd38c484 | RegionOne |   |
>> |  | 8d30999ba36943359b4e7c4ae4f0a15c |
>> | 255f7316074d4aecb34b69e3f28309c1 | RegionOne |   |
>> |  | f26931e1fa43438da4c32fe530f33796 |
>>
>>
>> Some of the keystone CLIs are not working. e.g. user-list is working. But
>> not the others, say service-list/role-list. It is returning : The resource
>> could not be found. (HTTP 404) (Request-ID:
>> req-b52eace0-b65a-4ba3-afb9-616689a0833e)
>>
>>
>> Not sure what I have messed up.
>>
>>
>> Any help would be solicited.
>>
>>
>>
>>
>> --pradip
>>
>>
>>
>>
>> __
>> 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 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 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] [Monasca] Allowing 'admin' user and 'admin' project full access to Monasca

[Pradip Mukhopadhyay]

Hello,


Following [1]
, I set up
Monasca (with all other services). I get the 'mini-mon' project;  'monasca'
service; 'monasca-agent', 'monasca-user' role and 'mini-mon',
'monasca-agent' users.

I can do all expected operations (alarm defn, alarm lising, metric push,
notifications) using mini-mon user and 'mini-mon' project as follows:

#monasca --os-username mini-mon --os-password password --os-project-name
mini-mon  notification-create pradipm_email_try EMAIL 



However, I am getting an error when trying to do the same for 'admin' user
and 'admin' project:

$ monasca --os-username admin --os-password secretadmin --os-project-name
admin  notification-create pradipm_email EMAIL <...>
{
  "description": "Tenant ID is missing a required role to access this
service",
  "title": "Forbidden"
}




How can I make it work for 'admin' user also?



There are following three files. Do I need to add 'admin' role in

1. /opt/stack/monasca-api/devstack/files/monasca-api/api-config.yml  //
admin is there (defaultAuthorizedRoles)

2. /opt/stack/monasca-api/java/src/main/resources/api-config.yml  //
admin not there

3. /etc/monasca/api-config.conf  // admin not there in
default_authorized_roles clause



Any help will be solicited.


Thanks,
Pradip
__
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] Anomaly & Prediction Engine

[Pradip Mukhopadhyay]

(Apology for ignorance) - can anyone from Monasca please point any related
documentation about the APE micro-service which (whatever be the state
currently it is) currently we have in Monasca? Its in python or in Java?


--pradip


On Fri, Jan 22, 2016 at 4:12 PM, Osanai, Hisashi <
osanai.hisa...@jp.fujitsu.com> wrote:

>
> Monasca folks,
>
> We discussed about Anomaly & Prediction Engine in this week's
> irc meeting and decided we would exchange info using this list.
> I'm really interested in having this functionality but the status
> is prototype now.
>
> We know that there are a lot of related tech around it and the tech
> has been growing rapidly.
>
> Let's start to discuss about how to approach this. What do you think?
>
> Best Regards,
> Hisashi Osanai
>
> __
> 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 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] collectd-Monasca Python plugin

[Pradip Mukhopadhyay]

One question.  After pushing the data to Monasca (gathering from collectd)
- what else could potentially be done on this data to get some interesting
inside about the system?

Of course, specially for legacy system cases, it would be an awesome
addition (similar line of Ceilometer - I guess).



--pradip



On Fri, Jan 22, 2016 at 3:26 PM, Alonso Hernandez, Rodolfo <
rodolfo.alonso.hernan...@intel.com> wrote:

> Hello Roland:
>
> >> How would you map the metric names and fields in collectd to a monasa
> name and dimensions?
> I'm on it. I'm reading the API from collectd and monasca, to figure out
> how to connect them. Next week I'll upload a spec and I'll wait for your
> comments.
>
> Thank you for your interest!
>
> Regards.
>
>
> -Original Message-
> From: Hochmuth, Roland M [mailto:roland.hochm...@hpe.com]
> Sent: Thursday, January 21, 2016 11:53 PM
> To: OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [Monasca] collectd-Monasca Python plugin
>
> Hi Rodolfo, I think this would be useful work. Collectd has a lot of
> metrics that aren't supported in Monasca yet.
>
> How would you map the metric names and fields in collectd to a monasa name
> and dimensions?
>
> Regards --Roland
>
> From: Jaesuk Ahn >
> Reply-To: OpenStack List >
> Date: Thursday, January 21, 2016 at 4:49 AM
> To: OpenStack List >
> Subject: Re: [openstack-dev] [Monasca] collectd-Monasca Python plugin
>
> We are looking into similar plan to have collectd-plugin for Monasca.
>
> There are some env. we cannot deploy monasca agent, but want to put data
> into Monasca. In addition, we wanted to use easily accepted collectd for
> gathering data from legacy env.
>
> It will be interesting to see more detail about your plan.
>
> Cheers,
>
>
> ---
> Jaesuk Ahn
> SDI Tech. Lab, SKT
>
>
> 2016년 1월 21일 (목) 19:11, Alonso Hernandez, Rodolfo <
> rodolfo.alonso.hernan...@intel.com rodolfo.alonso.hernan...@intel.com>>님이 작성:
> Hello:
>
> We are doing (or at least planning) a collectd-Monasca Python plugin. This
> plugin will receive the data from RPC calls form collectd and will write
> this data in Monasca, using statsd API.
>
> My question is: do you think this development could be useful? Does it
> worth? Any comment?
>
> Thank you in advance. Regards.
>
> Rodolfo Alonso.
> --
> Intel Research and Development Ireland Limited Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263
>
>
> This e-mail and any attachments may contain confidential material for the
> sole use of the intended recipient(s). Any review or distribution by others
> is strictly prohibited. If you are not the intended recipient, please
> contact the sender and delete all copies.
>
>
> __
> 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 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
> --
> Intel Research and Development Ireland Limited
> Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263
>
>
> This e-mail and any attachments may contain confidential material for the
> sole
> use of the intended recipient(s). Any review or distribution by others is
> strictly prohibited. If you are not the intended recipient, please contact
> the
> sender and delete all copies.
> __
> 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 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] Anomaly & Prediction Engine

[Pradip Mukhopadhyay]

Thanks Hisashi.

I am sorry - by APE - I meant Anamoly and Prediction engine only.

Thanks a lot for the link.


--pradip




On Sat, Jan 23, 2016 at 12:18 AM, Hochmuth, Roland M <
roland.hochm...@hpe.com> wrote:

> Hi Pradip, There are several components in Monasca. I'm not sure what the
> acronym APE is stands for. Is that Anomaly and Prediction Engine? The list
> of components in Monasca and the languages that they are implemented in is
> as follows:
>
>   1.  API: Both Java and Python.
>   2.  Persister: Both Java and Python
>   3.  Threshold Engine: Java only
>   4.  Notification Engine: Python
>   5.  python-monascaclient: Python
>
> Over the past few months we developed around 120 Tempest tests that test
> the entire API, developed a plugin for Tempest and integrated in the
> OpenStack CI systems. The Tempest tests run to 100% completion against both
> APIs and Persisters.
>
> There was a Python implementation of an anomaly engine developed that was
> more of a proof-of-concept. It is at,
> https://github.com/roland-hochmuth/monasca-anomaly.
>
> Regards --Roland
>
>
> From: Pradip Mukhopadhyay <pradip.inte...@gmail.com pradip.inte...@gmail.com>>
> Reply-To: OpenStack List <openstack-dev@lists.openstack.org openstack-dev@lists.openstack.org>>
> Date: Friday, January 22, 2016 at 5:18 AM
> To: OpenStack List <openstack-dev@lists.openstack.org openstack-dev@lists.openstack.org>>
> Subject: Re: [openstack-dev] [monasca] Anomaly & Prediction Engine
>
> (Apology for ignorance) - can anyone from Monasca please point any related
> documentation about the APE micro-service which (whatever be the state
> currently it is) currently we have in Monasca? Its in python or in Java?
>
>
> --pradip
>
>
> On Fri, Jan 22, 2016 at 4:12 PM, Osanai, Hisashi <
> osanai.hisa...@jp.fujitsu.com<mailto:osanai.hisa...@jp.fujitsu.com>>
> wrote:
>
> Monasca folks,
>
> We discussed about Anomaly & Prediction Engine in this week's
> irc meeting and decided we would exchange info using this list.
> I'm really interested in having this functionality but the status
> is prototype now.
>
> We know that there are a lot of related tech around it and the tech
> has been growing rapidly.
>
> Let's start to discuss about how to approach this. What do you think?
>
> Best Regards,
> Hisashi Osanai
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> 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 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] Enabling Graphana GUI from Horizon

[Pradip Mukhopadhyay]

Thanks. I can able to see the 'Monitoring' tab in the Horizon UI.

However not able to launch the Monasca UI (Graphana). When trying to launch
it, getting a "Page not found error:" :


Using the URLconf defined in openstack_dashboard.urls, Django tried these
URL patterns, in this order:

   1. ^$ [name='splash']
   2. ^api/
   3. ^home/$ [name='user_home']
   4. ^i18n/js/(?P\S+?)/$ [name='jsi18n']
   5. ^i18n/setlang/$ [name='set_language']
   6. ^i18n/
   7. ^jasmine-legacy/$ [name='jasmine_tests']
   8. ^jasmine/.*?$
   9. ^settings/
   10. ^monitoring/
   11. ^developer/
   12. ^admin/
   13. ^identity/
   14. ^project/
   15. ^auth/
   16. ^static\/(?P.*)$
   17. ^media\/(?P.*)$
   18. ^500/$

The current URL, grafana/index.html, didn't match any of these.


Any help would be good.


Thanks,
Pradip









On Tue, Jan 12, 2016 at 10:42 PM, Pradip Mukhopadhyay <
pradip.inte...@gmail.com> wrote:

> Thanks! So I can temporarily follow the step to enable it in my setup.
>
>
> --pradip
>
>
> On Tue, Jan 12, 2016 at 9:45 PM, Lin Hua Cheng <os.lch...@gmail.com>
> wrote:
>
>>
>> You would need to propose the new feature in the monasca-ui [1], which is
>> the horizon plugin for displaying monasca dashboard.
>>
>> -Lin
>>
>> [1] https://github.com/openstack/monasca-ui/
>>
>> On Tue, Jan 12, 2016 at 3:32 AM, Pradip Mukhopadhyay <
>> pradip.inte...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>>
>>> We're using the following fullsetup to install Monasca (python):
>>>
>>> https://github.com/openstack/monasca-api/tree/master/devstack
>>>
>>>
>>>
>>> Most likely we need to do something more to see the "Monitoring" tab in
>>> left hand side that takes us to Monasca graphana GUI.
>>>
>>>
>>> Can anyone please point me?
>>>
>>>
>>> We do see it when do a vagrant setup with mini-mon and devstack VMs.
>>>
>>>
>>> Any help is highly solicited.
>>>
>>>
>>> --pradip
>>>
>>>
>>>
>>> __
>>> 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 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 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] [Monasca] Enabling Graphana GUI from Horizon

[Pradip Mukhopadhyay]

Hello,


We're using the following fullsetup to install Monasca (python):

https://github.com/openstack/monasca-api/tree/master/devstack



Most likely we need to do something more to see the "Monitoring" tab in
left hand side that takes us to Monasca graphana GUI.


Can anyone please point me?


We do see it when do a vagrant setup with mini-mon and devstack VMs.


Any help is highly solicited.


--pradip
__
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] Enabling Graphana GUI from Horizon

[Pradip Mukhopadhyay]

Thanks! So I can temporarily follow the step to enable it in my setup.


--pradip


On Tue, Jan 12, 2016 at 9:45 PM, Lin Hua Cheng <os.lch...@gmail.com> wrote:

>
> You would need to propose the new feature in the monasca-ui [1], which is
> the horizon plugin for displaying monasca dashboard.
>
> -Lin
>
> [1] https://github.com/openstack/monasca-ui/
>
> On Tue, Jan 12, 2016 at 3:32 AM, Pradip Mukhopadhyay <
> pradip.inte...@gmail.com> wrote:
>
>> Hello,
>>
>>
>> We're using the following fullsetup to install Monasca (python):
>>
>> https://github.com/openstack/monasca-api/tree/master/devstack
>>
>>
>>
>> Most likely we need to do something more to see the "Monitoring" tab in
>> left hand side that takes us to Monasca graphana GUI.
>>
>>
>> Can anyone please point me?
>>
>>
>> We do see it when do a vagrant setup with mini-mon and devstack VMs.
>>
>>
>> Any help is highly solicited.
>>
>>
>> --pradip
>>
>>
>> __
>> 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 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 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] [cinder][python-client-api] Retrieve host-name attribute of Cinder Volume

[Pradip Mukhopadhyay]

Hello,


>From CLI, I can see the host-name in the cinder show command as follows:

| os-vol-host-attr:host |  openstack4@mySCSIBackend#pool1
|

How this info can be accessed from the cinder python client?

I can access other information (id, size, name etc.) as follows:

>>> volumes = cinder.volumes.list()

>>> volumes

[]

>>> volumes[0].id

u'e8be1df5-64fb-43fa-aacd-9bebba17fba5'

>>> volumes[0].volume_type

u'iscsi_1'



Thanks,
Pradip
__
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] [cinder][python-client-api] Retrieve host-name attribute of Cinder Volume

[Pradip Mukhopadhyay]

Thanks, Yuriy.

My question was: how can I retrieve the "host@backend#pool" from the
pythonclient API of volume listing? Once I have that, I should use this
method to extract the pool-name.

But how can I access this info? CLI is showing this as in the following
field:

stack@openstack4:~/devstack$ cinder show
e8be1df5-64fb-43fa-aacd-9bebba17fba5
+---+--+
|Property   |
Value |
+---+--+
|  attachments  |
[]  |
|   availability_zone   |
nova |
|bootable   |
false |
|  consistencygroup_id  |
None |
|   created_at  |
2016-01-06T14:21:32.00  |
|  description  |
None |
|   encrypted   |
False |
|   id  |
e8be1df5-64fb-43fa-aacd-9bebba17fba5 |
|metadata   |
{}  |
|migration_status   |
None |
|  multiattach  |
False |
|  name |
None |
| *os-vol-host-attr:host |  openstack4@SCSIBackend#pool1*
|
| os-vol-mig-status-attr:migstat|
None |
| os-vol-mig-status-attr:name_id|
None |
|  os-vol-tenant-attr:tenant_id |
4713f79411844a29b3f53d5fd7502784   |
|   os-volume-replication:driver_data   |
None |
| os-volume-replication:extended_status |
None |
|   replication_status  |
disabled   |
|  size |
1   |
|  snapshot_id  |
None |
|  source_volid |
None |
| status|
available   |
|   updated_at  |
2016-01-06T14:21:34.00  |
|user_id|
89b4af10bc1a473caff22384c844bc6f   |
|  volume_type  |
iscsi_1|
+---+--+



Now in python client API, I am not able to get that field :(



>>> volumes = cinder.volumes.list()

>>> volumes

[]

>>> type(volumes[0])


>>> volumes[0].id

u'e8be1df5-64fb-43fa-aacd-9bebba17fba5'

>>> volumes[0].host
Traceback (most recent call last):
  File "", line 1, in 
  File
"/usr/local/lib/python2.7/dist-packages/cinderclient/openstack/common/apiclient/base.py",
line 464, in __getattr__
raise AttributeError(k)
AttributeError: host
>>> volumes[0].os-vol-host-attr
Traceback (most recent call last):
  File "", line 1, in 
  File
"/usr/local/lib/python2.7/dist-packages/cinderclient/openstack/common/apiclient/base.py",
line 464, in __getattr__
raise AttributeError(k)
AttributeError: os




Essentially what is the way to get the attribute from the API?




Thanks,

Pradip



On Wed, Jan 6, 2016 at 9:28 PM, Yuriy Nesenenko <ynesene...@mirantis.com>
wrote:

> Sorry, of course this
> https://github.com/openstack/cinder/blob/master/cinder/volume/utils.py#L575
>
> On Wed, Jan 6, 2016 at 5:57 PM, Yuriy Nesenenko <ynesene...@mirantis.com>
> wrote:
>
>> You can use this function
>> https://github.com/openstack/cinder/blob/master/cinder/volume/utils.py#L5
>>
>> On Wed, Jan 6, 2016 at 5:44 PM, Pradip Mukhopadhyay <
>> pradip.inte...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>>
>>> From CLI, I can see the host-name in the cinder show command as follows:
>>>
>>> | os-vol-host-attr:host |  openstack4@mySCSIBackend#pool1
>>> |
>>>
>>> How this info can be accessed from the cinder python client?
>>>
>>> I can access other information (id, size, name etc.) as follows:
>>>
>>> >>> volumes = cinder.volumes.list()
>>>
>>> >>> volumes
>>>
>>> []
>>>
>>> >>> volumes[0].id
>>>
>>> u'e8be1df5-64fb-43fa-aacd-9bebba17fba5'
>>>
>>> >>> volumes[0].volume_type
>>>
>>> u'iscsi_1'
>>>
>>>
>>>
>>> Thanks,
>>> Pradip
>>>
>>>
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscrib

Re: [openstack-dev] [cinder][python-client-api] Retrieve host-name attribute of Cinder Volume

[Pradip Mukhopadhyay]

Thanks a ton Duncan. It's just awesome.

>>> volumes[0].__dict__['os-vol-host-attr:host']
u'openstack4@cmodeSCSIBackend#pool1'
>>>



--pradip



On Thu, Jan 7, 2016 at 12:53 AM, Duncan Thomas <duncan.tho...@gmail.com>
wrote:

> Try client.volumes..get(id).__dict__['
>
> *os-vol-host-attr:host'] *
>
> *Ugly, but it seems to work*
>
> On 6 January 2016 at 18:20, Pradip Mukhopadhyay <pradip.inte...@gmail.com>
> wrote:
>
>> Thanks, Yuriy.
>>
>> My question was: how can I retrieve the "host@backend#pool" from the
>> pythonclient API of volume listing? Once I have that, I should use this
>> method to extract the pool-name.
>>
>> But how can I access this info? CLI is showing this as in the following
>> field:
>>
>> stack@openstack4:~/devstack$ cinder show
>> e8be1df5-64fb-43fa-aacd-9bebba17fba5
>>
>> +---+--+
>> |Property   |
>> Value |
>>
>> +---+--+
>> |  attachments  |
>> []  |
>> |   availability_zone   |
>> nova |
>> |bootable   |
>> false |
>> |  consistencygroup_id  |
>> None |
>> |   created_at  |
>> 2016-01-06T14:21:32.00  |
>> |  description  |
>> None |
>> |   encrypted   |
>> False |
>> |   id  |
>> e8be1df5-64fb-43fa-aacd-9bebba17fba5 |
>> |metadata   |
>> {}  |
>> |migration_status   |
>> None |
>> |  multiattach  |
>> False |
>> |  name |
>> None |
>> | *os-vol-host-attr:host |  openstack4@SCSIBackend#pool1*
>> |
>> | os-vol-mig-status-attr:migstat|
>> None |
>> | os-vol-mig-status-attr:name_id|
>> None |
>> |  os-vol-tenant-attr:tenant_id |
>> 4713f79411844a29b3f53d5fd7502784   |
>> |   os-volume-replication:driver_data   |
>> None |
>> | os-volume-replication:extended_status |
>> None |
>> |   replication_status  |
>> disabled   |
>> |  size |
>> 1   |
>> |  snapshot_id  |
>> None |
>> |  source_volid |
>> None |
>> | status|
>> available   |
>> |   updated_at  |
>> 2016-01-06T14:21:34.00  |
>> |user_id|
>> 89b4af10bc1a473caff22384c844bc6f   |
>> |  volume_type  |
>> iscsi_1|
>>
>> +---+--+
>>
>>
>>
>> Now in python client API, I am not able to get that field :(
>>
>>
>>
>> >>> volumes = cinder.volumes.list()
>>
>> >>> volumes
>>
>> []
>>
>> >>> type(volumes[0])
>> 
>>
>> >>> volumes[0].id
>>
>> u'e8be1df5-64fb-43fa-aacd-9bebba17fba5'
>>
>> >>> volumes[0].host
>> Traceback (most recent call last):
>>   File "", line 1, in 
>>   File
>> "/usr/local/lib/python2.7/dist-packages/cinderclient/openstack/common/apiclient/base.py",
>> line 464, in __getattr__
>> raise AttributeError(k)
>> AttributeError: host
>> >>> volumes[0].os-vol-host-attr
>> Traceback (most recent call last):
>>   File "", line 1, in 
>>   File
>> "/usr/local/lib/python2.7/dist-packages/cinderclient/openstack/common/apiclient/base.py",
>> line 464, in __getattr__
>> raise AttributeError(k)
>> AttributeError: os
>>
>>
>>
>>
>> Essentially what is the way to get the attribute from the API?
>>
>>
>>
>>
>> Thanks,
>>
>> Pradip
>>
>>
>>
>> On Wed, Jan 6, 2016 at 9:28 PM, Yuriy Nesenenko <ynesene...@mirantis.com>
>

[openstack-dev] [cinder] oslo_config.PortOp is undefined

[Pradip Mukhopadhyay]

Hello,


I have a devstack created on 12/22/15. Just seeing that (after a vacation)
it stops working.

Tried to restart the cinder services, getting the error:

stack@openstack4:~/devstack$ /usr/local/bin/cinder-api --config-file
/etc/cinder/cinder.conf & echo $! >/opt/stack/status/stack/c-api.pid; fg ||
echo "c-api failed to start" | tee "/opt/stack/status/stack/c-api.failure"
[1] 23828
/usr/local/bin/cinder-api --config-file /etc/cinder/cinder.conf
Traceback (most recent call last):
  File "/usr/local/bin/cinder-api", line 6, in 
from cinder.cmd.api import main
  File "/opt/stack/cinder/cinder/cmd/api.py", line 37, in 
from cinder import service
  File "/opt/stack/cinder/cinder/service.py", line 65, in 
cfg.PortOpt('osapi_volume_listen_port',
AttributeError: 'module' object has no attribute 'PortOpt'
c-api failed to start
stack@openstack4:~/devstack$



Looks like something to do with oslo_config.PortOpt.

I dont have any port mentioned in cinder.conf (tried also specifying 8070 -
same failure).

When commenting out the lines, getting the following for rabbit:

2016-01-05 05:44:10.421 TRACE cinder plugin = ep.resolve()
2016-01-05 05:44:10.421 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line
2386, in resolve
2016-01-05 05:44:10.421 TRACE cinder module =
__import__(self.module_name, fromlist=['__name__'], level=0)
2016-01-05 05:44:10.421 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/impl_rabbit.py",
line 94, in 
2016-01-05 05:44:10.421 TRACE cinder cfg.PortOpt('rabbit_port',
2016-01-05 05:44:10.421 TRACE cinder AttributeError: 'module' object has no
attribute 'PortOpt'
2016-01-05 05:44:10.421 TRACE cinder



Any workaround (unstack and stacking want to avoid) would be hightly
appreciated.



Thanks in advance,
Pradip
__
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] [cinder] oslo_config.PortOp is undefined

[Pradip Mukhopadhyay]

I did not do anything specific.

Oslo Config has IntOpt, not PortOpt.

Any clue how can I upgrade oslo.config?



--pradip



On Tue, Jan 5, 2016 at 4:43 PM, Julien Danjou <jul...@danjou.info> wrote:

> On Tue, Jan 05 2016, Pradip Mukhopadhyay wrote:
>
> Upgrade oslo.config?
>
> > Hello,
> >
> >
> > I have a devstack created on 12/22/15. Just seeing that (after a
> vacation)
> > it stops working.
> >
> > Tried to restart the cinder services, getting the error:
> >
> > stack@openstack4:~/devstack$ /usr/local/bin/cinder-api --config-file
> > /etc/cinder/cinder.conf & echo $! >/opt/stack/status/stack/c-api.pid; fg
> ||
> > echo "c-api failed to start" | tee
> "/opt/stack/status/stack/c-api.failure"
> > [1] 23828
> > /usr/local/bin/cinder-api --config-file /etc/cinder/cinder.conf
> > Traceback (most recent call last):
> >   File "/usr/local/bin/cinder-api", line 6, in 
> > from cinder.cmd.api import main
> >   File "/opt/stack/cinder/cinder/cmd/api.py", line 37, in 
> > from cinder import service
> >   File "/opt/stack/cinder/cinder/service.py", line 65, in 
> > cfg.PortOpt('osapi_volume_listen_port',
> > AttributeError: 'module' object has no attribute 'PortOpt'
> > c-api failed to start
> > stack@openstack4:~/devstack$
> >
> >
> >
> > Looks like something to do with oslo_config.PortOpt.
> >
> > I dont have any port mentioned in cinder.conf (tried also specifying
> 8070 -
> > same failure).
> >
> > When commenting out the lines, getting the following for rabbit:
> >
> > 2016-01-05 05:44:10.421 TRACE cinder plugin = ep.resolve()
> > 2016-01-05 05:44:10.421 TRACE cinder   File
> > "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line
> > 2386, in resolve
> > 2016-01-05 05:44:10.421 TRACE cinder module =
> > __import__(self.module_name, fromlist=['__name__'], level=0)
> > 2016-01-05 05:44:10.421 TRACE cinder   File
> >
> "/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/impl_rabbit.py",
> > line 94, in 
> > 2016-01-05 05:44:10.421 TRACE cinder cfg.PortOpt('rabbit_port',
> > 2016-01-05 05:44:10.421 TRACE cinder AttributeError: 'module' object has
> no
> > attribute 'PortOpt'
> > 2016-01-05 05:44:10.421 TRACE cinder
> >
> >
> >
> > Any workaround (unstack and stacking want to avoid) would be hightly
> > appreciated.
> >
> >
> >
> > Thanks in advance,
> > Pradip
> >
> >
>
> --
> Julien Danjou
> # Free Software hacker
> # https://julien.danjou.info
>
__
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] [cinder] oslo_config.PortOp is undefined

[Pradip Mukhopadhyay]

After upgrading all the oslo.config, oslo.service and oslo.log, now c-sch
and c-vol running well. Buit c-api is failing with this stack-trace:

stack@openstack4:~/devstack$ screen -x
2016-01-05 06:44:18.544 TRACE cinder return
self.object_type.invoke(self)
2016-01-05 06:44:18.544 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
144, in invoke
2016-01-05 06:44:18.544 TRACE cinder **context.local_conf)
2016-01-05 06:44:18.544 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/paste/deploy/util.py", line 58, in
fix_call
2016-01-05 06:44:18.544 TRACE cinder reraise(*exc_info)
2016-01-05 06:44:18.544 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/paste/deploy/compat.py", line 23,
in reraise
2016-01-05 06:44:18.544 TRACE cinder exec('raise t, e, tb', dict(t=t,
e=e, tb=tb))
2016-01-05 06:44:18.544 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/paste/deploy/util.py", line 55, in
fix_call
2016-01-05 06:44:18.544 TRACE cinder val = callable(*args, **kw)
2016-01-05 06:44:18.544 TRACE cinder   File
"/opt/stack/cinder/cinder/api/__init__.py", line 38, in root_app_factory
2016-01-05 06:44:18.544 TRACE cinder return
paste.urlmap.urlmap_factory(loader, global_conf, **local_conf)
2016-01-05 06:44:18.544 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/paste/urlmap.py", line 31, in
urlmap_factory
2016-01-05 06:44:18.544 TRACE cinder app = loader.get_app(app_name,
global_conf=global_conf)
2016-01-05 06:44:18.544 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
350, in get_app
2016-01-05 06:44:18.544 TRACE cinder name=name,
global_conf=global_conf).create()
2016-01-05 06:44:18.544 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
710, in create
2016-01-05 06:44:18.544 TRACE cinder return
self.object_type.invoke(self)
2016-01-05 06:44:18.544 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
144, in invoke
2016-01-05 06:44:18.544 TRACE cinder **context.local_conf)
2016-01-05 06:44:18.544 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/paste/deploy/util.py", line 58, in
fix_call
2016-01-05 06:44:18.544 TRACE cinder reraise(*exc_info)
2016-01-05 06:44:18.544 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/paste/deploy/compat.py", line 23,
in reraise
2016-01-05 06:44:18.544 TRACE cinder exec('raise t, e, tb', dict(t=t,
e=e, tb=tb))
2016-01-05 06:44:18.544 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/paste/deploy/util.py", line 55, in
fix_call
2016-01-05 06:44:18.544 TRACE cinder val = callable(*args, **kw)
2016-01-05 06:44:18.544 TRACE cinder   File
"/opt/stack/cinder/cinder/api/middleware/auth.py", line 55, in
pipeline_factory
2016-01-05 06:44:18.544 TRACE cinder filters = [loader.get_filter(n)
for n in pipeline[:-1]]
2016-01-05 06:44:18.544 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
354, in get_filter
2016-01-05 06:44:18.544 TRACE cinder name=name,
global_conf=global_conf).create()
2016-01-05 06:44:18.544 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
710, in create
2016-01-05 06:44:18.544 TRACE cinder return
self.object_type.invoke(self)
2016-01-05 06:44:18.544 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
161, in invoke
2016-01-05 06:44:18.544 TRACE cinder context.global_conf,
**context.local_conf)
2016-01-05 06:44:18.544 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/paste/deploy/util.py", line 58, in
fix_call
2016-01-05 06:44:18.544 TRACE cinder reraise(*exc_info)
2016-01-05 06:44:18.544 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/paste/deploy/compat.py", line 23,
in reraise
2016-01-05 06:44:18.544 TRACE cinder exec('raise t, e, tb', dict(t=t,
e=e, tb=tb))
2016-01-05 06:44:18.544 TRACE cinder   File
"/usr/local/lib/python2.7/dist-packages/paste/deploy/util.py", line 55, in
fix_call
2016-01-05 06:44:18.544 TRACE cinder val = callable(*args, **kw)
2016-01-05 06:44:18.544 TRACE cinder TypeError: factory() takes exactly 3
arguments (2 given); got ({'__file...er'}, oslo_config_project=...), wanted
(cls, global_conf, allowed_origin, **local_conf)
2016-01-05 06:44:18.544 TRACE cinder





Any help.


--pradip



On Tue, Jan 5, 2016 at 5:03 PM, Pradip Mukhopadhyay <
pradip.inte...@gmail.com> wrote:

> I did not do anything specific.
>
> Oslo Config has IntOpt, not PortOpt.
>
> Any clue how can I upgrade oslo.config?
>
>
>
> --pradip
>
>
>
> On Tue, Jan 5, 2016 at 4:43 PM, Julien Danjou <jul...@danjou.i

Re: [openstack-dev] [cinder] oslo_config.PortOp is undefined

[Pradip Mukhopadhyay]

Thanks. Tried this. Still getting the same error on c-api installation.


The pip upgrade shown some issues as follows:

Installing collected packages: lxml, oslo.middleware, pyparsing, requests,
python-keystoneclient, SQLAlchemy, urllib3
  Found existing installation: lxml 3.3.3
Uninstalling lxml-3.3.3:
Exception:
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/pip/basecommand.py", line
211, in main
status = self.run(options, args)
  File "/usr/local/lib/python2.7/dist-packages/pip/commands/install.py",
line 311, in run
root=options.root_path,
  File "/usr/local/lib/python2.7/dist-packages/pip/req/req_set.py", line
640, in install
requirement.uninstall(auto_confirm=True)
  File "/usr/local/lib/python2.7/dist-packages/pip/req/req_install.py",
line 716, in uninstall
paths_to_remove.remove(auto_confirm)
  File "/usr/local/lib/python2.7/dist-packages/pip/req/req_uninstall.py",
line 125, in remove
renames(path, new_path)
  File "/usr/local/lib/python2.7/dist-packages/pip/utils/__init__.py", line
315, in renames
shutil.move(old, new)
  File "/usr/lib/python2.7/shutil.py", line 300, in move
rmtree(src)
  File "/usr/lib/python2.7/shutil.py", line 252, in rmtree
onerror(os.remove, fullname, sys.exc_info())
  File "/usr/lib/python2.7/shutil.py", line 250, in rmtree
os.remove(fullname)
OSError: [Errno 13] Permission denied:
'/usr/lib/python2.7/dist-packages/lxml/lxml.etree_api.h'




Do you think a unstack-stake would make life simple?




--pradip



On Tue, Jan 5, 2016 at 5:25 PM, Michał Dulko <michal.du...@intel.com> wrote:

> PortOpt definitely exists in oslo.config [1]. Try executing "pip install
> -U -r /opt/stack/cinder/requirements.txt".
>
> [1]
>
> https://github.com/openstack/oslo.config/blob/f5e2fab3ae5af5bd47fe3526a73f13fbaa27c1f0/oslo_config/cfg.py#L1180-L1216
>
> On 01/05/2016 12:33 PM, Pradip Mukhopadhyay wrote:
> > I did not do anything specific.
> >
> > Oslo Config has IntOpt, not PortOpt.
> >
> > Any clue how can I upgrade oslo.config?
> >
> >
> >
> > --pradip
> >
> >
> >
> > On Tue, Jan 5, 2016 at 4:43 PM, Julien Danjou <jul...@danjou.info
> > <mailto:jul...@danjou.info>> wrote:
> >
> > On Tue, Jan 05 2016, Pradip Mukhopadhyay wrote:
> >
> > Upgrade oslo.config?
> >
> > > Hello,
> > >
> > >
> > > I have a devstack created on 12/22/15. Just seeing that (after a
> > vacation)
> > > it stops working.
> > >
> > > Tried to restart the cinder services, getting the error:
> > >
> > > stack@openstack4:~/devstack$ /usr/local/bin/cinder-api
> --config-file
> > > /etc/cinder/cinder.conf & echo $!
> > >/opt/stack/status/stack/c-api.pid; fg ||
> > > echo "c-api failed to start" | tee
> > "/opt/stack/status/stack/c-api.failure"
> > > [1] 23828
> > > /usr/local/bin/cinder-api --config-file /etc/cinder/cinder.conf
> > > Traceback (most recent call last):
> > >   File "/usr/local/bin/cinder-api", line 6, in 
> > > from cinder.cmd.api import main
> > >   File "/opt/stack/cinder/cinder/cmd/api.py", line 37, in 
> > > from cinder import service
> > >   File "/opt/stack/cinder/cinder/service.py", line 65, in 
> > > cfg.PortOpt('osapi_volume_listen_port',
> > > AttributeError: 'module' object has no attribute 'PortOpt'
> > > c-api failed to start
> > > stack@openstack4:~/devstack$
> > >
> > >
> > >
> > > Looks like something to do with oslo_config.PortOpt.
> > >
> > > I dont have any port mentioned in cinder.conf (tried also
> > specifying 8070 -
> > > same failure).
> > >
> > > When commenting out the lines, getting the following for rabbit:
> > >
> > > 2016-01-05 05:44:10.421 TRACE cinder plugin = ep.resolve()
> > > 2016-01-05 05:44:10.421 TRACE cinder   File
> > >
> > "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py",
> line
> > > 2386, in resolve
> > > 2016-01-05 05:44:10.421 TRACE cinder module =
> > > __import__(self.module_name, fromlist=['__name__'], level=0)
> > > 2016-01-05 05:44:10.421 TRACE cinder   File
> > >
> >
>  
> "/usr/local/lib/python2.7/dist-packages/oslo_messagin

Re: [openstack-dev] [cinder] oslo_config.PortOp is undefined

[Pradip Mukhopadhyay]

Oops. sorry. I was as stack user. It works now (with a sudo). All the three
cinder services are running.


Thanks a ton for the help,

Pradip





On Tue, Jan 5, 2016 at 5:51 PM, Pradip Mukhopadhyay <
pradip.inte...@gmail.com> wrote:

> Thanks. Tried this. Still getting the same error on c-api installation.
>
>
> The pip upgrade shown some issues as follows:
>
> Installing collected packages: lxml, oslo.middleware, pyparsing, requests,
> python-keystoneclient, SQLAlchemy, urllib3
>   Found existing installation: lxml 3.3.3
> Uninstalling lxml-3.3.3:
> Exception:
> Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/dist-packages/pip/basecommand.py", line
> 211, in main
> status = self.run(options, args)
>   File "/usr/local/lib/python2.7/dist-packages/pip/commands/install.py",
> line 311, in run
> root=options.root_path,
>   File "/usr/local/lib/python2.7/dist-packages/pip/req/req_set.py", line
> 640, in install
> requirement.uninstall(auto_confirm=True)
>   File "/usr/local/lib/python2.7/dist-packages/pip/req/req_install.py",
> line 716, in uninstall
> paths_to_remove.remove(auto_confirm)
>   File "/usr/local/lib/python2.7/dist-packages/pip/req/req_uninstall.py",
> line 125, in remove
> renames(path, new_path)
>   File "/usr/local/lib/python2.7/dist-packages/pip/utils/__init__.py",
> line 315, in renames
> shutil.move(old, new)
>   File "/usr/lib/python2.7/shutil.py", line 300, in move
> rmtree(src)
>   File "/usr/lib/python2.7/shutil.py", line 252, in rmtree
> onerror(os.remove, fullname, sys.exc_info())
>   File "/usr/lib/python2.7/shutil.py", line 250, in rmtree
> os.remove(fullname)
> OSError: [Errno 13] Permission denied:
> '/usr/lib/python2.7/dist-packages/lxml/lxml.etree_api.h'
>
>
>
>
> Do you think a unstack-stake would make life simple?
>
>
>
>
> --pradip
>
>
>
> On Tue, Jan 5, 2016 at 5:25 PM, Michał Dulko <michal.du...@intel.com>
> wrote:
>
>> PortOpt definitely exists in oslo.config [1]. Try executing "pip install
>> -U -r /opt/stack/cinder/requirements.txt".
>>
>> [1]
>>
>> https://github.com/openstack/oslo.config/blob/f5e2fab3ae5af5bd47fe3526a73f13fbaa27c1f0/oslo_config/cfg.py#L1180-L1216
>>
>> On 01/05/2016 12:33 PM, Pradip Mukhopadhyay wrote:
>> > I did not do anything specific.
>> >
>> > Oslo Config has IntOpt, not PortOpt.
>> >
>> > Any clue how can I upgrade oslo.config?
>> >
>> >
>> >
>> > --pradip
>> >
>> >
>> >
>> > On Tue, Jan 5, 2016 at 4:43 PM, Julien Danjou <jul...@danjou.info
>> > <mailto:jul...@danjou.info>> wrote:
>> >
>> > On Tue, Jan 05 2016, Pradip Mukhopadhyay wrote:
>> >
>> > Upgrade oslo.config?
>> >
>> > > Hello,
>> > >
>> > >
>> > > I have a devstack created on 12/22/15. Just seeing that (after a
>> > vacation)
>> > > it stops working.
>> > >
>> > > Tried to restart the cinder services, getting the error:
>> > >
>> > > stack@openstack4:~/devstack$ /usr/local/bin/cinder-api
>> --config-file
>> > > /etc/cinder/cinder.conf & echo $!
>> > >/opt/stack/status/stack/c-api.pid; fg ||
>> > > echo "c-api failed to start" | tee
>> > "/opt/stack/status/stack/c-api.failure"
>> > > [1] 23828
>> > > /usr/local/bin/cinder-api --config-file /etc/cinder/cinder.conf
>> > > Traceback (most recent call last):
>> > >   File "/usr/local/bin/cinder-api", line 6, in 
>> > > from cinder.cmd.api import main
>> > >   File "/opt/stack/cinder/cinder/cmd/api.py", line 37, in 
>> > > from cinder import service
>> > >   File "/opt/stack/cinder/cinder/service.py", line 65, in 
>> > > cfg.PortOpt('osapi_volume_listen_port',
>> > > AttributeError: 'module' object has no attribute 'PortOpt'
>> > > c-api failed to start
>> > > stack@openstack4:~/devstack$
>> > >
>> > >
>> > >
>> > > Looks like something to do with oslo_config.PortOpt.
>> > >
>> > > I dont have any port mentioned in cinder.conf (tried also
>> > specifying 8070 

[openstack-dev] [Monasca] Facing issue in running monasca python client

[Pradip Mukhopadhyay]

Hello,



I setup the devstack-monasca using the following wiki:
https://github.com/openstack/monasca-api/tree/master/devstack

So I can see all the OS services and the monansca-api, agent etc. is up and
running.

I would like to play with some Monascal python-client. So I install python
client as: sudo pip install python-monascaclient

Now when I am trying to see the CLI, it is giving an error as follows:

stack@stack-ThinkPad-W530:~/devstack$ monasca --os-username mini-mon
--os-password password --os-project-name mini-mon --os-auth-url
http://10.74.150.158:35357/v3 --monasca-api-url
http://10.74.150.158:8070/v2.0 metric-list
*('Connection aborted.', error(104, 'Connection reset by peer'))*



Here is my keystone endpoint:

| f259de7e41db4871854a9e56a406daa1 | RegionOne |
http://10.74.150.158:5000/v2.0|
http://10.74.150.158:5000/v2.0|
http://10.74.150.158:35357/v2.0| 0208a38741d443bdb74592a3d9017762 |

(I think Monasca require Keystone 3.0 - hence I have given 'v3').

Here is my monasca endpoint in keystone:

| 21be1893c8934950956b0f57c24c50fe | RegionOne |
http://10.74.150.158:8070/v2.0|
http://10.74.150.158:8070/v2.0|
http://10.74.150.158:8070/v2.0| 34134ffdb56241e2a5beb9995b0e3628 |



Any help in resolving this will be highly appreciated.


--pradip
__
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] [Monasca] monasca-threshold smoke is failing

[Pradip Mukhopadhyay]

Hello,


Trying to install the Monasca through vagrant stuff. On the 'vagrant
provision' step, getting the threshold smoke failure.

Any clue what might be the cause. I am in Ubuntu 15.10:

pradipm@pradipm-ThinkPad-W530:~$ uname -a
Linux pradipm-ThinkPad-W530 4.2.0-19-generic #23-Ubuntu SMP Wed Nov 11
11:39:30 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux





failed: [mini-mon] => {"failed": true}
msg: Exception in thread "main"
org.apache.thrift7.transport.TTransportException:
java.net.ConnectException: Connection refused
at org.apache.thrift7.transport.TSocket.open(TSocket.java:183)
at
org.apache.thrift7.transport.TFramedTransport.open(TFramedTransport.java:81)
at
backtype.storm.thrift$nimbus_client_and_conn.invoke(thrift.clj:75)
at
backtype.storm.command.kill_topology$_main.doInvoke(kill_topology.clj:26)
at clojure.lang.RestFn.applyTo(RestFn.java:137)
at backtype.storm.command.kill_topology.main(Unknown Source)
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at org.apache.thrift7.transport.TSocket.open(TSocket.java:178)
... 5 more
Exception in thread "main"
org.apache.thrift7.transport.TTransportException:
java.net.ConnectException: Connection refused
at org.apache.thrift7.transport.TSocket.open(TSocket.java:183)
at
org.apache.thrift7.transport.TFramedTransport.open(TFramedTransport.java:81)
at
backtype.storm.thrift$nimbus_client_and_conn.invoke(thrift.clj:75)
at backtype.storm.command.list$_main.invoke(list.clj:22)
at clojure.lang.AFn.applyToHelper(AFn.java:159)
at clojure.lang.AFn.applyTo(AFn.java:151)
at backtype.storm.command.list.main(Unknown Source)
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at org.apache.thrift7.transport.TSocket.open(TSocket.java:178)
... 6 more

TASK: [monasca-thresh | Enable the Service]
***
FATAL: no hosts matched or all hosts have already failed -- aborting


PLAY RECAP

   to retry, use: --limit @/home/pradipm/mini-mon.retry

mini-mon   : ok=157  changed=21   unreachable=0
failed=1

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.



__
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] [Monasca] Authentication through Keystone

[Pradip Mukhopadhyay]

Hello,


How Monasca is getting authenticated through Keystone?

The reason of asking this is: Monasca is in Java, whereas other services
(like Cinder) uses the keystone-middleware-authentication (when configured)
through api-paste.ini. And the middleware is in python.


Does Monasca uses some other scheme to authenticate to Keystone?



Thanks in advance,
Pradip
__
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] [cinder] Attaching extra-spec to vol-type using Cinder py-client

[Pradip Mukhopadhyay]

Oops. Missed it. Thanks! It worked Vipin.



On Tue, Mar 31, 2015 at 12:06 PM, Vipin Balachandran 
vbalachand...@vmware.com wrote:

  cinder.volume_types.create returns an instance of VolumeType.


 https://github.com/openstack/python-cinderclient/blob/master/cinderclient/v2/volume_types.py#L118



 Thanks,

 Vipin



 *From:* Pradip Mukhopadhyay [mailto:pradip.inte...@gmail.com]
 *Sent:* Tuesday, March 31, 2015 10:07 AM
 *To:* OpenStack Development Mailing List (not for usage questions)
 *Subject:* [openstack-dev] [cinder] Attaching extra-spec to vol-type
 using Cinder py-client



 Hello,

 I am trying to create and type-set some parameters to a volume-type as
 follows:

 cinder type-create nfs

 cinder type-key nfs set volume_backend_name=myNFSBackend

 The same thing I want to achieve through python client.

 I can create the type as follows:

 from cinderclient import client

 cinder = client.Client('2', 'admin', 'pw', 'demo', 
 'http://127.0.0.1:5000/v2.0 
 https://urldefense.proofpoint.com/v2/url?u=http-3A__127.0.0.1-3A5000_v2.0d=AwMBaQc=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEsr=CTAUyaHvyUUJ-0QHviztQxBhCDLLSg1DksoSE4TOfZ8m=EIUflZKBvoV_Hp3DkmTE612FqBGHpwXLuwGJ3UpwbbIs=hk8YML4Dn_kR2cMzCB4Lohd-fnmlk8Z9zBEu1Cc3DO0e=',
  service_type=volumev2)

 cinder.volume_types.create('nfs')

 However how can I associate the extra-spec through python-client code to
 the 'nfs' volume (same impact as the CLI 'cinder type-key nfs set
 volume_backend_name=myNFSBackend' does)?

 The 'set_keys' etc. methods are there in the v2/volume_types.py in
 python-cinderclient codebase. How to call it? (it's part of VolumeType
 class, not VolumeTypeManager).

 Any help would be great.

 Thanks, Pradip

 __
 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 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] [cinder] Attaching extra-spec to vol-type using Cinder py-client

[Pradip Mukhopadhyay]

Hello,

I am trying to create and type-set some parameters to a volume-type as
follows:

cinder type-create nfs
cinder type-key nfs set volume_backend_name=myNFSBackend

The same thing I want to achieve through python client.

I can create the type as follows:

from cinderclient import client
cinder = client.Client('2', 'admin', 'pw', 'demo',
'http://127.0.0.1:5000/v2.0', service_type=volumev2)
cinder.volume_types.create('nfs')

However how can I associate the extra-spec through python-client code to
the 'nfs' volume (same impact as the CLI 'cinder type-key nfs set
volume_backend_name=myNFSBackend' does)?

The 'set_keys' etc. methods are there in the v2/volume_types.py in
python-cinderclient codebase. How to call it? (it's part of VolumeType
class, not VolumeTypeManager).

Any help would be great.

Thanks, Pradip
__
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] [infrastructure] Document to write a new service

[Pradip Mukhopadhyay]

Hello,


Is there any documentation available which can be followed to start writing
up (from scratch) a new service?


Thanks,
Pradip
__
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] [cinder] CURD operation for storage pools in Cinder

[Pradip Mukhopadhyay]

Hello,



Does Cinder already have a blue-print/planned-schedule for supporting (at
least in API level - may not be python-client/Horizon levels) the
create/edit/delete operation on the storage pools?

It is understood that the read part 'get_pools' is already there.


If it is already planned/scheduled - what is the time-frame of having it as
a part of devstack?



Thanks in advance,
Pradip
__
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] [cinder] CURD operation for storage pools in Cinder

[Pradip Mukhopadhyay]

Ok, thanks.

Usecase perspective, it is the under-cloud usecase (the cloud admin
provisioned the underlying storage - which will in turn use to create
cinder). Will there be any other usecase?

What will be the semantic of 'Edit' operation to the pool? Create and
Delete is obvious. But how to define the 'Edit'?




--pradip




On Thu, Feb 12, 2015 at 1:01 AM, Bruns, Curt E curt.e.br...@intel.com
wrote:

 Hi Duncan and Pradip,

 It was Reddy, a colleague of mine at Intel, that expressed interest with
 managing storage pools in Cinder.  We haven’t put a BP out yet, but we
 definitely think it would be useful and we should get a BP in the works.

 - Curt

 From: Duncan Thomas duncan.tho...@gmail.commailto:
 duncan.tho...@gmail.com
 Reply-To: OpenStack Development Mailing List (not for usage questions) 
 openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
 
 Date: Wednesday, February 11, 2015 at 10:38 AM
 To: OpenStack Development Mailing List openstack-dev@lists.openstack.org
 mailto:openstack-dev@lists.openstack.org
 Subject: Re: [openstack-dev] [cinder] CURD operation for storage pools in
 Cinder


 As far as I know, this has not been looked at - you need to use whatever
 management tools your backend provides to do this.

 There was somebody from Intel IIRC in Paris with some interest in maybe
 starting something about this, but I don't know that it came to much.

 Duncan Thomas

 On Feb 11, 2015 6:53 PM, Pradip Mukhopadhyay pradip.inte...@gmail.com
 mailto:pradip.inte...@gmail.com wrote:
 Hello,



 Does Cinder already have a blue-print/planned-schedule for supporting (at
 least in API level - may not be python-client/Horizon levels) the
 create/edit/delete operation on the storage pools?

 It is understood that the read part 'get_pools' is already there.


 If it is already planned/scheduled - what is the time-frame of having it
 as a part of devstack?



 Thanks in advance,
 Pradip






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


 __
 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 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] [Monasca][Monasca-agent] Logfile format to send matrices

[Pradip Mukhopadhyay]

Hello,


In Monasca-agent README here
https://github.com/stackforge/monasca-agent#introduction It mentioned:
Retrieving metrics from log files written in a specific format. 

Can anyone please point to such a format?Any such pointer would be good.

If I understand it correctly, if I point the monasca-agent to the logfile
written in specific format - it can pick it up from there (the collector)
and send it to the monasca-api. Right?



Thanks.

Pradip
__
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] [Cinder]

[Pradip Mukhopadhyay]

Hi,


Is there a way to find out/list down the backends discovered for Cinder?


There is, I guess, no API for get the list of backends.



Thanks,
Pradip
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Cinder] Listing of backends

[Pradip Mukhopadhyay]

Hi,


Is there a way to find out/list down the backends discovered for Cinder?


There is, I guess, no API for get the list of backends.



Thanks,
Pradip
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cinder] Code pointer for processing cinder backend config

[Pradip Mukhopadhyay]

Hello,


Suppose I have a backend specification in cinder.conf as follows:

[nfs_pradipm]
volume_backend_name=nfs_pradipm
volume_driver=cinder.volume.drivers.netapp.common.NetAppDriver
netapp_server_hostname=IP
netapp_server_port=80
netapp_storage_protocol=nfs
netapp_storage_family=ontap_cluster
netapp_login=admin
netapp_password=password
netapp_vserver=my_vs1
nfs_shares_config=/home/ubuntu/nfs.shares



Where this config info is getting parsed out in the cinder code?



Thanks,
Pradip
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [All] Programatically re-starting OpenStack services

[Pradip Mukhopadhyay]

Hello,


Are there ways (which pattern might be preferred) by which one can
programatically restart different OpenStack services?

For example: if one wants to restart cinder-scheduler or heat-cfn?



Thanks in advance,
Pradip
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [All] Programatically re-starting OpenStack services

[Pradip Mukhopadhyay]

Yeah, I meant from Orchestration. Sorry if the earlier one is not clear.


To be little more specific: from the Life Cycle management functions of the
custom Heat resource definition.


Thanks,
Pradip



On Mon, Dec 1, 2014 at 9:54 AM, Sadia Bashir 11msccssbas...@seecs.edu.pk
wrote:

 Hi,

 What do you mean by programatically? Do you want to restart services via a
 script or want to orchestrate restarting services from within openstack?

 If it is via script, you can write a bash script as follows:

 service cinder-scheduler restart
 service heat-api-cfn restart



 On Mon, Dec 1, 2014 at 9:03 AM, Pradip Mukhopadhyay 
 pradip.inte...@gmail.com wrote:

 Hello,


 Are there ways (which pattern might be preferred) by which one can
 programatically restart different OpenStack services?

 For example: if one wants to restart cinder-scheduler or heat-cfn?



 Thanks in advance,
 Pradip


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




 --



 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [heat] [cinder backend options] Propagate Cinder backend config information to Heat

[Pradip Mukhopadhyay]

Hello,


Suppose we have a cinder backend in local.conf | cinder.conf as :


[myNFSBackend]
nfs_mount_options = nfsvers=3
volume_backend_name = myNFSBackend
volume_driver = cinder.volume.drivers.netapp.common.NetAppDriver
netapp_server_hostname = IP
netapp_server_port = 80
netapp_storage_protocol = nfs
netapp_storage_family = ontap_cluster
netapp_login = admin
netapp_password = password
netapp_vserver = vserver_name
nfs_shares_config = /opt/stack/nfs.shares


We would like to access some of such cinder backend configuration
information from Heat. More specifically from custom resource inside the
Heat (e.g. access the netapp_server_hostname, netapp_login, netapp_password
etc. when defining a custom resource class extending the base Resource
class). The purpose is to facilitate some (soap) service call to the
backend storage from custom resource definitions.


What is the best pattern/mechanism available? Any pointers to code/doc will
be highly appreciated.


Does any database table holds the local.conf (or service specific conf)
information?



Thanks,
Pradip
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [heat] [cinder backend options] Propagate Cinder backend config information to Heat

[Pradip Mukhopadhyay]

Thanks Qiming  Pavlo. We had looked into the v2 of Cinder API listings:
http://developer.openstack.org/api-ref-blockstorage-v2.html. However most
likely (or may be we missed to note) none of the APIs peeped into/exposed
the Cinder's backend configuration (the info we were looking for). So we
were curious if, *by design, *it is not expected to expose that through
Cinder? Or Cinder API can potentially be written to bridge the gap.

@Sirushti- that's interesting. Shall peep into it.


Thanks.
Pradip



On Fri, Nov 28, 2014 at 7:46 PM, Pavlo Shchelokovskyy 
pshchelokovs...@mirantis.com wrote:

 That's true. Heat's job is mainly to call other OpenStack APIs in correct
 order in order to achieve desired combination of infrastructure resources.
 Physically though it may run on a completely different host where these
 files are not present, even including a host that is outside of the
 datacenter where OpenStack is deployed (so called Heat standalone mode).
 The only info Heat knows about other OpenStack services is what Heat can
 get trough their API.

 Pavlo Shchelokovskyy
 Software Engineer
 Mirantis Inc
 www.mirantis.com

 On Fri, Nov 28, 2014 at 3:15 PM, Qiming Teng teng...@linux.vnet.ibm.com
 wrote:

 The first thing you may want to check is the Cinder API.  If I'm
 understanding this correctly, Heat only interact with other OpenStack
 services via their APIs.  It is not supposed to peek into their
 internals.

 Regards,
   - Qiming

 On Fri, Nov 28, 2014 at 06:19:56PM +0530, Pradip Mukhopadhyay wrote:
  Hello,
 
 
  Suppose we have a cinder backend in local.conf | cinder.conf as :
 
 
  [myNFSBackend]
  nfs_mount_options = nfsvers=3
  volume_backend_name = myNFSBackend
  volume_driver = cinder.volume.drivers.netapp.common.NetAppDriver
  netapp_server_hostname = IP
  netapp_server_port = 80
  netapp_storage_protocol = nfs
  netapp_storage_family = ontap_cluster
  netapp_login = admin
  netapp_password = password
  netapp_vserver = vserver_name
  nfs_shares_config = /opt/stack/nfs.shares
 
 
  We would like to access some of such cinder backend configuration
  information from Heat. More specifically from custom resource inside the
  Heat (e.g. access the netapp_server_hostname, netapp_login,
 netapp_password
  etc. when defining a custom resource class extending the base Resource
  class). The purpose is to facilitate some (soap) service call to the
  backend storage from custom resource definitions.
 
 
  What is the best pattern/mechanism available? Any pointers to code/doc
 will
  be highly appreciated.
 
 
  Does any database table holds the local.conf (or service specific conf)
  information?
 
 
 
  Thanks,
  Pradip

  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [heat] [CustomResource] LifeCycle methods flow

[Pradip Mukhopadhyay]

Hello,



Any pointer (document and/or code pointer) related to how the different
overridden methods are getting called when a custom resource is getting
deployed in the heat stack?


Basically just tried to annotate the h-eng log on a simple,
very-first-attempt 'hello world' resource. Noticed the log is something
like:

2014-11-26 15:38:30.251 INFO heat.engine.plugins.helloworld [-]
[pradipm]:Inside handle_create
2014-11-26 15:38:30.257 INFO heat.engine.plugins.helloworld [-]
[pradipm]:Inside _set_param_values
2014-11-26 15:38:31.259 INFO heat.engine.plugins.helloworld [-]
[pradipm]:Inside check_create_complete
2014-11-26 15:38:44.227 INFO heat.engine.plugins.helloworld
[req-9979deb9-f911-4df4-bdf8-ecc3609f054b None demo] [pradipm]:Inside
HelloWorld ctor
2014-11-26 15:38:44.234 INFO heat.engine.plugins.helloworld
[req-9979deb9-f911-4df4-bdf8-ecc3609f054b None demo] [pradipm]:Inside
_resolve_attribute




The constructor (ctor) is getting called in the flow after the
create-resource. So though understanding the flow would help.



Thanks in advance,
Pradip
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [heat] [CustomResource] LifeCycle methods flow

[Pradip Mukhopadhyay]

Thanks Pavlo.

One particular thing I did not comprehend is:

Suppose my resource code is something like:


class HelloWorld(resource.Resource):
def __init__(self, controller, deserializer, serializer=None):
LOG.info([pradipm]:Inside HelloWorld ctor);
resource.Resource.__init__(self, controller, deserializer,
serializer)
## Re-setting the data value
self._data_value = self.properties['value']

properties_schema = {
'value': properties.Schema(
properties.Schema.STRING,
_('foo')
),
}

attributes_schema = {
   'data': _('the data')
}

...
   def _set_param_values(self):
LOG.info([pradipm]:Inside _set_param_values)
self._data_value = self.properties['value']
return

def handle_create(self):
LOG.info([pradipm]:Inside handle_create)
container_id = 1   ## some arbitrary id
self.resource_id_set(container_id)
self._set_param_values()
return container_id



I am seeing the constructor is getting called *later on* compared to the
handle_create - check_create_complete etc.

Is that a *defined* behavior? Or it is purely *temporal* (such that in some
cases the ctor might be called early also).




Thanks,
Pradip





On Wed, Nov 26, 2014 at 4:05 PM, Pavlo Shchelokovskyy 
pshchelokovs...@mirantis.com wrote:

 Pradip,

 https://github.com/openstack/heat/blob/master/heat/engine/resource.py#L473

 Basically, it calls handle_create that might return some data, yields, and
 than keeps calling check_create_complete with that data returned by
 handle_create, yielding control in-between, until check_create_complete
 returns True.

 Best regards,
 Pavlo Shchelokovskyy.

 On Wed, Nov 26, 2014 at 12:20 PM, Pradip Mukhopadhyay 
 pradip.inte...@gmail.com wrote:

 Hello,



 Any pointer (document and/or code pointer) related to how the different
 overridden methods are getting called when a custom resource is getting
 deployed in the heat stack?


 Basically just tried to annotate the h-eng log on a simple,
 very-first-attempt 'hello world' resource. Noticed the log is something
 like:

 2014-11-26 15:38:30.251 INFO heat.engine.plugins.helloworld [-]
 [pradipm]:Inside handle_create
 2014-11-26 15:38:30.257 INFO heat.engine.plugins.helloworld [-]
 [pradipm]:Inside _set_param_values
 2014-11-26 15:38:31.259 INFO heat.engine.plugins.helloworld [-]
 [pradipm]:Inside check_create_complete
 2014-11-26 15:38:44.227 INFO heat.engine.plugins.helloworld
 [req-9979deb9-f911-4df4-bdf8-ecc3609f054b None demo] [pradipm]:Inside
 HelloWorld ctor
 2014-11-26 15:38:44.234 INFO heat.engine.plugins.helloworld
 [req-9979deb9-f911-4df4-bdf8-ecc3609f054b None demo] [pradipm]:Inside
 _resolve_attribute




 The constructor (ctor) is getting called in the flow after the
 create-resource. So though understanding the flow would help.



 Thanks in advance,
 Pradip


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




 --
 Pavlo Shchelokovskyy
 Software Engineer
 Mirantis Inc
 www.mirantis.com

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [heat] [CustomResource] LifeCycle methods flow

[Pradip Mukhopadhyay]

Thanks, Zane.

I do understand the mistake I made (too much dependency on ctags).

I am getting what you're pointing out. In face inside my
_resolve_attribute, I should have return self.properties['value'] instead
of depending on the cached value.

I wanted to understand if it is OK to cache value in any of such resource.
And your explanation is making sense. Thanks a lot.


--pradip


On Thu, Nov 27, 2014 at 4:05 AM, Zane Bitter zbit...@redhat.com wrote:

 On 26/11/14 05:20, Pradip Mukhopadhyay wrote:

 Hello,



 Any pointer (document and/or code pointer) related to how the different
 overridden methods are getting called when a custom resource is getting
 deployed in the heat stack?


 Basically just tried to annotate the h-eng log on a simple,
 very-first-attempt 'hello world' resource. Noticed the log is something
 like:

 2014-11-26 15:38:30.251 INFO heat.engine.plugins.helloworld [-]
 [pradipm]:Inside handle_create
 2014-11-26 15:38:30.257 INFO heat.engine.plugins.helloworld [-]
 [pradipm]:Inside _set_param_values
 2014-11-26 15:38:31.259 INFO heat.engine.plugins.helloworld [-]
 [pradipm]:Inside check_create_complete
 2014-11-26 15:38:44.227 INFO heat.engine.plugins.helloworld
 [req-9979deb9-f911-4df4-bdf8-ecc3609f054b None demo] [pradipm]:Inside
 HelloWorld ctor
 2014-11-26 15:38:44.234 INFO heat.engine.plugins.helloworld
 [req-9979deb9-f911-4df4-bdf8-ecc3609f054b None demo] [pradipm]:Inside
 _resolve_attribute




 The constructor (ctor) is getting called in the flow after the
 create-resource. So though understanding the flow would help.


 That's... surprising. I suspect it isn't the same object though.

  def __init__(self, controller, deserializer, serializer=None):


 BTW that isn't the signature for Resource.__init__. It's

   def __init__(self, name, definition, stack):

 In any event, whatever you're trying to do with self._data_value is
 probably not something you should be doing. Resource plugins are
 essentially stateless beyond what is explicitly stored in the database
 (stuff like resource_id_set()). If you really need to cache a value like
 that, store it in the ResourceData table (although I consider this
 something of an anti-pattern).

 Basically it's legit for every operation to use a brand new copy of the
 object that doesn't contain any runtime state you may have manipulated on a
 previous incarnation of the object.

 cheers,
 Zane.


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Heat] Heat Resource Plugin for third party storage

[Pradip Mukhopadhyay]

Hello,


We come across this:
http://docs.openstack.org/developer/heat/pluginguide.html


Looks like it solves three of the purposes listed below:

1. Define a custom resource type with properties and attributes
2. Register the resource to the Hear orchestrator
3. Write a driver/plugin (most likely the Life Cycle methods) which can
create/manage the resources when encounter from the Heat orchestration
engine.


Am I right?


Now the question is: in one place it is mentioned as:


It defines methods corresponding to the life cycle as well as the basic
hooks for plug-ins to handle the work of communicating with specific
down-stream services



Can this down-stream service be *anything* (say a third-party storage
array)? Or it has to be a OpenStack service only?




Thanks in advance,
Pradip
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Heat] Heat Resource Plugin for third party storage

[Pradip Mukhopadhyay]

Thanks, Zane for pointing out the right mailing list.



--pradip


On Wed, Nov 12, 2014 at 6:35 PM, Zane Bitter zbit...@redhat.com wrote:

 The developer mailing list is not for usage questions. Please ask this on
 ask.openstack.org - I'm sure a lot of people will be interested in the
 answer and we want it searchable for them in future. Feel free to ping me
 with a link when you've posted it.

 cheers,
 Zane.

 On 12/11/14 06:00, Pradip Mukhopadhyay wrote:

 Hello,


 We come across this:
 http://docs.openstack.org/developer/heat/pluginguide.html


 Looks like it solves three of the purposes listed below:

 1. Define a custom resource type with properties and attributes
 2. Register the resource to the Hear orchestrator
 3. Write a driver/plugin (most likely the Life Cycle methods) which can
 create/manage the resources when encounter from the Heat orchestration
 engine.


 Am I right?


 Now the question is: in one place it is mentioned as:

 
 It defines methods corresponding to the life cycle as well as the basic
 hooks for plug-ins to handle the work of communicating with specific
 down-stream services
 


 Can this down-stream service be /anything/ (say a third-party storage
 array)? Or it has to be a OpenStack service only?




 Thanks in advance,
 Pradip



 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Heat][Orchestration Template] Hierarchical Heat templates

[Pradip Mukhopadhyay]

Would like to ask the forum if something has already been considered to
make the HOT (Heat Orchestration Template) hierarchical.

Basically the template file might consist of different personas putting
things together. So from manageability of the templates - it will be a good
idea to separate it our based on different personas and have a master file
that will 'instantiate' the respective templates.personas.


If not considered already - any thought on this?


If already considered - any cons that was discussed earlier?




Thanks,
Pradip
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Devstack start

[Pradip Mukhopadhyay]

Rim,


Is it possible to share urs local.conf once?

You can view the logs using screen -x stack though.



--pradip




On Thu, Nov 6, 2014 at 7:18 PM, Rim Chol (rimc) r...@zhaw.ch wrote:

 Greetings!

 I am sending this email because I have some problems with starting the
 devstack.

 I cloned the devstack repository in my laptop and ran ./stack.sh in the
 devstack directory.
 But the konsole complains about that and some of the error messages are
 shown below.
 + screen -S stack -p g-api -X stuff '/usr/local/bin/glance-api
 --config-file=/etc/glance/glance-api.conf  echo $!
 /opt/stack/status/stack/g-api.pid; fg || echo g-api failed to start |
 tee /opt/stack/s'atus/stack/g-api.failure
 + echo 'Waiting for g-api (160.85.231.43:9292) to start...'
 Waiting for g-api (160.85.231.43:9292) to start...
 + wait_for_service 60 http://160.85.231.43:9292
 + local timeout=60
 + local url=http://160.85.231.43:9292
 + timeout 60 sh -c 'while ! curl -k --noproxy '\''*'\'' -s
 http://160.85.231.43:9292 /dev/null; do sleep 1; done'
 + die 317 'g-api did not start'
 + local exitcode=0
 + set +o xtrace
 [Call Trace]
 ./stack.sh:1186:start_glance
 /home/chol/OpenStack/devstack/lib/glance:317:die
 [ERROR] /home/chol/OpenStack/devstack/lib/glance:317 g-api did not
 start
 Error on exit
 World dumping... see ./worlddump-2014-11-06-133528.txt for details\

 I can not find any helpful materials on this over the Internet.
 Could anyone of you help me fix this?
 I would really appreciate your help

 Chol.
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] devstack build is failing

[Pradip Mukhopadhyay]

Hello,


Trying first time to build a devstack in my Ubuntu-14.10 VM. Getting the
following error:


2014-11-04 09:27:32.182 | + recreate_database_mysql nova latin1
2014-11-04 09:27:32.182 | + local db=nova
2014-11-04 09:27:32.182 | + local charset=latin1
2014-11-04 09:27:32.182 | + mysql -uroot -pstackdb -h127.0.0.1 -e 'DROP
DATABASE IF EXISTS nova;'
2014-11-04 09:27:32.186 | + mysql -uroot -pstackdb -h127.0.0.1 -e 'CREATE
DATABASE nova CHARACTER SET latin1;'
2014-11-04 09:27:32.189 | + /usr/local/bin/nova-manage db sync
2014-11-04 09:27:32.455 | Traceback (most recent call last):
2014-11-04 09:27:32.455 |   File /usr/local/bin/nova-manage, line 6, in
module
2014-11-04 09:27:32.455 | from nova.cmd.manage import main
2014-11-04 09:27:32.455 |   File
/home/ubuntu/devstack/nova/nova/cmd/manage.py, line 68, in module
2014-11-04 09:27:32.455 | from nova.api.ec2 import ec2utils
2014-11-04 09:27:32.455 |   File
/home/ubuntu/devstack/nova/nova/api/ec2/__init__.py, line 34, in module
2014-11-04 09:27:32.455 | from nova.api.ec2 import faults
2014-11-04 09:27:32.455 |   File
/home/ubuntu/devstack/nova/nova/api/ec2/faults.py, line 20, in module
2014-11-04 09:27:32.455 | from nova import utils
2014-11-04 09:27:32.455 |   File
/home/ubuntu/devstack/nova/nova/utils.py, line 39, in module
2014-11-04 09:27:32.456 | from oslo.concurrency import lockutils
2014-11-04 09:27:32.456 |   File
/usr/local/lib/python2.7/dist-packages/oslo/concurrency/lockutils.py,
line 30, in module
2014-11-04 09:27:32.456 | from oslo.config import cfgfilter
2014-11-04 09:27:32.456 | ImportError: cannot import name cfgfilter
2014-11-04 09:27:32.471 | + exit_trap
2014-11-04 09:27:32.471 | + local r=1
2014-11-04 09:27:32.471 | ++ jobs -p
2014-11-04 09:27:32.472 | + jobs=
2014-11-04 09:27:32.472 | + [[ -n '' ]]
2014-11-04 09:27:32.472 | + kill_spinner
2014-11-04 09:27:32.472 | + '[' '!' -z '' ']'
2014-11-04 09:27:32.472 | + [[ 1 -ne 0 ]]




Any idea what is missing? Any help is highly appreciated.



Some more details may be helpful:

ubuntu@ubuntu:~$ uname -a

Linux ubuntu 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux



ubuntu@ubuntu:~$ python --version

Python 2.7.6

ubuntu@ubuntu:~$ which python

/usr/bin/python







Thanks,
Pradip
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] devstack build is failing

[Pradip Mukhopadhyay]

Thanks Anish.


I guess the same happened to me. A mixed of python packages. So what I did
is that 'pip uninstall', followed by unstack, followed by ./clean.sh,
followed by stack.sh. It worked. So far so good.



--pradip



On Wed, Nov 5, 2014 at 5:00 AM, Anish Bhatt an...@chelsio.com wrote:

  I had similar errors due to a mixture of python packages installed via
 yum not playing too nicely with pip. I ended up nuking most of the install
 to fix it, so don’t have a recommendation beyond that, plus I was using
 RHEL 7. Maybe this is of interest to you

 https://bugs.launchpad.net/oslo.config/+bug/1374741



 -Anish



 *From:* Pradip Mukhopadhyay [mailto:pradip.inte...@gmail.com]
 *Sent:* Tuesday, November 4, 2014 2:27 AM
 *To:* openstack-dev@lists.openstack.org
 *Subject:* [openstack-dev] devstack build is failing



 Hello,



 Trying first time to build a devstack in my Ubuntu-14.10 VM. Getting the
 following error:


 2014-11-04 09:27:32.182 | + recreate_database_mysql nova latin1
 2014-11-04 09:27:32.182 | + local db=nova
 2014-11-04 09:27:32.182 | + local charset=latin1
 2014-11-04 09:27:32.182 | + mysql -uroot -pstackdb -h127.0.0.1 -e 'DROP
 DATABASE IF EXISTS nova;'
 2014-11-04 09:27:32.186 | + mysql -uroot -pstackdb -h127.0.0.1 -e 'CREATE
 DATABASE nova CHARACTER SET latin1;'
 2014-11-04 09:27:32.189 | + /usr/local/bin/nova-manage db sync
 2014-11-04 09:27:32.455 | Traceback (most recent call last):
 2014-11-04 09:27:32.455 |   File /usr/local/bin/nova-manage, line 6, in
 module
 2014-11-04 09:27:32.455 | from nova.cmd.manage import main
 2014-11-04 09:27:32.455 |   File
 /home/ubuntu/devstack/nova/nova/cmd/manage.py, line 68, in module
 2014-11-04 09:27:32.455 | from nova.api.ec2 import ec2utils
 2014-11-04 09:27:32.455 |   File
 /home/ubuntu/devstack/nova/nova/api/ec2/__init__.py, line 34, in module
 2014-11-04 09:27:32.455 | from nova.api.ec2 import faults
 2014-11-04 09:27:32.455 |   File
 /home/ubuntu/devstack/nova/nova/api/ec2/faults.py, line 20, in module
 2014-11-04 09:27:32.455 | from nova import utils
 2014-11-04 09:27:32.455 |   File
 /home/ubuntu/devstack/nova/nova/utils.py, line 39, in module
 2014-11-04 09:27:32.456 | from oslo.concurrency import lockutils
 2014-11-04 09:27:32.456 |   File
 /usr/local/lib/python2.7/dist-packages/oslo/concurrency/lockutils.py,
 line 30, in module
 2014-11-04 09:27:32.456 | from oslo.config import cfgfilter
 2014-11-04 09:27:32.456 | ImportError: cannot import name cfgfilter
 2014-11-04 09:27:32.471 | + exit_trap
 2014-11-04 09:27:32.471 | + local r=1
 2014-11-04 09:27:32.471 | ++ jobs -p
 2014-11-04 09:27:32.472 | + jobs=
 2014-11-04 09:27:32.472 | + [[ -n '' ]]
 2014-11-04 09:27:32.472 | + kill_spinner
 2014-11-04 09:27:32.472 | + '[' '!' -z '' ']'
 2014-11-04 09:27:32.472 | + [[ 1 -ne 0 ]]



  Any idea what is missing? Any help is highly appreciated.


   Some more details may be helpful:

 ubuntu@ubuntu:~$ uname -a

 Linux ubuntu 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014
 x86_64 x86_64 x86_64 GNU/Linux



 ubuntu@ubuntu:~$ python --version

 Python 2.7.6

 ubuntu@ubuntu:~$ which python

 /usr/bin/python









 Thanks,

 Pradip


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev