openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #06640
Re: Can't pimg
Hi,
I too have encountered the problem in the past. Maybe the attached mail
may help.
Thanks
Gary
From: openstack-bounces+garyk=radware.com@xxxxxxxxxxxxxxxxxxx
[mailto:openstack-bounces+garyk=radware.com@xxxxxxxxxxxxxxxxxxx] On
Behalf Of Leander Bessa
Sent: Tuesday, January 10, 2012 6:22 PM
To: Brebner, Gavin
Cc: openstack@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack] Can't pimg
I have already given permissions to ping and ssh.
output from euca-describe-group:
GROUP myproject default default
PERMISSION myproject default ALLOWS tcp 22
22 FROM CIDR 0.0.0.0/0
PERMISSION myproject default ALLOWS icmp -1
-1 FROM CIDR 0.0.0.0/0
On Tue, Jan 10, 2012 at 4:17 PM, Brebner, Gavin <gavin.brebner@xxxxxx>
wrote:
In my experience this usually this means you have forgotten to set up a
security group - you need to run euca-authorize / nova secgroup
commands. By default
there is no network access.
Gavin
From: openstack-bounces+gavin.brebner=hp.com@xxxxxxxxxxxxxxxxxxx
[mailto:openstack-bounces+gavin.brebner
<mailto:openstack-bounces%2Bgavin.brebner> =hp.com@xxxxxxxxxxxxxxxxxxx]
On Behalf Of Leander Bessa
Sent: Tuesday, January 10, 2012 5:08 PM
To: openstack@xxxxxxxxxxxxxxxxxxx
Subject: [Openstack] Can't pimg
Hello,
I'm having trouble accessing the instances that are being launched. I
have two nodes a controller and a compute. They are both running Ubuntu
11.10 (64bits) and using KVM as hypervisor. When i launch an instance, i
can see the instances is launched with the command
euca-describe-instances, however i can neither ping or ssh into it
through the controller node. I've checked the nova-network and
nova-manage logs and didn't find anything out of the ordinary. I've also
check the libvirt logs in the compute node and can't seem to find
anything wrong with it.
Previously i had a single node with qemu and everything worked fine. Now
that i switched to a multi-node environment with KVM things stopped
working. The controller has the ip 192.168.82.24 and the compute
192.168.111.220. Floating range for public IPs is 192.168.111.236-240.
Any ideas?
The controller the following nova.conf file:
--daemonize=1
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--verbose
--libvirt_type=kvm
--sql_connection=mysql://root:nova@192.168.82.24/nova
--s3_host=192.168.82.24
--rabbit_host=192.168.82.24
--ec2_host=192.168.82.24
--ec2_dmz_host=192.168.82.24
--ec2_url=http://192.168.82.24:8773/services/Cloud
--fixed_range=10.1.1.0/24
--network_size=64
--num_networks=1
--FAKE_subdomain=ec2
--public_interface=eth0
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--glance_host=192.168.82.24
--image_service=nova.image.glance.GlanceImageService
--glance_api_servers=192.168.82.24:9292
--vlan_start=100
--vlan_interface=eth1
--iscsi_ip_prefix=192.168.
The controller has this config file.
--daemonize=1
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--verbose
--libvirt_type=kvm
--sql_connection=mysql://root:nova@192.168.82.24/nova
--s3_host=192.168.82.24
--rabbit_host=192.168.82.24
--ec2_host=192.168.82.24
--ec2_dmz_host=192.168.82.24
--ec2_url=http://192.168.82.24:8773/services/Cloud
--fixed_range=10.1.1.0/24
--network_size=64
--num_networks=1
--FAKE_subdomain=ec2
--public_interface=eth0
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--glance_host=192.168.82.24
--image_service=nova.image.glance.GlanceImageService
--glance_api_servers=192.168.82.24:9292
--vlan_start=100
--vlan_interface=eth1
Regards,
Leander
--- Begin Message ---
In some cases when everything is on one interface you need to set your main bridge to promisc mode to get it to forward properly.
Try:
ip link set promisc on br100
Vish
On Dec 28, 2011, at 2:39 AM, Lucio Cossio wrote:
Hello Guys, I'm testing a dual node installation of OpenStack Nova with Glance, and i really hope someone can help me with my current problem.
My setup is like that:
- First Node : All nova components plus Glance
- Second Node : nova-compute
I'm using diablo version that was installed from the ubuntu repository, which i suppose is the nova 2011.3+git20111117-0ubuntu1 oneiric version.
For what a read, the second node only needs nova-compute ,but sometimes i see others saying about using nova-network together. I'm using machines that have just one network interface, so they are in the same network with other non-OpenStack computers (this network uses dhcp).
At the network configuration i'm using flatDHCP. The nova.conf file can be see here (the ip is not exactly what im using, is just a template): http://paste.openstack.org/show/3978/
So, i'm able to install and run virtual machines in both nodes. My problem is, for any instance that is running on the second node, i can't connect with the outside world (i can ssh and ping it from the first node, but not from an outside computer). Into the first node all goes fine.
If i restart nova-network (not exactly one time, sometimes more) at some point nova-network goes down, and then i'm able to ping the instances. Is like the configuration is good but the service break. The error that appears on logs is Stderr: 'RTNETLINK answers: File exists\n' - http://pastebin.com/qYhhYS6h
Currently i'm trying the same configuration in another 2 computers, using the diablo-final version of the rcb repository, as the openstack forum suggest. The errors is different. From what i remember (i'm not the only working with that) i was not even able to ping instances from outside after restarting the nova-network.
Then we tried to use nova-network with the second node too. After some time, new instances running on the second node start gracefully, and i can ping them from outside, however i can't run instances on the first node anymore. There's no log errors at nova or qemu folder, i can vnc to the instance but it appears stopped (cant do nothing).
I appreciate any help
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--- End Message ---
Follow ups
References
