Ask Your Question

sambol's profile - activity

2015-10-28 10:12:27 -0600 received badge  Famous Question (source)
2015-09-03 08:51:21 -0600 received badge  Famous Question (source)
2015-06-02 09:50:59 -0600 received badge  Taxonomist
2015-02-01 06:24:20 -0600 received badge  Notable Question (source)
2015-01-26 13:43:55 -0600 received badge  Famous Question (source)
2015-01-23 06:55:35 -0600 received badge  Famous Question (source)
2015-01-21 11:54:19 -0600 received badge  Popular Question (source)
2015-01-14 11:35:17 -0600 asked a question Debugging Heat Installation

I'm having trouble getting Heat to start. I'm following this guide: http://docs.openstack.org/juno/instal... .

I try the following command:

sudo service openstack-heat-api start

And upon checking the status, I receive:

openstack-heat-api dead but pid file exists

The log files are blank even though I have verbose set to true. MySQL and Keystone are on different nodes, could that be a problem? Any hints on how I can better debug?

Thank you...

2014-12-16 09:35:11 -0600 received badge  Notable Question (source)
2014-11-14 19:44:14 -0600 received badge  Popular Question (source)
2014-11-14 09:55:55 -0600 commented question Swift proxy failed to start

Thanks, Beny!

2014-11-13 15:23:40 -0600 asked a question Swift proxy failed to start

When I run service swift-proxy restart I get the following:

stop: Unknown instance: 
start: Job failed to start

However, there is no traceback and no log in /var/log/swift, so I'm not sure how to debug. Any pointers?

I followed the instructions here: http://docs.openstack.org/juno/instal...

2014-11-10 14:51:45 -0600 received badge  Popular Question (source)
2014-11-10 14:51:45 -0600 received badge  Notable Question (source)
2014-10-28 05:52:43 -0600 received badge  Famous Question (source)
2014-10-13 13:36:29 -0600 received badge  Notable Question (source)
2014-10-13 06:37:28 -0600 received badge  Nice Question (source)
2014-10-13 06:36:47 -0600 received badge  Famous Question (source)
2014-10-09 22:42:41 -0600 received badge  Popular Question (source)
2014-10-09 16:02:35 -0600 commented answer Second Swift Proxy Node

So in summary, you'd assign a VIP when you are using more than one HAProxy node so that there would only be one Keystone endpoint?

Thanks for your help..

2014-10-09 15:44:32 -0600 commented answer Second Swift Proxy Node

Right, but why can't the Keystone endpoint be the IP of the HAProxy node? Maybe I was confusing earlier: I have two Swift proxy nodes but only one HAProxy node.

2014-10-09 15:33:54 -0600 commented answer Second Swift Proxy Node

Okay, thanks! I'd be fine using the IP of the node too?

2014-10-09 15:33:54 -0600 received badge  Commentator
2014-10-09 15:18:03 -0600 commented answer Second Swift Proxy Node

Can you explain why a VIP is necessary? Just curious. Have a dedicated node for HAProxy.

2014-10-09 13:14:44 -0600 received badge  Supporter (source)
2014-10-09 11:58:14 -0600 asked a question Second Swift Proxy Node

I'm adding a second proxy node to my Swift cluster, and I have a few questions. I installed the swift-proxy service, adjusted memcached.conf (-l PROXY_LOCAL_NET_IP_new_node), and added memcache_servers = PROXY_LOCAL_NET_IP_old_node:11211, PROXY_LOCAL_NET_IP_new_node:11211 to the proxy-server.conf files on both proxy nodes. Is it enough now to copy {account,container,object}.ring.gz and {account,container,object}.builder to the new proxy node or do I need to create new rings and add the nodes to each ring?

What about the endpoint in Keystone? Do I leave it pointing at only the first proxy node?

Thank you...

2014-09-26 05:37:03 -0600 received badge  Notable Question (source)
2014-09-25 20:23:49 -0600 received badge  Popular Question (source)
2014-09-25 15:39:28 -0600 commented question Cinder and Keystone Authorization Error (HTTP 401)

Edited above.

2014-09-25 15:38:51 -0600 received badge  Editor (source)
2014-09-25 15:04:51 -0600 asked a question Cinder and Keystone Authorization Error (HTTP 401)

I'm having difficulty getting Cinder and Keystone to talk properly (I've tried several other solutions related to this question to no avail). I have an RDO deployment of OpenStack on a bare metal (the controller) and Cinder installed on a separate node (the node). I have confirmed connectivity between the controller and the node. On the controller, I have deleted the endpoints for cinder and cinderv2 and created new ones that point to the node. I have also deleted the cinder database on the controller and created and synced a rew one. Cinder-API and Cinder-Scheduler are running on the node, but when I try to run 'cinder list', I get the following error in cinder-api.log on the node:

WARNING [keystoneclient.middleware.auth_token] Unexpected response from keystone service: {u'error': {u'message': u'The request you have made requires authentication.', u'code': 401, u'title': u'Unauthorized'}}

On the controller, the following message shows in keystone.log:

WARNING keystone.common.wsgi [-] Authorization failed. The request you have made requires authentication. from <node_IP>

Here's my cinder.conf on the node:

[DEFAULT]
logdir = /var/log/cinder
state_path = /var/lib/cinder
lock_path = /var/lib/cinder/tmp
volumes_dir = /etc/cinder/volumes
iscsi_helper = tgtadm

api_paste_config = /etc/cinder/api-paste.ini
sql_connection = mysql://cinder:5d96c8fa075b400d@<controller_iP>/cinder
rpc_backend = cinder.openstack.common.rpc.impl_kombu
rootwrap_config = /etc/cinder/rootwrap.conf
auth_strategy = keystone
rabbit_host = <controller_IP>
rabbit_port = 5672
rabbit_hosts = <controller_IP>:5672
rabbit_use_ssl=False
rabbit_userid=guest
rabbit_password=guest
#rabbit_login_method=AMQPLAIN
rabbit_virtual_host=/
rabbit_ha_queues=False
notification_driver=cinder.openstack.common.notifier.rpc_notifier

amqp_durable_queues=False

[keystone_authtoken]
admin_tenant_name = services
admin_user = cinder
admin_password = passw0rd
auth_uri = http://<controller_IP>:5000/v2.0/
auth_host = <controller_IP>
auth_port = 35357
auth_protocol = http
signing_dirname = /tmp/keystone-signing-cinder

[database]
connection = mysql://cinder:5d96c8fa075b400d@<controller_IP>/cinder
idle_timeout=3600

And api-paste.ini on the node:

#############
# OpenStack #
#############

[composite:osapi_volume]
use = call:cinder.api:root_app_factory
/: apiversions
/v1: openstack_volume_api_v1
/v2: openstack_volume_api_v2

[composite:openstack_volume_api_v1]
use = call:cinder.api.middleware.auth:pipeline_factory
noauth = faultwrap sizelimit noauth apiv1
keystone = faultwrap sizelimit authtoken keystonecontext apiv1
keystone_nolimit = faultwrap sizelimit authtoken keystonecontext apiv1

[composite:openstack_volume_api_v2]
use = call:cinder.api.middleware.auth:pipeline_factory
noauth = faultwrap sizelimit noauth apiv2
keystone = faultwrap sizelimit authtoken keystonecontext apiv2
keystone_nolimit = faultwrap sizelimit authtoken keystonecontext apiv2

[filter:faultwrap]
paste.filter_factory = cinder.api.middleware.fault:FaultWrapper.factory

[filter:noauth]
paste.filter_factory = cinder.api.middleware.auth:NoAuthMiddleware.factory

[filter:sizelimit]
paste.filter_factory = cinder.api.middleware.sizelimit:RequestBodySizeLimiter.factory

[app:apiv1]
paste.app_factory = cinder.api.v1.router:APIRouter.factory

[app:apiv2]
paste.app_factory = cinder.api.v2.router:APIRouter.factory

[pipeline:apiversions]
pipeline = faultwrap osvolumeversionapp

[app:osvolumeversionapp]
paste.app_factory = cinder.api.versions:Versions.factory

##########
# Shared #
##########

[filter:keystonecontext]
paste.filter_factory = keystoneclient.middleware.auth_token:filter_factory
#paste.filter_factory = cinder.api.middleware.auth:CinderKeystoneContext.factory

[filter:authtoken]
paste.filter_factory = keystoneclient.middleware.auth_token:filter_factory
admin_tenant_name=services
auth_host=<controller_IP>
service_port=5000
auth_uri=http://<controller_IP>:5000/
auth_port=35357
service_host=<controller_IP>
service_protocol=http
admin_user=cinder
auth_protocol=http
admin_password= passw0rd

Output from 'cinder --debug list':

REQ: curl -i http://<controller_IP>:35357/v2.0/tokens -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "User-Agent: python-cinderclient" -d '{"auth": {"tenantName": "admin", "passwordCredentials": {"username": "admin", "password ...
(more)
2014-09-19 14:13:27 -0600 commented answer Install Cinder on Different Node than Controller

This guide: http://docs.openstack.org/icehouse/in... . So /etc/cinder/cinder.conf should be configured to point to DB on the main controller?

Also, you mentioned Glance config files above??

2014-09-18 10:54:48 -0600 marked best answer Install Cinder on Different Node than Controller

Variations of this question have been asked, but is there an installation guide for installing the Cinder service on a different node than the controller node?

Thank you in advance....

2014-09-18 10:54:48 -0600 commented answer Install Cinder on Different Node than Controller

The database (steps 2-4 on the install Cinder guide) should be created on the controller not the node with Cinder?

Thank you....

2014-09-18 10:47:22 -0600 received badge  Enthusiast