[Openstack] nova-network-snat weird behavior
Dear all, I am running FlatDHCPNetwork. I have two interfaces, em1 and em2. - em1 is my flat_interface for fixed (192.168.15.0/24) and node (192.168.14.0/24) ips. - em2 is my public_interface for floating ips (192.168.16.0/24). When I create an instance, I notice that the following iptable rule gets created: -A nova-network-snat -s 192.168.15.0/24 -o em2 -j SNAT --to-source 192.168.14.10 Strangely, the interface in the -o option seems to be always following the "public_interface = em2" configuration in '/etc/nova/nova.conf'. If I don't define it, then the rule that gets created is -A nova-network-snat -s 192.168.15.0/24 -o eth0 -j SNAT --to-source 192.168.14.10 This results in outgoing traffic from instances not being SNAT correctly, because the iptable rule is applied on the public_interface and not flat_network_bridge FWIW, I changed public_interface to vmnetbr0 (that bridges em1 and vnet0), and the instance was able to ping out. But that shouldn't be the correct configuration, should it? Can someone tell me what am I doing wrong? (I am running openstack-nova-network-2012.2-1 on fedora) /etc/nova/nova.conf public_interface = em2 flat_interface = em1 fixed_range = 192.168.15.0/24 floating_range = 192.168.16.0/24 flat_network_bridge = vmnetbr0 multi_host = True Regards, WP ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] cloud-init and resizing centos image
Dear all, I am trying to build a CentOS image. I followed the instructions here: at http://docs.openstack.org/essex/openstack-compute/starter/content/CentOS-de1592.html I have also added EPEL cloud-init package to the image that I build. I can boot the image fine, however, the root partition does not resize upon boot. I am reading around but the documentation is quite sketchy. All I know that I might need cloud-initramfs-growroot or something, but there's no docs on how to achieve that. Can I know if there's anyone on the list that has successfully create CentOS images and using cloud-init to expand the root partition? - WP ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] New instances stuck in BUILD
Dear all, I am running openstack grizzly on 2 nodes, with multi-host options and without conductor. Node 1 has compute, api, network, etc Node 2 has compute, network When launching new instances, those that are launched on the 1st node launches fine. Those not on node 2 gets stuck in BUILD. "nova show xxx" prints the following (snipped) | status | BUILD | | updated | 2013-04-25T11:37:29Z | | OS-EXT-STS:task_state | scheduling I've been reviewing the logs and there are no errors. I have a few questions and hope someone can help. 1) How do I start tracing this error? 2) In multi-host mode, are the compute nodes supposed to connect to AMQP of the main node, or themselves? I specified rabbit_host and it still shows nova-compute connecting to localhost. 3) In scheduler.log, there is the following 2013-04-25 19:37:29.064 WARNING nova.scheduler.host_manager [req-2272a45e-8e8a-4af0-96cd-b8a387e051fa 91cd099661f54df7bad0c7248c0451ca c91d0ed52321439c8b7d0c05b89bb0c8] No service for compute ID 2 Is this what is causing the problem? 4) If I were to use conductor in multi-host, do I need a conductor for each compute node? If not, how do I specify where is the conductor? Any advice is greatly appreciated. Thanks, WP ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] New instances stuck in BUILD
Dear all, I managed to solve this. If you are using qpid, you need rpc_backend=nova.rpc.impl_qpid qpid_hostname= if you are using rabbit, you need rabbit_host= to ensure that the correct amqp is set up. Cheers - WP On Thu, Apr 25, 2013 at 7:44 PM, YIP Wai Peng wrote: > Dear all, > > I am running openstack grizzly on 2 nodes, with multi-host options and > without conductor. > > Node 1 has compute, api, network, etc > > Node 2 has compute, network > > When launching new instances, those that are launched on the 1st node > launches fine. Those not on node 2 gets stuck in BUILD. "nova show xxx" > prints the following (snipped) > > | status | BUILD > | > | updated | 2013-04-25T11:37:29Z > | > | OS-EXT-STS:task_state | scheduling > > I've been reviewing the logs and there are no errors. I have a few > questions and hope someone can help. > > 1) How do I start tracing this error? > > 2) In multi-host mode, are the compute nodes supposed to connect to AMQP > of the main node, or themselves? I specified rabbit_host and it still shows > nova-compute connecting to localhost. > > 3) In scheduler.log, there is the following > 2013-04-25 19:37:29.064 WARNING nova.scheduler.host_manager > [req-2272a45e-8e8a-4af0-96cd-b8a387e051fa 91cd099661f54df7bad0c7248c0451ca > c91d0ed52321439c8b7d0c05b89bb0c8] No service for compute ID 2 > Is this what is causing the problem? > > 4) If I were to use conductor in multi-host, do I need a conductor for > each compute node? If not, how do I specify where is the conductor? > > Any advice is greatly appreciated. > > Thanks, > WP > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] nova-consoleauth timeout
Hi, I am having some problems with starting a novnc console. When I try to connect on the URL generated by "nova get-vnc-console", it is stuck with a "Starting VNC handshake" message. After a while, it will show "Failed to connect to server (code: 1006)". I am using nova-consoleauth with qpid. Digging deeper, in consoleauth.log it shows 2013-05-14 18:24:05.135 AUDIT nova.consoleauth.manager [req-0ffce0d5-bb14-4430-b73a-f68090502b6f None None] Checking Token: a70eab92-33e3-45b6-9132-ada441933ef7, True) 2013-05-14 18:25:05.162 ERROR nova.openstack.common.rpc.amqp [req-0ffce0d5-bb14-4430-b73a-f68090502b6f None None] Exception during message handling 2013-05-14 18:25:05.162 13764 TRACE nova.openstack.common.rpc.amqp Timeout: Timeout while waiting on RPC response. When I debug qpid, it shows the following 2013-05-14 18:14:27 debug No messages available to dispatch to consumer anonymous.891183d7-f7d8-4dd9-9499-103623fca15e:0::0 on queue 'consoleauth' 2013-05-14 18:14:27 debug Exception constructed: Exchange not found: 191c1daec221467fb6e9aa07979f5205 (qpid/broker/ExchangeRegistry.cpp:97) Can anybody help point me to the source of this error or where to look further? Help will be much appreciated. Regards, Wai Peng ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] nova-consoleauth timeout
I did more digging and found the following: 2013-05-15 13:56:25.881 AUDIT nova.consoleauth.manager [req-71725790-fe8d-4919-87aa-d5e0ce9870a7 None None] Checking Token: 2a276401-9cfd-4dee-a811-3ab9460b76dc, True) 2013-05-15 13:56:25.882 DEBUG nova.openstack.common.rpc.amqp [req-71725790-fe8d-4919-87aa-d5e0ce9870a7 None None] Making synchronous call on conductor ... multicall /usr/lib/python2.6/site-packages/nova/openstack/common/rpc/amqp.py:583 2013-05-15 13:56:25.883 DEBUG nova.openstack.common.rpc.amqp [req-71725790-fe8d-4919-87aa-d5e0ce9870a7 None None] MSG_ID is c8aea2d693cb4a1c8ac897226ec7c119 multicall /usr/lib/python2.6/site-packages/nova/openstack/common/rpc/amqp.py:586 2013-05-15 13:56:25.883 DEBUG nova.openstack.common.rpc.amqp [req-71725790-fe8d-4919-87aa-d5e0ce9870a7 None None] UNIQUE_ID is a29fff1d3f79418e94320e0c19d86a1b. _add_unique_id /usr/lib/python2.6/site-packages/nova/openstack/common/rpc/amqp.py:337 It seems like consoleauth is still trying to connect via amqp to a "conductor" topic? I already have in my config, [conductor] use_local = True so why is consoleauth still trying to connect to "conductor"? By the way, I started conductor and the console works. Does that mean that consoleauth relies on conductor? Can anyone shed some light on this? - WP On Tue, May 14, 2013 at 6:29 PM, YIP Wai Peng wrote: > Hi, > > I am having some problems with starting a novnc console. When I try to > connect on the URL generated by "nova get-vnc-console", it is stuck with a > "Starting VNC handshake" message. After a while, it will show "Failed to > connect to server (code: 1006)". I am using nova-consoleauth with qpid. > > Digging deeper, in consoleauth.log it shows > > 2013-05-14 18:24:05.135 AUDIT nova.consoleauth.manager > [req-0ffce0d5-bb14-4430-b73a-f68090502b6f None None] Checking Token: > a70eab92-33e3-45b6-9132-ada441933ef7, True) > 2013-05-14 18:25:05.162 ERROR nova.openstack.common.rpc.amqp > [req-0ffce0d5-bb14-4430-b73a-f68090502b6f None None] Exception during > message handling > > 2013-05-14 18:25:05.162 13764 TRACE nova.openstack.common.rpc.amqp > Timeout: Timeout while waiting on RPC response. > > When I debug qpid, it shows the following > > 2013-05-14 18:14:27 debug No messages available to dispatch to consumer > anonymous.891183d7-f7d8-4dd9-9499-103623fca15e:0::0 on queue 'consoleauth' > 2013-05-14 18:14:27 debug Exception constructed: Exchange not found: > 191c1daec221467fb6e9aa07979f5205 (qpid/broker/ExchangeRegistry.cpp:97) > > > Can anybody help point me to the source of this error or where to look > further? Help will be much appreciated. > > Regards, > Wai Peng > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
