OpenStack Compute (nova)

Couldn't enable openstackX extensions

Asked by Roman Sokolkov

I have nova,dashboard from trunk. In dashboard I see error message "Unable to get service info: This error may be caused by missing openstackx extensions in nova. See the dashboard README."

I download openstacx from github. Added in nova.conf:
--osapi_extensions_path=/opt/openstackx/extensions/

but it is not work:(

in nova-api.log I found this:
2011-09-12 16:54:10,833 DEBUG routes.middleware [-] No route matched for GET /admin/services from (pid=4312) __call__ /usr/lib/python2.7/site-packages/routes/middleware.py:97
2011-09-12 16:54:10,834 DEBUG routes.middleware [-] No route matched for GET /admin/services from (pid=4312) __call__ /usr/lib/python2.7/site-packages/routes/middleware.py:97
2011-09-12 16:54:10,838 DEBUG routes.middleware [-] No route matched for GET /extras/usage from (pid=4312) __call__ /usr/lib/python2.7/site-packages/routes/middleware.py:97
2011-09-12 16:54:10,839 DEBUG routes.middleware [-] No route matched for GET /extras/usage from (pid=4312) __call__ /usr/lib/python2.7/site-packages/routes/middleware.py:97
2011-09-12 16:54:12,203 DEBUG routes.middleware [-] No route matched for GET /admin/services from (pid=4312) __call__ /usr/lib/python2.7/site-packages/routes/middleware.py:97
2011-09-12 16:54:12,203 DEBUG routes.middleware [-] No route matched for GET /admin/services from (pid=4312) __call__ /usr/lib/python2.7/site-packages/routes/middleware.py:97

In README for openstacx I found:
------------------------
DEPRECATED

This is being deleted in favor of python-novaclient. We are working on moving all the functionality into nova core and novaclient.

See: https://github.com/rackspace/python-novaclient
-----------------------

Can I configure nova to work with extensions at all?
sorry for my english:)

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Solved by:
Roman Sokolkov
Solved:
Last query:
Last reply:
Revision history for this message
Roman Sokolkov (rsokolkov) said : 		#1

My nova.conf

--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lib/nova/tmp
--verbose
--s3_host=212.193.47.19
--rabbit_host=212.193.47.19
--cc_host=212.193.47.19
--ec2_url=http://212.193.47.19:8773/services/Cloud
--FAKE_subdomain=ec2
--routing_source_ip=212.193.47.19
--flat_network_dns=212.193.33.11
--verbose
--sql_connection=mysql://ssucloud:j,kfrj@127.0.0.1/nova
--scheduler_driver=nova.scheduler.simple.SimpleScheduler
--network_manager=nova.network.manager.FlatDHCPManager
--flat_network_dhcp_start=212.193.60.19
--flat_network_bridge=br0
--flat_injected=False
--public_interface=em1
--flat_interface=em1.89
--keys_path=/mnt/drbd0/nova/keys
--ca_path=/mnt/drbd0/nova/CA
--volume_group=nova
--instances_path=/mnt/drbd0/nova/instances
--vnc_console_proxy_url=http://212.193.47.19:6080
--vncproxy_wwwroot=/opt/noVNC
--osapi_extensions_path=/opt/openstackx/extensions/
--allow_admin_api=true

Revision history for this message
Roman Sokolkov (rsokolkov) said : 		#2

I ve solved my problem! Thanks Anthony Young: "Another thing to check - the os1.1 keystone endpoints have been modified in d4 to include a tenant prefix. If you are upgrading an existing install, you may need to update your keystone service catalog accordingly:

keystone-manage $* endpointTemplates add RegionOne nova http://<%= api_vip %>:8774/v1.1/%tenant_id% http://<%= api_vip %>:8774/v1.1/%tenant_id% http://<%= api_vip %>:8774/v1.1/%tenant_id% 1 1
"

But I manually update keystone database

#sqlite3 keystone.db
sqlite> update endpoint_templates set public_url="http://nova.publicinternets.com/v1.1/%tenant_id%" where id=3;
sqlite> update endpoint_templates set admin_url="http://127.0.0.1:8774/v1.1/%tenant_id%" where id=3;
sqlite> update endpoint_templates set internal_url="http://localhost:8774/v1.1/%tenant_id%" where id=3;