[Openstack] Network problem: Instances from non-nova-network can't reach outside
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+git2017-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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Seek Help -- Strange Problem on Euca- Commands in Openstack Nova
Hi All, I encountered a problem configuring the cloud controller of Openstack Nova (Diablo release) on Ubuntu 11.10 x64 server. I've already done 'source novarc', the commands 'euca-describe-availability-zones verbose' and 'euca-describe-instances' works just fine, but 'euca-describe-images' cannot be carried out, with the following returning message: UnknownError: An unknown error has occurred. Please try your request again. Thus I cannot publish img on this server using 'cloud-publish-tarball'. All the configuration is identical to the official starter guide, BTW: http://docs.openstack.org/diablo/openstack-compute/starter/content/Nova_conf-d2s367.html Reboot doesn't help; I've even tried re-installed Ubuntu and all Nova components all over again and this problem is still there. Do someone know something about it? Any help is appreciated :) Thanks. Regards, Chang ___ 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] Test failures in keystone with python 2.6
Hello there, I've had some difficulties getting tests to pass in keystone on python 2.6 since some commits on December 23: https://review.openstack.org/#change,2504 I'm still a bit new to the differences between python 2.6 and 2.7, but I tried running the tests on a few different platforms anyway to see if I could find a pattern: Debian Squeeze (python 2.6.6) - failed Debian Wheezy (python 2.7.2) - passed Fedora 15 (python 2.7.1) - passed Here's the failure I'm having in python 2.6: http://pastie.org/pastes/3084725/text Is anyone else having a similar issue on python 2.6? I've triple-checked to make sure my python modules are up to date with what is required by tools/pip-requires within the keystone repository. -- Major Hayden ___ 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] Network problem: Instances from non-nova-network can't reach outside
I am not sure why, but sharing the same Network Interface means these three subnets share the same range. Using the same subnet for Management and Storage network is common place and should not be an issue, but sharing the Public network subnet can be tricky. http://blog.stackops.com/2011/06/13/understanding-stackops-openstack-nova-networking-configuration/ Is this your case? Probably someone here can better explain why share the same interface for the Public network is not a good idea. 2011/12/28 Lucio Cossio lucio_cos...@yahoo.com.br 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+git2017-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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Alisson Pontes __ Network Technology Evolution Researcher CPqD - Center for Research and Development in Telecommunications Tel.: +55 19 3705-4996 apon...@cpqd.com.br apo...@cpqd.com.br www.cpqd.com.br ___ 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] Seek Help -- Strange Problem on Euca- Commands in Openstack Nova
Hi Chang - I've seen this also as have these guys: https://answers.launchpad.net/nova/+question/179016 If you set --use_deprecated_auth in nova.conf to true it may work however I also looked through the bugs to see if it has been reported and couldn't find it, so perhaps this is fixed in trunk? Anne On Wednesday, December 28, 2011, Chang Liu changliu...@gmail.com wrote: Hi All, I encountered a problem configuring the cloud controller of Openstack Nova (Diablo release) on Ubuntu 11.10 x64 server. I've already done 'source novarc', the commands 'euca-describe-availability-zones verbose' and 'euca-describe-instances' works just fine, but 'euca-describe-images' cannot be carried out, with the following returning message: UnknownError: An unknown error has occurred. Please try your request again. Thus I cannot publish img on this server using 'cloud-publish-tarball'. All the configuration is identical to the official starter guide, BTW: http://docs.openstack.org/diablo/openstack-compute/starter/content/Nova_conf-d2s367.html Reboot doesn't help; I've even tried re-installed Ubuntu and all Nova components all over again and this problem is still there. Do someone know something about it? Any help is appreciated :) Thanks. Regards, Chang ___ 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] cannot launch instance via dasboard - glance auth error
Hi! You need to remove the %tenant_id% part from the Glance URI endpoint templates. Cheers, -jay On Thu, Dec 22, 2011 at 6:28 AM, denmat tu2bg...@gmail.com wrote: Hi all, I'm trying to launch an instance via the dashboard with the admin account. (I have been following: http://keystone.openstack.org/configuringservices.html). Error: The server has either erred or is incapable of performing the requested operation. (nova.api.openstack.v2): TRACE: File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 411, in _do_request (nova.api.openstack.v2): TRACE: raise exception.NotAuthorized(res.read()) (nova.api.openstack.v2): TRACE: NotAuthorized: You are not authorized to complete this action. In a previous post I was not able to access the images at all but that was fixed with a change of the endpoint templates. This is how I have set up the keystone endpoints: `keystone-manage endpointTemplates add Australia nova \ http://nova.local:8774/v1.1/%tenant_id% \ http://nova.local:8774/v1.1/%tenant_id% \ http://nova.local:8774/v1.1/%tenant_id% \ 1 1` `keystone-manage endpointTemplates add Australia glance \ http://glance.local:9292/v1.1/%tenant_id% \ http://glance.local:9292/v1.1/%tenant_id% \ http://glance.local:9292/v1.1/%tenant_id% \ 1 1` `keystone-manage endpointTemplates add Australia swift \ http://swift.local:8080/v1/AUTH_%tenant_id% \ http://swift.local:8080/v1.0/ \ http://swift.local:8080/v1/AUTH_%tenant_id% \ 1 1` `keystone-manage endpointTemplates add Australia keystone \ http://identity.local:5000/v2.0 \ http://identity.local:35357/v2.0 \ http://identity.local:5000/v2.0 \ 1 1` Neither the admin or me user can create instances. But the admin user could create a volume. | Roles | | id | name | service_id | description | | 1 | Admin | None | None | | 2 | KeystoneServiceAdmin | None | None | | 3 | Member | None | None | root@au-mel-kvm-3:~/setup# keystone-manage user list admin --- | Users | --- | id | name | enabled | tenant | --- | c75e1e8a074822078728c7ea3af9e7382 | admin | True | 828e80debe314d84823d606c587e867d | | 16b403c3811144b5976a740edeb4b868 | demo | True | ad1efcd098494058b451abaf438a8adb | | 67b9b4b622b03e88344e95601b180d6f8 | me | True | 05a72d14b4434a848c07f00544069d20 | --- root@au-mel-kvm-3:~/setup# keystone-manage role grant KeystoneServiceAdmin admin SUCCESS: Granted admin the KeystoneServiceAdmin role on None. root@au-mel-kvm-3:~/setup# keystone-manage tenant list --- | Tenants | --- | id | name | enabled | --- | 828e80debe314d84823d606c587e867d | admin | True | | ad1efcd098494058b451abaf438a8adb | demo | True | | 7871122791c34cc4b2ec03324f259c7b | developers | True | | 05a72d14b4434a848c07f00544069d20 | SysAdmins | True | | 6c6672c6bf0a4de08d772dca797a3447 | QA | True | --- Does anyone know how I can further investigate this? Thanks, Den ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] how to re-attach volume after vm and host down unexpectedly
Hey dude :)Remember my doc.In fact the main issue is not about the database state... it's about the ISCSI session that is lost after the node reboots.Check out my drp script. It does handle that for you :https://github.com/Razique/BashStuff/blob/master/SYSTEMS/OpenStack/SCR_5006_V00_NUAC-OPENSTACK-DRP-OpenStack.shThere are much more better way, but that script saved me several times. the part you are looking for is here : use nova; update volumes set mountpoint=NULL; update volumes set status="available" where status "error_deleting"; update volumes set attach_status="detached"; update volumes set instance_id=0; The other way around would be to cron a script that saves the iscsi sessions, and after a reboot, and BEFORE the openstack services start, recreate the sessions.I'll try that and see if it's working on a long-term basis. Nuage Co - Razique Mahrouarazique.mahr...@gmail.com Le 28 déc. 2011 à 08:23, DeadSun a écrit :I have write a blog about re-attachhttp://livemoon.dyndns.org/life/2011/12/how-to-re-attach-volume-in-openstack-if-vm-down-since-of-host-down.html I think my way is stupid . Better way should exists.The case is:The vm using volume, and then host where vm is runnning down because some reason. After host up, we can reboot vm using "nova reboot server", but the disk(filesystem mounted) in vm will be lost. In novaclient, using "nova volume-list", it show volume status is still in-used by this vm. At first, I want to detach it and re-attach it again. This way can work if we reboot vm in normal(host not down unexpectedly), but now it will show error like this: 2011-12-28 14:30:08,269 AUDIT nova.compute.manager [661dae13-05ec-4365-9f44-15d9072e000a admin 1] Detach volume 6 from mountpoint /dev/vdb on instance 74 (nova.rpc): TRACE: DiskNotFound: No disk at vdbI don't know how to write "vdb" to somewhere. But I think I can clear the database about it. So following steps I do:update nova database, volumes table, found this vm, set mountpoint to NULL, set status='available' , set attach_status='detach'logout iscsi volume in host where vm running, like this: $ sudo iscsiadm -m node -T iqn.2010-10.org.openstack:volume-0006 -p 10.200.200.5:23260 --logoutattach volume again using "nova volume-attach server volume /dev/vdb It can work, but I want to know , is this way correct ?-- 非淡薄无以明志，非宁静无以致远 ___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help : https://help.launchpad.net/ListHelp___ 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] Fwd: reconnecting to RabbitMQ
-- Forwarded message -- From: Roman Sokolkov rsokol...@gmail.com Date: 2011/12/28 Subject: Re: [Openstack] reconnecting to RabbitMQ To: Ask Solem a...@rabbitmq.com Hi! I tried to make Rabbit HA for Openstack. My first e-mail was little innacurate. I use two nodes with active/active rabbits with mirrored queues. Additionally I use Virtual IP. And all it managed by Pacemaker. Openstack uses this remote rabbitmq via VIP. I hardly reboot node with VIP and VIP moves to other node. In this case, connections on Openstack host staying forever in ESTABLISHED state(in py-amqlib 0.6.1 no tcp keepalive options). Openstack think that all good and doesn't try to reconnect. But I if correctly stop RabbitMQ, connections closed correctly and Openstack will try to reconnect. I solve this issue by adding tcp_keepalive options in py-amqlib(transport.py). It's very interesting what implemented in KAMQP. And how heartbeats work? 2011/12/28 Ask Solem a...@rabbitmq.com Not sure how I can help until the problem is identified. Kombu does not do automatic reconnecting by default, but provides the primitives necessary to implement it. amqplib does not support heartbeats so there may be cases where the client/server does not properly detect that the socket has been closed, this usually only a problem with some particular intermediate network components like routers and firewalls. Support for heartbeats is currently in the works, and I already have a rudimentary implementation at http://github.com/ask/kamqp/ if someone wants to try it out (though that probably requires some hacking). On 28 Dec 2011, at 10:51, Alexis Richardson wrote: Hi all, I am bcc'ing the author of Kombu in case he can help. alexis On Sun, Dec 25, 2011 at 2:11 AM, Chris Behrens chris.behr...@rackspace.com wrote: Hi Roman, Are you using diablo or trunk (both of which use kombu by default and should support reconnecting)? If so, can you 'egrep' for the following strings in logs and provide the output? You can reply to me directly so we're not spamming this list. Unable to connect to AMQP server Connected to AMQP server Re-established AMQP queues AMQP server on.*unreachable 'Failed to consume Failed to publish Thanks, - Chris On Dec 24, 2011, at 1:56 PM, Roman Sokolkov wrote: Hello! If for some reason rabbitmq has been down some time or connection was aborted, nova couldn't reconnect automatically and I need to restart all nova services manually. Additionally after restarting rabbit, If I make some call to API. For example, nova floating-ip-list only API reconnects automatically. Other nova services staying disconnected. Are there mechanisms to monitor establising of connections? And it difficult to add them? -- Best regards, Roman Sokolkov ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Regards, Roman Sokolkov -- Regards, Roman Sokolkov ___ 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] [Blueprint solidfire-scan-iscsidriver] Subclass in san.py to add Solidfire device support
I have submitted additions to nova/volume/san.py to add support for SolidFire iSCSI devices. I'm still learning the process so please be patient if I went about this incorrectly. I followed the docs to utilize the gerrit review system. https://blueprints.launchpad.net/nova/+spec/solidfire-san-iscsidriver Thanks, John ___ 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] AMQPChannelException: (406, uPRECONDITION_FAILED) - Diablo
Hi guys, Im facing this error http://pastebin.com/8X3j4g8e it seems like nova compute cannot redeclare the queue I tried : rabbmitmqctl app-stop; rabbmitmqctl reset; rabbmitmqctl app-start and deleting the quees with amqp ruby utils Restaring nova-compute and libvirt, still getting the same error Anybode faced this ? Regards Lele ___ 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] Writes are faster than reads in Swift
Thanks for explaining it. I read the source code and confirmed that read operations incur more drop_cache calls than write operations. However, I am not sure whether the additional calls result in significant overhead. Need some tests to verify. Gerald On Tue, Dec 13, 2011 at 11:32 PM, Michael Barton mike-launch...@weirdlooking.com wrote: I can't explain it off the top of my head. I don't have a swift installation to play with at the moment, but it's conceivable that posix_fadvise is slower than we expect (drop_cache is called more frequently during reads than writes, iirc). That could be tested by making drop_cache a no-op in the object server. Or running the object server under a profiler during both operations might shed some light on what is taking so much time. --Mike On Mon, Dec 12, 2011 at 8:44 AM, Zhenhua (Gerald) Guo jen...@gmail.com wrote: Hi, folks Recently, I have run some read/write tests for large files (400GB) in Swift. I found that writes were always faster than reads, which is kinda counter-intuitive. What may be the cause? Has anyone else seen the same problem? Gerald ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] Writes are faster than reads in Swift
Thanks. Now, I understand the access pattern Swift is designed for. Do you know some real applications (or scenarios, use cases) that benefit from that design (except static image files)? Gerald On Wed, Dec 14, 2011 at 1:17 AM, Michael Barton mike-launch...@weirdlooking.com wrote: On Tue, Dec 13, 2011 at 9:21 PM, Huang Zhiteng winsto...@gmail.com wrote: Can anyone explain why Swift doesn't want to utilize page cache _at all_? It's an artifact of the use case swift was built for - heavy on writes, and repeat reads (where a cache would help) are very rare. Having that memory available to cache dirents and inodes has a positive impact on performance, since a swift object server has so many files. The object server used to not drop caches if the file was small and the user wasn't authenticated, but I guess that's been factored out at some point. It'd be nice to have that logic pluggable or configurable somehow, since it does make swift kind of useless for things it'd otherwise be good at, like serving static files directly to browsers. - Mike ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] reconnecting to RabbitMQ
On Dec 28, 2011, at 5:36 AM, Ask Solem wrote: [...] amqplib does not support heartbeats so there may be cases where the client/server does not properly detect that the socket has been closed, this usually only a problem with some particular intermediate I received a private reply from Roman which seems to indicate this is what is happening. The OS is seeing the tcp connections as ESTABLISHED still, even though they are dead. Not much an application can do there Sounds like enabling tcp keepalive solved the problem for him. Doing heartbeats in the app itself is another way, as you mention. - Chris ___ 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] CRITICAL XENAPI_MISSING_PLUGIN xenhost
Hi, I'm trying to have both XenAPI (XCP, which I uploaded last week in SID) to work with Openstack (the version currently in experimental). Despite bug #909373 which I hacked my way around, nova-compute refuses to start with the below error. What am I doing wrong? What's that plugin thing about? Note that I've put stuff in /etc/xapi.d, like the xenhost python script, but it doesn't seem that's enough. By the way, if these have to be installed in the dom0, wouldn't it be wise to have it packaged as openstack-xcp-xapi-plugin or something similar? If so, what exactly should I put in this package? All what I have in plugins/xenserver/xenapi/etc/xapi.d? Should xcp-xapi be restarted after these are installed? Cheers, Thomas Goirand (zigo) ___ 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] CRITICAL XENAPI_MISSING_PLUGIN xenhost
On Thu, Dec 29, 2011, Thomas Goirand tho...@goirand.fr wrote: What am I doing wrong? What's that plugin thing about? Note that I've put stuff in /etc/xapi.d, like the xenhost python script, but it doesn't seem that's enough. Did you place it in /etc/xapi.d or /etc/xapi.d/plugins? The latter is the correct path. JE ___ 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] swift enforcing ssl?
On Tue, Dec 27, 2011 at 2:11 PM, andi abes andi.a...@gmail.com wrote: Does the swift proxy enforce SSL connections if it's configured with a cert/key file? Or is it assumed that there's an external entity performing that? The Swift proxy's SSL support is probably only useful for light testing - SSL in python (and especially with eventlet) has historically been slow and subtly broken. But basically the way it works, it's either in SSL mode or non-SSL mode. If you configure cert and key files, it switches to SSL mode. In a production environment, I'd suggest putting a reverse proxy like Pound in front of Swift to terminate SSL. Depending on your environment, it may also be a good idea to run that on separate hardware. That can get SSL termination CPU usage off the proxies, and provide all the usual benefits of load balancing like being able to remove proxy servers from rotation without downtime. -Michael ___ 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] swift enforcing ssl?
Do not use the ssl in the python for anything beyond noodling on a proof of concept. Between the python ssl and eventlet, ssl is unusably broken. This should probably be in red in the documentation. ___ 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] Live migration with mult_host - only ugly approach?
Alternate approach: Give all hosts the .1 gateway address: diff --git a/nova/network/manager.py b/nova/network/manager.py index 2d62581..e6a0ba8 100644 --- a/nova/network/manager.py +++ b/nova/network/manager.py @@ -477,8 +477,7 @@ class NetworkManager(manager.SchedulerDependentManager): def _get_dhcp_ip(self, context, network_ref, host=None): Get the proper dhcp address to listen on. # NOTE(vish): this is for compatibility -if not network_ref['multi_host']: -return network_ref['gateway'] +return network_ref['gateway'] if not host: host = self.host and make sure to create ebtables/iptables rules on every host that blocks traffic from that address and broadcast traffic on that network between the hosts. That way all of the hosts will have the .1 address on the bridge so migrated instances will still use the local ip as the gateway. Note: there is potential for some odd failures due to the mac address of the .1 address changing through migration and the vm having a different mac address in its arp cache, but theoretically it should be able to do a broadcast dhcp request to continue to dhcp. Vish On Dec 26, 2011, at 1:23 AM, 이준원 (Joonwon Lee) wrote: Dear all. We want to use Kei's live migration feature while adopting Vish’s multi_host network configuration, but there are problems as noted below by Vish. http://etherpad.openstack.org/live-migration-with-multi-host Is there any way to change the gateway of a VM instance? (i.e. is it possible to force a VM instance to request DHCP server again?) As I found no clue on this, it may be better to implement storing the history of live migration in DB. And we should keep the iptables rules and DHCP entries(in nova-br100.conf) for VM instances migrated in two or more hosts. I'm going to take this *ugly* approach without a good idea. The common gateway cannot be set for us because the network of VMs(10.x.x.x) is different from the network of external switches/routers(public IPs). Also the minimum DHCP expiration time is 120 seconds according to the man page. Two minutes are too long. Even worse, a VM instance won't change the gateway set by DHCP until rebooting with my test. Please help me finding a better approach, if any. Thanks in advance. Joonwon Lee ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] Network problem: Instances from non-nova-network can't reach outside
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+git2017-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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] AMQPChannelException: (406, uPRECONDITION_FAILED) - Diablo
Solved installing from trunk and restarting Rabbitmq on the controller node Regards On Wed, Dec 28, 2011 at 12:56 PM, Leandro Reox leandro.r...@gmail.comwrote: Hi guys, Im facing this error http://pastebin.com/8X3j4g8e it seems like nova compute cannot redeclare the queue I tried : rabbmitmqctl app-stop; rabbmitmqctl reset; rabbmitmqctl app-start and deleting the quees with amqp ruby utils Restaring nova-compute and libvirt, still getting the same error Anybode faced this ? Regards Lele ___ 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] CRITICAL XENAPI_MISSING_PLUGIN xenhost
- Original message - On Thu, Dec 29, 2011, Thomas Goirand tho...@goirand.fr wrote: What am I doing wrong? What's that plugin thing about? Note that I've put stuff in /etc/xapi.d, like the xenhost python script, but it doesn't seem that's enough. Did you place it in /etc/xapi.d or /etc/xapi.d/plugins? The latter is the correct path. JE The later, though I did that mistake first! :) any idea? Thomas ___ 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] CRITICAL XENAPI_MISSING_PLUGIN xenhost
You need chmod a+x /etc/xapi.d/plugins/* If you just want to install a package, Xen.org are building an RPM for XenServer / XCP with these plugins: http://downloads.xen.org/XCP/openstack/openstack-xen-plugins/. Cheers, Ewan. -Original Message- From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.net [mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net] On Behalf Of Thomas Goirand Sent: 28 December 2011 17:36 To: Johannes Erdfelt; openstack@lists.launchpad.net Subject: Re: [Openstack] CRITICAL XENAPI_MISSING_PLUGIN xenhost - Original message - On Thu, Dec 29, 2011, Thomas Goirand tho...@goirand.fr wrote: What am I doing wrong? What's that plugin thing about? Note that I've put stuff in /etc/xapi.d, like the xenhost python script, but it doesn't seem that's enough. Did you place it in /etc/xapi.d or /etc/xapi.d/plugins? The latter is the correct path. JE The later, though I did that mistake first! :) any idea? Thomas ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] CRITICAL XENAPI_MISSING_PLUGIN xenhost
On 12/29/2011 10:40 AM, Ewan Mellor wrote: You need chmod a+x /etc/xapi.d/plugins/* If you just want to install a package, Xen.org are building an RPM for XenServer / XCP with these plugins: http://downloads.xen.org/XCP/openstack/openstack-xen-plugins/. Cheers, Ewan. Hi, Thanks, but that's not what I'm trying to do here. I'm not interested in the RPM packages at all. I had a quick look though, in this package. I'm working on the Debian packaging of both XCP and OpenStack. I worked closely with Mike and Jon from Citrix, and last week, I uploaded XCP in Debian SID (that would be the first milestone of the project Kronos). I'm currently modifying nova packaging so that these files are packaged in a convenient nova-xcp-pluggins. I have found out (by myself) that the plugin directory in Debian isn't: /etc/xapi.d/pluggins but rather: /usr/lib/xcp/plugins which indeed makes a lot more sense in a packaged, FHS respecting, environment, and I know both Jon and Mike worked on that. Now, I'm having another error though: (nova): TRACE: Failure: ['XENAPI_PLUGIN_FAILURE', 'host_data', 'IOError', [Errno 2] No such file or directory: '/usr/etc/xenhost.conf'] I don't really mind the path issue (the issue is in the xenhost python script, I can fix it and set it to /etc/xcp/xenhost.conf instead), but what does the plugin expect to see in this file? Thomas ___ 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] CRITICAL XENAPI_MISSING_PLUGIN xenhost
It looks like it creates the file if it's not there -- it's just not smart enough to create /usr/etc if *that's* missing. I reckon if you fix the path, everything will work fine. I've no idea why that path was chosen even for XenServer (CentOS 5 based). Something like /etc/openstack would be more appropriate in either environment, in my opinion. Cheers, Ewan. -Original Message- From: Thomas Goirand [mailto:tho...@goirand.fr] Sent: 28 December 2011 21:25 To: Ewan Mellor Cc: Johannes Erdfelt; openstack@lists.launchpad.net Subject: Re: [Openstack] CRITICAL XENAPI_MISSING_PLUGIN xenhost On 12/29/2011 10:40 AM, Ewan Mellor wrote: You need chmod a+x /etc/xapi.d/plugins/* If you just want to install a package, Xen.org are building an RPM for XenServer / XCP with these plugins: http://downloads.xen.org/XCP/openstack/openstack-xen-plugins/. Cheers, Ewan. Hi, Thanks, but that's not what I'm trying to do here. I'm not interested in the RPM packages at all. I had a quick look though, in this package. I'm working on the Debian packaging of both XCP and OpenStack. I worked closely with Mike and Jon from Citrix, and last week, I uploaded XCP in Debian SID (that would be the first milestone of the project Kronos). I'm currently modifying nova packaging so that these files are packaged in a convenient nova-xcp-pluggins. I have found out (by myself) that the plugin directory in Debian isn't: /etc/xapi.d/pluggins but rather: /usr/lib/xcp/plugins which indeed makes a lot more sense in a packaged, FHS respecting, environment, and I know both Jon and Mike worked on that. Now, I'm having another error though: (nova): TRACE: Failure: ['XENAPI_PLUGIN_FAILURE', 'host_data', 'IOError', [Errno 2] No such file or directory: '/usr/etc/xenhost.conf'] I don't really mind the path issue (the issue is in the xenhost python script, I can fix it and set it to /etc/xcp/xenhost.conf instead), but what does the plugin expect to see in this file? Thomas ___ 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] Multinode installation (with devstack on the master)
Hi, I set up openstack on my second node with devstack as suggested. I could launch instances from the dashboard on the master node but couldn't view the vms on the second node with the VNC console in the dashboard. But the VNC console worked fine with instances launched on the master. On my laptop (with an ip of 10.3.0.1), i did the following: route add default gw 10.2.0.1 (master node's public ip) - i did this to access the private ips from my laptop vncviewer 192.168.2.1 (master node's private ip) - i could view the VM i launched on this node and i could ping my public network with this vncviewer 192.168.2.2 (second node's private ip) - i could view the VM running on this node but i couldn't ping other VMs and the public, private networks I think the problem is in my second node's network configuration. It has two NICs but only one of them is connected (eth1 with an ip of 192.168.2.2). Unlike the master node, eth0 is not connected to the public network on this node. nova.conf has the following parameters which i think may be the cause of this problem: PUBLIC_INTERFACE=eth0 VLAN_INTERFACE=eth0 FLAT_INTERFACE=eth0 In this case, how should i tweak my localrc file to get network access for my VMs? I have setup SNAT on the master node to provide external network access to machines in the network 192.168.2.0/24. All my VMs are given ips in the fixed range 192.168.3.0/24. Regarding crowbar, I haven't tried it yet. Once I read more about it, I'll give it a shot. Thanks and regards, Sagar ___ 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] Multinode installation (with devstack on the master)
In this case, how should i tweak my localrc file to get network access for my VMs? I have setup SNAT on the master node to provide external network access to machines in the network 192.168.2.0/24. All my VMs are given ips in the fixed range 192.168.3.0/24. Is each machine configured with an address in the 192.168.3.0/24 range, and is that network otherwise configured? It sounds like you have not fully configured the instance network. Typically for deployments with FlatDHCP, there are at least 3 networks - one public, one management, and one for instances. Each of these is usually on its on physical network interface or vlan. If this is just for testing, you can also try putting your vms inside your manage-net (say the upper part of 192.168.2.128/25, which can be convenient for testing but not generally a good idea. Anthony Regarding crowbar, I haven't tried it yet. Once I read more about it, I'll give it a shot. Thanks and regards, Sagar ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] CRITICAL XENAPI_MISSING_PLUGIN xenhost
Hi Ewan, Yes, fixing the path is easy, but *what is in this file*? (see below: it was what I was specifically asking for) I've been searching for quite some time on the net, and didn't find any info about this, and I have no access to a XCP / XenServer machine... Is that file shipped by default with a XenServer? Cheers, Thomas On 12/29/2011 01:47 PM, Ewan Mellor wrote: It looks like it creates the file if it's not there -- it's just not smart enough to create /usr/etc if *that's* missing. I reckon if you fix the path, everything will work fine. I've no idea why that path was chosen even for XenServer (CentOS 5 based). Something like /etc/openstack would be more appropriate in either environment, in my opinion. Cheers, Ewan. -Original Message- From: Thomas Goirand [mailto:tho...@goirand.fr] Sent: 28 December 2011 21:25 To: Ewan Mellor Cc: Johannes Erdfelt; openstack@lists.launchpad.net Subject: Re: [Openstack] CRITICAL XENAPI_MISSING_PLUGIN xenhost [...] '/usr/etc/xenhost.conf'] I don't really mind the path issue (the issue is in the xenhost python script, I can fix it and set it to /etc/xcp/xenhost.conf instead), but what does the plugin expect to see in this file? Thomas ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
