Ask Your Question
0

Openstack on multiple nodes

asked 2012-02-22 18:00:52 -0600

Hi all. I've installed openstack on 3 nodes: node1: compute 192.168.1.102 node2: compute 192.168.1.107 node3: all services 192.168.1.100 the nova.conf is the same for all nodes: ##### --dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --force_dhcp_release=True --use_deprecated_auth=true --iscsi_helper=tgtadm --verbose --flagfile=/etc/nova/nova-compute.conf --sql_connection=mysql://root:nova@192.168.1.100/nova --network_manager=nova.network.manager.VlanManager --use_ipv6=false --s3_host=192.168.1.100 --cc_host=192.168.1.100 --fixed_range=10.0.0.0/12 --network_size=8 --FAKE_subdomain=ec2 --routing_source_ip=192.168.1.100 --connection_type=libvirt --vncproxy_url=http://192.168.1.100:6080 --daemonize=1 --rabbit_host=192.168.1.100 --osapi_host=192.168.1.100 --ec2_host=192.168.1.100 --image_service=nova.image.glance.GlanceImageService --glance_api_servers=192.168.1.100:9292 --use_syslog ##### When i try to connect to db from node1 and node2 all goes ok. When i try nova-manage db sync from node1 and node2 all goes ok. When i try to publish an image i get this output: ###### uec-publish-tarball ttylinux-uec-amd64-12.1_2.6.35-22_1.tar.gz mybuck WARNING: 'uec-publish-tarball' is now to 'cloud-publish-tarball'. Please update your tools or docs mer 22 feb 2012, 18.37.24, CET: ====== extracting image ====== kernel : ttylinux-uec-amd64-12.1_2.6.35-22_1-vmlinuz ramdisk: ttylinux-uec-amd64-12.1_2.6.35-22_1-initrd image : ttylinux-uec-amd64-12.1_2.6.35-22_1.img mer 22 feb 2012, 18.37.24, CET: ====== bundle/upload kernel ====== failed to upload bundle to mybuck/ttylinux-uec-amd64-12.1_2.6.35-22_1-vmlinuz.manifest.xml failed: euca-upload-bundle --bucket mybuck --manifest /tmp/cloud-publish-image.2D1xvS/ttylinux-uec-amd64-12.1_2.6.35-22_1-vmlinuz.manifest.xml Checking bucket: mybuck [Errno 111] Connection refusedfailed to upload kernel ######

Any ideas? I don't want only the answer, but also a method to check if all works fine. Sorry for english. Thx all.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2012-02-23 14:40:05 -0600

solved by changing tcp port 3333 for objectstore. Sorry.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2012-02-22 18:00:52 -0600

Seen: 41 times

Last updated: Feb 23 '12