Re: [Openstack] [OpenStack][Swift] Fast way of uploading 200GB of 200KB files to Swift
I've updated the keystoneclient to the lastest version available in GitHub and I'm still not getting any speedups. I've switched to the tempauth system and noticed an immediate increase in throughput (6.4 GB/day to 53.5 GB/day). Since I'm time-restrained, I'll stick with the tempauth system for now. I'll check back on the keystone token cache later. Thanks for all the help. On Tue, Jan 15, 2013 at 8:36 AM, Chmouel Boudjnah chmo...@chmouel.comwrote: as Chuck explain you usually would see that on the server, having said that if you use latest swiftclient from github you will be able to see the requests that swiftclient make via keystoneclient to keystone to get a token. If you go on the swift proxy server and only if you use a recent checked out version of swift you will be able to see the auth_token debug messages (the authentication middleware for validating a token to keystone) in your proxy-server log. I would advise to take a look at a devstack, running it with swift and see how it work on the swift proxy server console (in screen). On Mon, Jan 14, 2013 at 8:00 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Neither keystone nor swift proxy are producing any logs. I'm not sure what to do :S On Mon, Jan 14, 2013 at 6:50 PM, Chuck Thier cth...@gmail.com wrote: You would have to look at the proxy log to see if a request is being made. The results from the swift command line are just the calls that the client makes. The server still haves to validate the token on every request. -- Chuck On Mon, Jan 14, 2013 at 12:37 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Below is an output from Swift stat, since I don't see any requests to keystone, I'm assuming that memcache is being used right? REQ: curl -i http://192.168.111.215:8080/v1/AUTH_[ID] -X HEAD -H X-Auth-Token: [TOKEN] DEBUG:swiftclient:REQ: curl -i http://192.168.111.215:8080/v1/AUTH_[ID] -X HEAD -H X-Auth-Token: [TOKEN] RESP STATUS: 204 DEBUG:swiftclient:RESP STATUS: 204 Account: AUTH_[ID] Containers: 44 Objects: 4818 Bytes: 112284450 Accept-Ranges: bytes X-Timestamp: 1358184925.20885 X-Trans-Id: tx8cffb469c9c542be830db10a2b90d901 On Mon, Jan 14, 2013 at 6:31 PM, Dolph Mathews dolph.math...@gmail.com wrote: If memcache is being utilized by your keystone middleware, you should see keystone attaching to it on the first incoming request, e.g.: keystoneclient.middleware.auth_token [INFO]: Using Keystone memcache for caching token You may also want to use auth_token from keystoneclient = v0.2.0 if you're not already (instead of from keystone itself). -Dolph On Mon, Jan 14, 2013 at 11:43 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Are you by any chance referring to this topic https://lists.launchpad.net/openstack/msg08639.html regarding the keystone token cache? If so I've already added the configuration line and have not noticed any speedup :/ On Mon, Jan 14, 2013 at 5:19 PM, Leander Bessa Beernaert leande...@gmail.com wrote: I'm using the ubuntu 12.04 packages of the folsom repository by the way. On Mon, Jan 14, 2013 at 5:18 PM, Chuck Thier cth...@gmail.com wrote: On Mon, Jan 14, 2013 at 11:03 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Also, I'm unable to run the swift-bench with keystone. Hrm... That was supposed to be fixed with this bug: https://bugs.launchpad.net/swift/+bug/1011727 My keystone dev instance isn't working at the moment, but I'll see if I can get one of the team to take a look at it. -- Chuck ___ 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 ___ 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] [OpenStack][Swift] Fast way of uploading 200GB of 200KB files to Swift
Sorry, At the moment i'm unable to fetch the latest version of swift :s On Tue, Jan 15, 2013 at 12:14 PM, Chmouel Boudjnah chmo...@chmouel.comwrote: any chances you can try with latest swift as well and set : log_level = DEBUG in swift proxy-server.conf and what what the authtoken middleware is doing in the /var/log/syslog (or wherever syslog log on your distro). Chmouel. On Tue, Jan 15, 2013 at 12:09 PM, Leander Bessa Beernaert leande...@gmail.com wrote: I've updated the keystoneclient to the lastest version available in GitHub and I'm still not getting any speedups. I've switched to the tempauth system and noticed an immediate increase in throughput (6.4 GB/day to 53.5 GB/day). Since I'm time-restrained, I'll stick with the tempauth system for now. I'll check back on the keystone token cache later. Thanks for all the help. On Tue, Jan 15, 2013 at 8:36 AM, Chmouel Boudjnah chmo...@chmouel.comwrote: as Chuck explain you usually would see that on the server, having said that if you use latest swiftclient from github you will be able to see the requests that swiftclient make via keystoneclient to keystone to get a token. If you go on the swift proxy server and only if you use a recent checked out version of swift you will be able to see the auth_token debug messages (the authentication middleware for validating a token to keystone) in your proxy-server log. I would advise to take a look at a devstack, running it with swift and see how it work on the swift proxy server console (in screen). On Mon, Jan 14, 2013 at 8:00 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Neither keystone nor swift proxy are producing any logs. I'm not sure what to do :S On Mon, Jan 14, 2013 at 6:50 PM, Chuck Thier cth...@gmail.com wrote: You would have to look at the proxy log to see if a request is being made. The results from the swift command line are just the calls that the client makes. The server still haves to validate the token on every request. -- Chuck On Mon, Jan 14, 2013 at 12:37 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Below is an output from Swift stat, since I don't see any requests to keystone, I'm assuming that memcache is being used right? REQ: curl -i http://192.168.111.215:8080/v1/AUTH_[ID] -X HEAD -H X-Auth-Token: [TOKEN] DEBUG:swiftclient:REQ: curl -i http://192.168.111.215:8080/v1/AUTH_[ID] -X HEAD -H X-Auth-Token: [TOKEN] RESP STATUS: 204 DEBUG:swiftclient:RESP STATUS: 204 Account: AUTH_[ID] Containers: 44 Objects: 4818 Bytes: 112284450 Accept-Ranges: bytes X-Timestamp: 1358184925.20885 X-Trans-Id: tx8cffb469c9c542be830db10a2b90d901 On Mon, Jan 14, 2013 at 6:31 PM, Dolph Mathews dolph.math...@gmail.com wrote: If memcache is being utilized by your keystone middleware, you should see keystone attaching to it on the first incoming request, e.g.: keystoneclient.middleware.auth_token [INFO]: Using Keystone memcache for caching token You may also want to use auth_token from keystoneclient = v0.2.0 if you're not already (instead of from keystone itself). -Dolph On Mon, Jan 14, 2013 at 11:43 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Are you by any chance referring to this topic https://lists.launchpad.net/openstack/msg08639.html regarding the keystone token cache? If so I've already added the configuration line and have not noticed any speedup :/ On Mon, Jan 14, 2013 at 5:19 PM, Leander Bessa Beernaert leande...@gmail.com wrote: I'm using the ubuntu 12.04 packages of the folsom repository by the way. On Mon, Jan 14, 2013 at 5:18 PM, Chuck Thier cth...@gmail.com wrote: On Mon, Jan 14, 2013 at 11:03 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Also, I'm unable to run the swift-bench with keystone. Hrm... That was supposed to be fixed with this bug: https://bugs.launchpad.net/swift/+bug/1011727 My keystone dev instance isn't working at the moment, but I'll see if I can get one of the team to take a look at it. -- Chuck ___ 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 ___ 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] [OpenStack][Swift] Fast way of uploading 200GB of 200KB files to Swift
Hello all, I'm trying to upload 200GB of 200KB files to Swift. I'm using 4 clients (each hosted on a different machine) with 10 threads each uploading files using the official python-swiftclient. Each thread is uploading to a separate container. I have 5 storage nodes and 1 proxy node. The nodes are all running with a replication factor of 3. Each node has a quad-core i3 processor, 4GB of RAM and a gigabit network interface. Is there any way I can speed up this process? At the moment it takes about 20 seconds per file or more. Regards, Leander ___ 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] [OpenStack][Swift] Fast way of uploading 200GB of 200KB files to Swift
I forgot to mention that I'm also using the suggestions mentioned here: http://docs.openstack.org/developer/swift/deployment_guide.html#general-system-tuning On Mon, Jan 14, 2013 at 11:02 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello all, I'm trying to upload 200GB of 200KB files to Swift. I'm using 4 clients (each hosted on a different machine) with 10 threads each uploading files using the official python-swiftclient. Each thread is uploading to a separate container. I have 5 storage nodes and 1 proxy node. The nodes are all running with a replication factor of 3. Each node has a quad-core i3 processor, 4GB of RAM and a gigabit network interface. Is there any way I can speed up this process? At the moment it takes about 20 seconds per file or more. Regards, Leander ___ 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] [OpenStack][Swift] Fast way of uploading 200GB of 200KB files to Swift
By stopping, do you mean halt the service (kill the process) or is it a change in the configuration file? On Mon, Jan 14, 2013 at 1:20 PM, Robert van Leeuwen robert.vanleeu...@spilgames.com wrote: On Mon, Jan 14, 2013 at 11:02 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello all, I'm trying to upload 200GB of 200KB files to Swift. I'm using 4 clients (each hosted on a different machine) with 10 threads each uploading files using the official python-swiftclient. Each thread is uploading to a separate container. I have 5 storage nodes and 1 proxy node. The nodes are all running with a replication factor of 3. Each node has a quad-core i3 processor, 4GB of RAM and a gigabit network interface. Is there any way I can speed up this process? At the moment it takes about 20 seconds per file or more. It is very likely the system is starved on IO's. As a temporary workaround you can stop the object-replicator and object-auditor during the import to have less daemons competing for IO's. Some general troubleshooting tips: Use iotop to look for the processes consuming io's Assuming you use XFS: Make sure the filesystem is created with the appropriate inode size as described in the docs. (e.g. mkfs.xfs -i size=1024) Also with lots of files you need quite a bit of memory to cache the inodes into memory. Use the xfs runtime stats to get some indication about the cache: http://xfs.org/index.php/Runtime_Stats xs_dir_lookup and xs_ig_missed will give some indication how much IO's are spend on the inode lookups You can look at slabtop to see how much memory is used by the inode cache. Cheers, Robert ___ 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
[Openstack] [OpenStack][Swift] Reset Swift | Clear Swift and Account Database
Hello all, I've come to realize that my swift storage partitions are setup with the wrong node size. The only way for me to fix this is to format the partitions. I was wondering how I could reset swift (remove all data from stored files) without having to install it again. Regards, Leander ___ 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] [OpenStack][Swift] Fast way of uploading 200GB of 200KB files to Swift
I see. With replication switched off during upload, does inserting into various containers speed up the process or is it irrelevant? On Mon, Jan 14, 2013 at 1:49 PM, Robert van Leeuwen robert.vanleeu...@spilgames.com wrote: According to the info below, i think the current size is 256 right? If I format the storage partition, will that automatically clear all the contents from the storage or do I need to clean something else as well? Output from xfs_info: meta-data=/dev/sda3 isize=256agcount=4, agsize=13309312 blks Yes, this is the wrong inode size. When you format the disk on one node it will start to sync the removed data back from the other nodes to this machine (as long as the object-replicator is running on the other nodes). Note that this can take a pretty long time. (our nodes with millions of files more then a week to sync) If you want to throw away everything and start with a empty cluster my guess is you would need to stop everything and also remove the account and container databases. I've never done this so I can't tell you for sure if that does not break anything or if it needs any manual intervention to re-create the databases. Cheers, Robert ___ 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] [OpenStack][Swift] Fast way of uploading 200GB of 200KB files to Swift
Allow me to rephrase. I've read somewhere (can't remember where) that it would be faster to upload files if they would be uploaded to separate containeres. This was suggested for a standard swift installation with a certain replication factor. Since I'll be uploading the files with the replicators turned off, does it really matter if I insert a group of them in separate containeres? On Mon, Jan 14, 2013 at 2:27 PM, Robert van Leeuwen robert.vanleeu...@spilgames.com wrote: I see. With replication switched off during upload, does inserting into various containers speed up the process or is it irrelevant? I'm not sure what's your question but maybe this helps: In short: The replication daemon is walking across your files to check if any files need to be replicated to other nodes (e.g. when a node was broken or a new node is added to the cluster). Because it is scanning your filesystem it eats up io's. That is why it speeds up the system if you turn this off. The number off objects in a container impacts the sqlite databases. Each container is a SQLite database. The SQLite database will get slower with more objects in them. I think the recommendations for spinning disks is max a few million for one container, when using SSD's for the databases you can go quite a bit higher though. Cheers, Robert ___ 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] [OpenStack][Swift] Fast way of uploading 200GB of 200KB files to Swift
Ok, thanks for all the tips/help. Regards, Leander On Mon, Jan 14, 2013 at 3:21 PM, Robert van Leeuwen robert.vanleeu...@spilgames.com wrote: Allow me to rephrase. I've read somewhere (can't remember where) that it would be faster to upload files if they would be uploaded to separate containeres. This was suggested for a standard swift installation with a certain replication factor. Since I'll be uploading the files with the replicators turned off, does it really matter if I insert a group of them in separate containeres? My guess is this concerns the SQLite database load distribution. So yes, it still matters. Just to be clear: turning replicators off does not matter at ALL when putting files in a healthy cluster. Files will be replicated / put on all required nodes at the moment the put request is done. The put request will only give an OK when there is quorum writing the file (the file is stored on more than half of the required object nodes) The replicator daemons do not have anything to do with this. Cheers, Robert ___ 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] [OpenStack][Swift] Fast way of uploading 200GB of 200KB files to Swift
Well, I've fixed the node size and disabled the all the replicator and auditor processes. However, it is even slower now than it was before :/. Any suggestions? On Mon, Jan 14, 2013 at 3:23 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Ok, thanks for all the tips/help. Regards, Leander On Mon, Jan 14, 2013 at 3:21 PM, Robert van Leeuwen robert.vanleeu...@spilgames.com wrote: Allow me to rephrase. I've read somewhere (can't remember where) that it would be faster to upload files if they would be uploaded to separate containeres. This was suggested for a standard swift installation with a certain replication factor. Since I'll be uploading the files with the replicators turned off, does it really matter if I insert a group of them in separate containeres? My guess is this concerns the SQLite database load distribution. So yes, it still matters. Just to be clear: turning replicators off does not matter at ALL when putting files in a healthy cluster. Files will be replicated / put on all required nodes at the moment the put request is done. The put request will only give an OK when there is quorum writing the file (the file is stored on more than half of the required object nodes) The replicator daemons do not have anything to do with this. Cheers, Robert ___ 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] [OpenStack][Swift] Fast way of uploading 200GB of 200KB files to Swift
I'm getting around 5-6.5 GB a day of bytes written on Swift. I calculated this by calling swift stat sleep 60s swift stat. I did some calculation based on those values to get to the end result. Currently I'm resetting swift with a node size of 64, since 90% of the files are less than 70KB in size. I think that might help. On Mon, Jan 14, 2013 at 4:34 PM, Chuck Thier cth...@gmail.com wrote: Hey Leander, Can you post what performance you are getting? If they are all sharing the same GigE network, you might also check that the links aren't being saturated, as it is pretty easy to saturate pushing 200k files around. -- Chuck On Mon, Jan 14, 2013 at 10:15 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Well, I've fixed the node size and disabled the all the replicator and auditor processes. However, it is even slower now than it was before :/. Any suggestions? On Mon, Jan 14, 2013 at 3:23 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Ok, thanks for all the tips/help. Regards, Leander On Mon, Jan 14, 2013 at 3:21 PM, Robert van Leeuwen robert.vanleeu...@spilgames.com wrote: Allow me to rephrase. I've read somewhere (can't remember where) that it would be faster to upload files if they would be uploaded to separate containeres. This was suggested for a standard swift installation with a certain replication factor. Since I'll be uploading the files with the replicators turned off, does it really matter if I insert a group of them in separate containeres? My guess is this concerns the SQLite database load distribution. So yes, it still matters. Just to be clear: turning replicators off does not matter at ALL when putting files in a healthy cluster. Files will be replicated / put on all required nodes at the moment the put request is done. The put request will only give an OK when there is quorum writing the file (the file is stored on more than half of the required object nodes) The replicator daemons do not have anything to do with this. Cheers, Robert ___ 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 ___ 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] [OpenStack][Swift] Fast way of uploading 200GB of 200KB files to Swift
I'm currently using the swift client to upload files, would you recommend another approach? On Mon, Jan 14, 2013 at 4:43 PM, Chuck Thier cth...@gmail.com wrote: Using swift stat probably isn't the best way to determine cluster performance, as those stats are updated async, and could be delayed quite a bit as you are heavily loading the cluster. It also might be worthwhile to use a tool like swift-bench to test your cluster to make sure it is properly setup before loading data into the system. -- Chuck On Mon, Jan 14, 2013 at 10:38 AM, Leander Bessa Beernaert leande...@gmail.com wrote: I'm getting around 5-6.5 GB a day of bytes written on Swift. I calculated this by calling swift stat sleep 60s swift stat. I did some calculation based on those values to get to the end result. Currently I'm resetting swift with a node size of 64, since 90% of the files are less than 70KB in size. I think that might help. On Mon, Jan 14, 2013 at 4:34 PM, Chuck Thier cth...@gmail.com wrote: Hey Leander, Can you post what performance you are getting? If they are all sharing the same GigE network, you might also check that the links aren't being saturated, as it is pretty easy to saturate pushing 200k files around. -- Chuck On Mon, Jan 14, 2013 at 10:15 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Well, I've fixed the node size and disabled the all the replicator and auditor processes. However, it is even slower now than it was before :/. Any suggestions? On Mon, Jan 14, 2013 at 3:23 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Ok, thanks for all the tips/help. Regards, Leander On Mon, Jan 14, 2013 at 3:21 PM, Robert van Leeuwen robert.vanleeu...@spilgames.com wrote: Allow me to rephrase. I've read somewhere (can't remember where) that it would be faster to upload files if they would be uploaded to separate containeres. This was suggested for a standard swift installation with a certain replication factor. Since I'll be uploading the files with the replicators turned off, does it really matter if I insert a group of them in separate containeres? My guess is this concerns the SQLite database load distribution. So yes, it still matters. Just to be clear: turning replicators off does not matter at ALL when putting files in a healthy cluster. Files will be replicated / put on all required nodes at the moment the put request is done. The put request will only give an OK when there is quorum writing the file (the file is stored on more than half of the required object nodes) The replicator daemons do not have anything to do with this. Cheers, Robert ___ 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 ___ 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] [OpenStack][Swift] Reset Swift | Clear Swift and Account Database
Thanks! Regards, Leander On Mon, Jan 14, 2013 at 4:29 PM, Chuck Thier cth...@gmail.com wrote: Hi Leander, The following assumes that the cluster isn't in production yet: 1. Stop all services on all machines 2. Format and remount all storage devices 3. Re-create rings with the correct partition size 4. Push new rings out to all servers 5. Start services back up and test. -- Chuck On Mon, Jan 14, 2013 at 8:02 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello all, I've come to realize that my swift storage partitions are setup with the wrong node size. The only way for me to fix this is to format the partitions. I was wondering how I could reset swift (remove all data from stored files) without having to install it again. Regards, Leander ___ 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] [OpenStack][Swift] Fast way of uploading 200GB of 200KB files to Swift
I currently have 4 machines running 10 clients each uploading 1/40th of the data. More than 40 simultaneous clientes starts to severely affect Keystone's ability to handle these operations. On Mon, Jan 14, 2013 at 4:58 PM, Chuck Thier cth...@gmail.com wrote: That should be fine, but it doesn't have any way of reporting stats currently. You could use tools like ifstat to look at how much bandwidth you are using. You can also look at how much cpu the swift tool is using. Depending on how your data is setup, you could run several swift-client processes in parallel until you max either your network or cpu. I would start with one client first, until you max it out, then move on to the next. -- Chuck On Mon, Jan 14, 2013 at 10:45 AM, Leander Bessa Beernaert leande...@gmail.com wrote: I'm currently using the swift client to upload files, would you recommend another approach? On Mon, Jan 14, 2013 at 4:43 PM, Chuck Thier cth...@gmail.com wrote: Using swift stat probably isn't the best way to determine cluster performance, as those stats are updated async, and could be delayed quite a bit as you are heavily loading the cluster. It also might be worthwhile to use a tool like swift-bench to test your cluster to make sure it is properly setup before loading data into the system. -- Chuck On Mon, Jan 14, 2013 at 10:38 AM, Leander Bessa Beernaert leande...@gmail.com wrote: I'm getting around 5-6.5 GB a day of bytes written on Swift. I calculated this by calling swift stat sleep 60s swift stat. I did some calculation based on those values to get to the end result. Currently I'm resetting swift with a node size of 64, since 90% of the files are less than 70KB in size. I think that might help. On Mon, Jan 14, 2013 at 4:34 PM, Chuck Thier cth...@gmail.com wrote: Hey Leander, Can you post what performance you are getting? If they are all sharing the same GigE network, you might also check that the links aren't being saturated, as it is pretty easy to saturate pushing 200k files around. -- Chuck On Mon, Jan 14, 2013 at 10:15 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Well, I've fixed the node size and disabled the all the replicator and auditor processes. However, it is even slower now than it was before :/. Any suggestions? On Mon, Jan 14, 2013 at 3:23 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Ok, thanks for all the tips/help. Regards, Leander On Mon, Jan 14, 2013 at 3:21 PM, Robert van Leeuwen robert.vanleeu...@spilgames.com wrote: Allow me to rephrase. I've read somewhere (can't remember where) that it would be faster to upload files if they would be uploaded to separate containeres. This was suggested for a standard swift installation with a certain replication factor. Since I'll be uploading the files with the replicators turned off, does it really matter if I insert a group of them in separate containeres? My guess is this concerns the SQLite database load distribution. So yes, it still matters. Just to be clear: turning replicators off does not matter at ALL when putting files in a healthy cluster. Files will be replicated / put on all required nodes at the moment the put request is done. The put request will only give an OK when there is quorum writing the file (the file is stored on more than half of the required object nodes) The replicator daemons do not have anything to do with this. Cheers, Robert ___ 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 ___ 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] [OpenStack][Swift] Fast way of uploading 200GB of 200KB files to Swift
Also, I'm unable to run the swift-bench with keystone.
I always get this error:
Traceback (most recent call last):
File /usr/bin/swift-bench, line 149, in module
controller.run()
File /usr/lib/python2.7/dist-packages/swift/common/bench.py, line 159,
in run
puts = BenchPUT(self.logger, self.conf, self.names)
File /usr/lib/python2.7/dist-packages/swift/common/bench.py, line 241,
in __init__
Bench.__init__(self, logger, conf, names)
File /usr/lib/python2.7/dist-packages/swift/common/bench.py, line 55,
in __init__
auth_version=self.auth_version)
File /usr/lib/python2.7/dist-packages/swiftclient/client.py, line 281,
in get_auth
if (kwargs['os_options'].get('object_storage_url') and
KeyError: 'os_options'
Here's my config file:
[bench]
auth = http://192.168.111.202:5000/v2.0
user = [tenant]:[user]
key = [key]
auth_version = 2
log-level = INFO
timeout = 10
put_concurrency = 10
get_concurrency = 10
lower_object_size = 20
upper_object_size = 2
num_objects = 1000
num_gets = 1
num_containers = 20
delete = yes
On Mon, Jan 14, 2013 at 5:01 PM, Leander Bessa Beernaert
leande...@gmail.com wrote:
I currently have 4 machines running 10 clients each uploading 1/40th of
the data. More than 40 simultaneous clientes starts to severely affect
Keystone's ability to handle these operations.
On Mon, Jan 14, 2013 at 4:58 PM, Chuck Thier cth...@gmail.com wrote:
That should be fine, but it doesn't have any way of reporting stats
currently. You could use tools like ifstat to look at how much
bandwidth you are using. You can also look at how much cpu the swift
tool is using. Depending on how your data is setup, you could run
several swift-client processes in parallel until you max either your
network or cpu. I would start with one client first, until you max it
out, then move on to the next.
--
Chuck
On Mon, Jan 14, 2013 at 10:45 AM, Leander Bessa Beernaert
leande...@gmail.com wrote:
I'm currently using the swift client to upload files, would you
recommend
another approach?
On Mon, Jan 14, 2013 at 4:43 PM, Chuck Thier cth...@gmail.com wrote:
Using swift stat probably isn't the best way to determine cluster
performance, as those stats are updated async, and could be delayed
quite a bit as you are heavily loading the cluster. It also might be
worthwhile to use a tool like swift-bench to test your cluster to make
sure it is properly setup before loading data into the system.
--
Chuck
On Mon, Jan 14, 2013 at 10:38 AM, Leander Bessa Beernaert
leande...@gmail.com wrote:
I'm getting around 5-6.5 GB a day of bytes written on Swift. I
calculated
this by calling swift stat sleep 60s swift stat. I did some
calculation based on those values to get to the end result.
Currently I'm resetting swift with a node size of 64, since 90% of
the
files
are less than 70KB in size. I think that might help.
On Mon, Jan 14, 2013 at 4:34 PM, Chuck Thier cth...@gmail.com
wrote:
Hey Leander,
Can you post what performance you are getting? If they are all
sharing the same GigE network, you might also check that the links
aren't being saturated, as it is pretty easy to saturate pushing
200k
files around.
--
Chuck
On Mon, Jan 14, 2013 at 10:15 AM, Leander Bessa Beernaert
leande...@gmail.com wrote:
Well, I've fixed the node size and disabled the all the replicator
and
auditor processes. However, it is even slower now than it was
before
:/.
Any
suggestions?
On Mon, Jan 14, 2013 at 3:23 PM, Leander Bessa Beernaert
leande...@gmail.com wrote:
Ok, thanks for all the tips/help.
Regards,
Leander
On Mon, Jan 14, 2013 at 3:21 PM, Robert van Leeuwen
robert.vanleeu...@spilgames.com wrote:
Allow me to rephrase.
I've read somewhere (can't remember where) that it would be
faster
to
upload files if they would be uploaded to separate
containeres.
This was suggested for a standard swift installation with a
certain
replication factor.
Since I'll be uploading the files with the replicators turned
off,
does
it really matter if I insert a group of them in separate
containeres?
My guess is this concerns the SQLite database load distribution.
So yes, it still matters.
Just to be clear: turning replicators off does not matter at ALL
when
putting files in a healthy cluster.
Files will be replicated / put on all required nodes at the
moment
the
put request is done.
The put request will only give an OK when there is quorum
writing
the
file (the file is stored on more than half of the required
object
nodes)
The replicator daemons do not have anything to do with this.
Cheers,
Robert
___
Mailing list: https://launchpad.net
Re: [Openstack] [OpenStack][Swift] Fast way of uploading 200GB of 200KB files to Swift
I'm using the ubuntu 12.04 packages of the folsom repository by the way. On Mon, Jan 14, 2013 at 5:18 PM, Chuck Thier cth...@gmail.com wrote: On Mon, Jan 14, 2013 at 11:03 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Also, I'm unable to run the swift-bench with keystone. Hrm... That was supposed to be fixed with this bug: https://bugs.launchpad.net/swift/+bug/1011727 My keystone dev instance isn't working at the moment, but I'll see if I can get one of the team to take a look at it. -- Chuck ___ 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] [OpenStack][Swift] Fast way of uploading 200GB of 200KB files to Swift
Are you by any chance referring to this topic https://lists.launchpad.net/openstack/msg08639.html regarding the keystone token cache? If so I've already added the configuration line and have not noticed any speedup :/ On Mon, Jan 14, 2013 at 5:19 PM, Leander Bessa Beernaert leande...@gmail.com wrote: I'm using the ubuntu 12.04 packages of the folsom repository by the way. On Mon, Jan 14, 2013 at 5:18 PM, Chuck Thier cth...@gmail.com wrote: On Mon, Jan 14, 2013 at 11:03 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Also, I'm unable to run the swift-bench with keystone. Hrm... That was supposed to be fixed with this bug: https://bugs.launchpad.net/swift/+bug/1011727 My keystone dev instance isn't working at the moment, but I'll see if I can get one of the team to take a look at it. -- Chuck ___ 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] [OpenStack][Swift] Fast way of uploading 200GB of 200KB files to Swift
Neither keystone nor swift proxy are producing any logs. I'm not sure what to do :S On Mon, Jan 14, 2013 at 6:50 PM, Chuck Thier cth...@gmail.com wrote: You would have to look at the proxy log to see if a request is being made. The results from the swift command line are just the calls that the client makes. The server still haves to validate the token on every request. -- Chuck On Mon, Jan 14, 2013 at 12:37 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Below is an output from Swift stat, since I don't see any requests to keystone, I'm assuming that memcache is being used right? REQ: curl -i http://192.168.111.215:8080/v1/AUTH_[ID] -X HEAD -H X-Auth-Token: [TOKEN] DEBUG:swiftclient:REQ: curl -i http://192.168.111.215:8080/v1/AUTH_[ID]-X HEAD -H X-Auth-Token: [TOKEN] RESP STATUS: 204 DEBUG:swiftclient:RESP STATUS: 204 Account: AUTH_[ID] Containers: 44 Objects: 4818 Bytes: 112284450 Accept-Ranges: bytes X-Timestamp: 1358184925.20885 X-Trans-Id: tx8cffb469c9c542be830db10a2b90d901 On Mon, Jan 14, 2013 at 6:31 PM, Dolph Mathews dolph.math...@gmail.com wrote: If memcache is being utilized by your keystone middleware, you should see keystone attaching to it on the first incoming request, e.g.: keystoneclient.middleware.auth_token [INFO]: Using Keystone memcache for caching token You may also want to use auth_token from keystoneclient = v0.2.0 if you're not already (instead of from keystone itself). -Dolph On Mon, Jan 14, 2013 at 11:43 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Are you by any chance referring to this topic https://lists.launchpad.net/openstack/msg08639.html regarding the keystone token cache? If so I've already added the configuration line and have not noticed any speedup :/ On Mon, Jan 14, 2013 at 5:19 PM, Leander Bessa Beernaert leande...@gmail.com wrote: I'm using the ubuntu 12.04 packages of the folsom repository by the way. On Mon, Jan 14, 2013 at 5:18 PM, Chuck Thier cth...@gmail.com wrote: On Mon, Jan 14, 2013 at 11:03 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Also, I'm unable to run the swift-bench with keystone. Hrm... That was supposed to be fixed with this bug: https://bugs.launchpad.net/swift/+bug/1011727 My keystone dev instance isn't working at the moment, but I'll see if I can get one of the team to take a look at it. -- Chuck ___ 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] [OpenStack][Swift] Cannot perform multiple requests with Python API
I'm still getting the same error. Here's what I did:
- git clone https://github.com/openstack/python-swiftclient
- cd python-swiftclient
- sudo python setup.py install
- Repeated the previous procedures
Did it not install correctly?
On Tue, Jan 8, 2013 at 3:47 PM, Chmouel Boudjnah chmo...@chmouel.comwrote:
I am not sure why it does that (works fine for me), can you try with the
git version to see if you can reproduce ?
Thanks,
Chmouel.
On Mon, Jan 7, 2013 at 7:31 PM, Leander Bessa Beernaert
leande...@gmail.com wrote:
Hello all,
I'm having an issue when using the Python API for swift [1]. I am unable
to do two sequential operations. The first operation works and the second
ceases to work. Is this expected, or is this a bug?
I'm using Ubuntu 12.04 with the Folsom Packages.
Example output (Python Interpreter):
import swiftclient
swiftclient.get_container([URL],[TOKEN],'test')
({'content-length': '174', 'x-container-object-count': '1',
'accept-ranges': 'bytes', 'x-container-bytes-used': '200', 'x-timestamp':
'1357299184.84634', 'date': 'Mon, 07 Jan 2013 18:25:41 GMT',
'content-type': 'application/json; charset=utf-8'}, [{'bytes': 200,
'last_modified': '2013-01-07T18:07:17.289060', 'hash':
'fbaf48ec981a5eecdb57b929fdd426e8', 'name': 'test_object', 'content_type':
'application/octet-stream'}])
swiftclient.get_container([URL],[TOKEN],'test')
Traceback (most recent call last):
File stdin, line 1, in module
File /usr/lib/python2.7/dist-packages/swiftclient/client.py, line
487, in get_container
resp = conn.getresponse()
File /usr/lib/python2.7/dist-packages/swift/common/bufferedhttp.py,
line 103, in getresponse
logging.debug(_(HTTP PERF: %(time).5f seconds to %(method)s
TypeError: 'tuple' object is not callable
Regards,
Leander
[1] https://github.com/openstack/python-swiftclient
___
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
[Openstack] [OpenStack][Swift] Cannot perform multiple requests with Python API
Hello all,
I'm having an issue when using the Python API for swift [1]. I am unable to
do two sequential operations. The first operation works and the second
ceases to work. Is this expected, or is this a bug?
I'm using Ubuntu 12.04 with the Folsom Packages.
Example output (Python Interpreter):
import swiftclient
swiftclient.get_container([URL],[TOKEN],'test')
({'content-length': '174', 'x-container-object-count': '1',
'accept-ranges': 'bytes', 'x-container-bytes-used': '200', 'x-timestamp':
'1357299184.84634', 'date': 'Mon, 07 Jan 2013 18:25:41 GMT',
'content-type': 'application/json; charset=utf-8'}, [{'bytes': 200,
'last_modified': '2013-01-07T18:07:17.289060', 'hash':
'fbaf48ec981a5eecdb57b929fdd426e8', 'name': 'test_object', 'content_type':
'application/octet-stream'}])
swiftclient.get_container([URL],[TOKEN],'test')
Traceback (most recent call last):
File stdin, line 1, in module
File /usr/lib/python2.7/dist-packages/swiftclient/client.py, line 487,
in get_container
resp = conn.getresponse()
File /usr/lib/python2.7/dist-packages/swift/common/bufferedhttp.py,
line 103, in getresponse
logging.debug(_(HTTP PERF: %(time).5f seconds to %(method)s
TypeError: 'tuple' object is not callable
Regards,
Leander
[1] https://github.com/openstack/python-swiftclient
___
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] [OpenStack][Swift] Calculating necessary disk space with replication
Thanks for the info! Regards, Leander On Thu, Jan 3, 2013 at 7:08 PM, Samuel Merritt s...@swiftstack.com wrote: On 1/3/13 7:07 AM, Leander Bessa Beernaert wrote: Hello all, Could some please confirm my analysis of the ring creation in swift? I need to run a few benchmarks on a set of data (200GB) total and need it to be replicated at least 3 times. From the Swift docs [1], I understood that the command below create the ring for a partition sized 2^18 and 3 replicas. swift-ring-builder account.builder create 18 3 1 # swift-ring-builder container.builder create 18 3 1 # swift-ring-builder object.builder create 18 3 1 Now, in my case i should use the values 28 3 1 right, or should i factor in the replication and instead use 30 3 1? Neither one. The partitions in the Swift ring are subsets of the range of a hash function; they don't have anything to do with the number of bytes of storage in your cluster. General rule of thumb is to figure out how many drives your cluster will ever have at its largest, and then choose the smallest part_power that gives you ~100 partitions per drive. I have at the moment 1 proxy node and 5 storage nodes with a 200GB storage partition. This won't be enough to accomodate everything right? I don't see why not. You've got 200GB stored data * 3 replicas = 600GB raw data used, and you've got 1000GB of disk. Even with a little bit of overhead for accounts and containers, that's still plenty of disk. __**_ Mailing list: https://launchpad.net/~**openstackhttps://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~**openstackhttps://launchpad.net/~openstack More help : https://help.launchpad.net/**ListHelphttps://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] [OpenStack][Swift] Calculating necessary disk space with replication
Hello all, Could some please confirm my analysis of the ring creation in swift? I need to run a few benchmarks on a set of data (200GB) total and need it to be replicated at least 3 times. From the Swift docs [1], I understood that [1] http://docs.openstack.org/trunk/openstack-compute/install/apt/content/installing-and-configuring-the-proxy-node.html ___ 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] [OpenStack][Swift] Calculating necessary disk space with replication
Hello all, Could some please confirm my analysis of the ring creation in swift? I need to run a few benchmarks on a set of data (200GB) total and need it to be replicated at least 3 times. From the Swift docs [1], I understood that the command below create the ring for a partition sized 2^18 and 3 replicas. swift-ring-builder account.builder create 18 3 1 # swift-ring-builder container.builder create 18 3 1 # swift-ring-builder object.builder create 18 3 1 Now, in my case i should use the values 28 3 1 right, or should i factor in the replication and instead use 30 3 1? I have at the moment 1 proxy node and 5 storage nodes with a 200GB storage partition. This won't be enough to accomodate everything right? Also, sorry for the split email, I pressed the send instead of the save button :S. Regards, Leander On Thu, Jan 3, 2013 at 3:01 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello all, Could some please confirm my analysis of the ring creation in swift? I need to run a few benchmarks on a set of data (200GB) total and need it to be replicated at least 3 times. From the Swift docs [1], I understood that [1] http://docs.openstack.org/trunk/openstack-compute/install/apt/content/installing-and-configuring-the-proxy-node.html ___ 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] [OpenStack][Cinder] ISCSITargetCreateFailed: Failed to create iscsi target for volume
Hello all, I'm having trouble getting Cinder to create volumes. I'm using a single install of OpenStack Folsom on Ubuntu 12.04 and a lvm volume with 40 GB labeled cinder-volumes. # Output from vgs: VG #PV #LV #SN Attr VSize VFree cinder-volumes 1 0 0 wz--n- 45.69g 45.69g Every time I try to create a volume I get the error ISCSITargetCreateFailed: Failed to create iscsi target for volume. I've already tried following suggestions from this topic [1], but it doesn't make any diference. One thing I do notice is, even though the volume creation ended in error, the equivalent space is used in the lvm volume. For instance, after the error operation on the creation of a 1GB volume, vgs reports the following: VG #PV #LV #SN Attr VSize VFree cinder-volumes 1 1 0 wz--n- 45.69g 44.69g As you can see, 1GB has been allocated. Below you can find my configuration files. # /etc/tgt/targets.conf: include /etc/tgt/conf.d/cinder_tgt.conf include /etc/tgt/conf.d/cinder.conf include /etc/tgt/conf.d/nova_tgt.conf default-driver iscsi # /etc/tgt/conf.d/cinder_tgt.conf nclude /var/lib/cinder/volumes/* # /etc/tgt/conf.d/cinder.conf include /var/lib/cinder/volumes/* # /etc/tgt/conf.d/nova_tgt.conf include /etc/nova/volumes/ #volume config in nova.conf volume_group=cinder-volumes volume_name_template=volume-%08x iscsi_helper=tgtadm iscsi_ip_prefix=192.168.111.218 volume_api_class=nova.volume.cinder.API Any ideas in regards to what might be wrong? Regards, Leander [1] https://bugs.launchpad.net/cinder/+bug/1057904 ___ 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] [OpenStack][Cinder] ISCSITargetCreateFailed: Failed to create iscsi target for volume
Reply is inlined below. On Wed, Jan 2, 2013 at 10:41 AM, Balamurugan V G balamuruga...@gmail.comwrote: Is that a typo in your configuration or a copy pase error: # /etc/tgt/conf.d/cinder_tgt.conf nclude /var/lib/cinder/volumes/* The 'i' is missing in 'include'. If its only a copy paste error in the mail, make sure you have the following running: That was a copy paste typo, the original file is correct. root@openstack-vm:~# ps -ef | grep cinder root 3636 1 0 06:53 ?00:00:33 /usr/bin/python /usr/local/bin/cinder-volume root 25433 1 0 06:46 ?00:00:01 /usr/bin/python /usr/local/bin/cinder-api --config-file /etc/cinder/cinder.conf root 25937 1 0 06:46 ?00:00:32 /usr/bin/python /usr/local/bin/cinder-scheduler --config-file /etc/cinder/cinder.conf root@openstack-vm:~# ps -ef | grep tgt root 31176 31174 0 06:49 ?00:00:03 tgtd root@openstack-vm:~# # ps -ef | grep cinder: cinder 14315 1 0 10:12 ?00:00:00 su -s /bin/sh -c exec cinder-volume --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-volume.log cinder cinder 14316 14315 0 10:12 ?00:00:01 /usr/bin/python /usr/bin/cinder-volume --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-volume.log cinder 14336 1 0 10:12 ?00:00:00 su -s /bin/sh -c exec cinder-api --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-api.log cinder cinder 14337 14336 0 10:12 ?00:00:00 /usr/bin/python /usr/bin/cinder-api --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-api.log cinder 14358 1 0 10:12 ?00:00:00 su -s /bin/sh -c exec cinder-scheduler --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-scheduler.log cinder cinder 14359 14358 0 10:12 ?00:00:01 /usr/bin/python /usr/bin/cinder-scheduler --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-scheduler.log root 21026 6073 0 10:49 pts/200:00:00 grep --color=auto cinder # ps -ef | grep tgt root 13648 1 0 10:09 ?00:00:00 tgtd root 13650 13648 0 10:09 ?00:00:00 tgtd root 21369 6073 0 10:51 pts/200:00:00 grep --color=auto tgt # cinder.conf: [user] and [pass] omitted [DEFAULT] rootwrap_config = /etc/cinder/rootwrap.conf api_paste_confg = /etc/cinder/api-paste.ini sql_connection = mysql://[user]:[pass]@192.168.111.218/cinder iscsi_helper = tgtadm volume_name_template = volume-%s volume_group = cinder-volumes verbose = True auth_strategy = keystone state_path = /var/lib/cinder volumes_dir = /var/lib/cinder/volumes Also, in my case(devstack install), the path is '/opt/stack/data/cinder/volumes/*' and not ' /var/lib/cinder/volumes/*'. So make sure your path is right. I'm using a custom install script to setup a single install of OpenStack using the packages provided by Ubuntu 12.04. Hope this helps. Regards, Balu On Wed, Jan 2, 2013 at 3:47 PM, Leander Bessa Beernaert leande...@gmail.com wrote: # /etc/tgt/conf.d/cinder_tgt.conf nclude /var/lib/cinder/volumes/* Regards, Leander ___ 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] [OpenStack][Cinder] ISCSITargetCreateFailed: Failed to create iscsi target for volume
I've already tried restarting all cinder services and tgt, the error still remains. Thanks for the help though. Regards, Leander On Wed, Jan 2, 2013 at 11:08 AM, Balamurugan V G balamuruga...@gmail.comwrote: Try restarting your 'tgt' and other cinder services. That is all I can think of. I had similar issue and after I set the path right and restarted the services, it worked fine. Regards, Balu On Wed, Jan 2, 2013 at 4:23 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Reply is inlined below. On Wed, Jan 2, 2013 at 10:41 AM, Balamurugan V G balamuruga...@gmail.com wrote: Is that a typo in your configuration or a copy pase error: # /etc/tgt/conf.d/cinder_tgt.conf nclude /var/lib/cinder/volumes/* The 'i' is missing in 'include'. If its only a copy paste error in the mail, make sure you have the following running: That was a copy paste typo, the original file is correct. root@openstack-vm:~# ps -ef | grep cinder root 3636 1 0 06:53 ?00:00:33 /usr/bin/python /usr/local/bin/cinder-volume root 25433 1 0 06:46 ?00:00:01 /usr/bin/python /usr/local/bin/cinder-api --config-file /etc/cinder/cinder.conf root 25937 1 0 06:46 ?00:00:32 /usr/bin/python /usr/local/bin/cinder-scheduler --config-file /etc/cinder/cinder.conf root@openstack-vm:~# ps -ef | grep tgt root 31176 31174 0 06:49 ?00:00:03 tgtd root@openstack-vm:~# # ps -ef | grep cinder: cinder 14315 1 0 10:12 ?00:00:00 su -s /bin/sh -c exec cinder-volume --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-volume.log cinder cinder 14316 14315 0 10:12 ?00:00:01 /usr/bin/python /usr/bin/cinder-volume --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-volume.log cinder 14336 1 0 10:12 ?00:00:00 su -s /bin/sh -c exec cinder-api --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-api.log cinder cinder 14337 14336 0 10:12 ?00:00:00 /usr/bin/python /usr/bin/cinder-api --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-api.log cinder 14358 1 0 10:12 ?00:00:00 su -s /bin/sh -c exec cinder-scheduler --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-scheduler.log cinder cinder 14359 14358 0 10:12 ?00:00:01 /usr/bin/python /usr/bin/cinder-scheduler --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-scheduler.log root 21026 6073 0 10:49 pts/200:00:00 grep --color=auto cinder # ps -ef | grep tgt root 13648 1 0 10:09 ?00:00:00 tgtd root 13650 13648 0 10:09 ?00:00:00 tgtd root 21369 6073 0 10:51 pts/200:00:00 grep --color=auto tgt # cinder.conf: [user] and [pass] omitted [DEFAULT] rootwrap_config = /etc/cinder/rootwrap.conf api_paste_confg = /etc/cinder/api-paste.ini sql_connection = mysql://[user]:[pass]@192.168.111.218/cinder iscsi_helper = tgtadm volume_name_template = volume-%s volume_group = cinder-volumes verbose = True auth_strategy = keystone state_path = /var/lib/cinder volumes_dir = /var/lib/cinder/volumes Also, in my case(devstack install), the path is '/opt/stack/data/cinder/volumes/*' and not ' /var/lib/cinder/volumes/*'. So make sure your path is right. I'm using a custom install script to setup a single install of OpenStack using the packages provided by Ubuntu 12.04. Hope this helps. Regards, Balu On Wed, Jan 2, 2013 at 3:47 PM, Leander Bessa Beernaert leande...@gmail.com wrote: # /etc/tgt/conf.d/cinder_tgt.conf nclude /var/lib/cinder/volumes/* Regards, Leander ___ 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] [OpenStack][Cinder] ISCSITargetCreateFailed: Failed to create iscsi target for volume
With what should i replace the include /var/lib/cinder/volumes/*? The folder /var/lib/cinder/volumes/ is empty :/ On Wed, Jan 2, 2013 at 11:22 AM, Pierre FREUND pierre.fre...@gmail.comwrote: Hello, I think you should try to replace all * in tgt conf files. Replace by one include line per file instead of *. Pierre FREUND 2013/1/2 Leander Bessa Beernaert leande...@gmail.com I've already tried restarting all cinder services and tgt, the error still remains. Thanks for the help though. Regards, Leander On Wed, Jan 2, 2013 at 11:08 AM, Balamurugan V G balamuruga...@gmail.com wrote: Try restarting your 'tgt' and other cinder services. That is all I can think of. I had similar issue and after I set the path right and restarted the services, it worked fine. Regards, Balu On Wed, Jan 2, 2013 at 4:23 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Reply is inlined below. On Wed, Jan 2, 2013 at 10:41 AM, Balamurugan V G balamuruga...@gmail.com wrote: Is that a typo in your configuration or a copy pase error: # /etc/tgt/conf.d/cinder_tgt.conf nclude /var/lib/cinder/volumes/* The 'i' is missing in 'include'. If its only a copy paste error in the mail, make sure you have the following running: That was a copy paste typo, the original file is correct. root@openstack-vm:~# ps -ef | grep cinder root 3636 1 0 06:53 ?00:00:33 /usr/bin/python /usr/local/bin/cinder-volume root 25433 1 0 06:46 ?00:00:01 /usr/bin/python /usr/local/bin/cinder-api --config-file /etc/cinder/cinder.conf root 25937 1 0 06:46 ?00:00:32 /usr/bin/python /usr/local/bin/cinder-scheduler --config-file /etc/cinder/cinder.conf root@openstack-vm:~# ps -ef | grep tgt root 31176 31174 0 06:49 ?00:00:03 tgtd root@openstack-vm:~# # ps -ef | grep cinder: cinder 14315 1 0 10:12 ?00:00:00 su -s /bin/sh -c exec cinder-volume --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-volume.log cinder cinder 14316 14315 0 10:12 ?00:00:01 /usr/bin/python /usr/bin/cinder-volume --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-volume.log cinder 14336 1 0 10:12 ?00:00:00 su -s /bin/sh -c exec cinder-api --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-api.log cinder cinder 14337 14336 0 10:12 ?00:00:00 /usr/bin/python /usr/bin/cinder-api --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-api.log cinder 14358 1 0 10:12 ?00:00:00 su -s /bin/sh -c exec cinder-scheduler --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-scheduler.log cinder cinder 14359 14358 0 10:12 ?00:00:01 /usr/bin/python /usr/bin/cinder-scheduler --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-scheduler.log root 21026 6073 0 10:49 pts/200:00:00 grep --color=auto cinder # ps -ef | grep tgt root 13648 1 0 10:09 ?00:00:00 tgtd root 13650 13648 0 10:09 ?00:00:00 tgtd root 21369 6073 0 10:51 pts/200:00:00 grep --color=auto tgt # cinder.conf: [user] and [pass] omitted [DEFAULT] rootwrap_config = /etc/cinder/rootwrap.conf api_paste_confg = /etc/cinder/api-paste.ini sql_connection = mysql://[user]:[pass]@192.168.111.218/cinder iscsi_helper = tgtadm volume_name_template = volume-%s volume_group = cinder-volumes verbose = True auth_strategy = keystone state_path = /var/lib/cinder volumes_dir = /var/lib/cinder/volumes Also, in my case(devstack install), the path is '/opt/stack/data/cinder/volumes/*' and not ' /var/lib/cinder/volumes/*'. So make sure your path is right. I'm using a custom install script to setup a single install of OpenStack using the packages provided by Ubuntu 12.04. Hope this helps. Regards, Balu On Wed, Jan 2, 2013 at 3:47 PM, Leander Bessa Beernaert leande...@gmail.com wrote: # /etc/tgt/conf.d/cinder_tgt.conf nclude /var/lib/cinder/volumes/* Regards, Leander ___ 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] [OpenStack][Cinder] ISCSITargetCreateFailed: Failed to create iscsi target for volume
That did it!! Thanks! On Wed, Jan 2, 2013 at 12:13 PM, Pierre FREUND pierre.fre...@gmail.comwrote: include /var/lib/cinder/volumes/* ___ 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] [OpenStack] Upgraded from Essex to Folsom, instances lost all internet connectivity
Hello all, I've upgraded my OpenStack installation about a month ago or so. I've been recently informed that the virtual machines no longer have internet connectivity. They can be accessed through ssh and can reach each other. They can however no longer perform any outside access such as apt-get update for instance. Before the upgrade, everything was working fine, is this due to some Folsom specific feature? Regards, Leander ___ 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] [OpenStack] Nova API does not start
Hello, I have just installed the Folsom package of Nova API and am unable to get it to start. Here's the error log: 2012-11-09 14:28:40 DEBUG nova.wsgi [-] Loading app metadata from /etc/nova/api-paste.ini from (pid=25593) load_app /usr/lib/python2.7/dist-packages/nova/wsgi.py:371 2012-11-09 14:28:40 CRITICAL nova [-] module 'nova.api.metadata.handler' from '/usr/lib/python2.7/dist-packages/nova/api/metadata/handler.pyc' has no 'Versions' attribute 2012-11-09 14:28:40 TRACE nova Traceback (most recent call last): 2012-11-09 14:28:40 TRACE nova File /usr/bin/nova-api, line 50, in module 2012-11-09 14:28:40 TRACE nova server = service.WSGIService(api) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 577, in __init__ 2012-11-09 14:28:40 TRACE nova self.app = self.loader.load_app(name) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 372, in load_app 2012-11-09 14:28:40 TRACE nova return deploy.loadapp(config:%s % self.config_path, name=name) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 247, in loadapp 2012-11-09 14:28:40 TRACE nova return loadobj(APP, uri, name=name, **kw) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 272, in loadobj 2012-11-09 14:28:40 TRACE nova return context.create() 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 710, in create 2012-11-09 14:28:40 TRACE nova return self.object_type.invoke(self) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 144, in invoke 2012-11-09 14:28:40 TRACE nova **context.local_conf) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/util.py, line 56, in fix_call 2012-11-09 14:28:40 TRACE nova val = callable(*args, **kw) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/urlmap.py, line 25, in urlmap_factory 2012-11-09 14:28:40 TRACE nova app = loader.get_app(app_name, global_conf=global_conf) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 350, in get_app 2012-11-09 14:28:40 TRACE nova name=name, global_conf=global_conf).create() 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 362, in app_context 2012-11-09 14:28:40 TRACE nova APP, name=name, global_conf=global_conf) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 450, in get_context 2012-11-09 14:28:40 TRACE nova global_additions=global_additions) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 559, in _pipeline_app_context 2012-11-09 14:28:40 TRACE nova APP, pipeline[-1], global_conf) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 458, in get_context 2012-11-09 14:28:40 TRACE nova section) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 517, in _context_from_explicit 2012-11-09 14:28:40 TRACE nova value = import_string(found_expr) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 22, in import_string 2012-11-09 14:28:40 TRACE nova return pkg_resources.EntryPoint.parse(x= + s).load(False) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1994, in load 2012-11-09 14:28:40 TRACE nova raise ImportError(%r has no %r attribute % (entry,attr)) 2012-11-09 14:28:40 TRACE nova ImportError: module 'nova.api.metadata.handler' from '/usr/lib/python2.7/dist-packages/nova/api/metadata/handler.pyc' has no 'Versions' attribute 2012-11-09 14:28:40 TRACE nova A similar error has been posted on Launchpad, but it has expired [1]. Any ideas? [1] https://answers.launchpad.net/nova/+question/211675 ___ 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] [OpenStack][Glance] Error starting Glance
Hello all, I'm unable to start glance. I upgraded it from Essex to Folsom on ubuntu 12.04. It produces the following output: 2012-11-09 14:51:27 29928 DEBUG glance.common.config [-] Loading glance-api-keystone from /etc/glance/glance-api-paste.ini load_paste_app /usr/lib/python2.7/dist-packages/glance/common/config.py:185 ERROR: Unable to load glance-api-keystone from configuration file /etc/glance/glance-api-paste.ini. Got: ImportError(module 'glance.common.wsgi' from '/usr/lib/python2.7/dist-packages/glance/common/wsgi.pyc' has no 'app_factory' attribute,) The file /etc/glance/glance-api-paste.ini exists and is the same as the one used before the upgrade. I'm following the details mentioned here[1] and none of them mention this particular error. [1] http://wiki.openstack.org/ReleaseNotes/Folsom Regards, Leander ___ 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] [OpenStack][Glance] Error starting Glance
I've managed to fix the problem by replacing my old paste.ini files for glance-api and glance-registry with the ones provided with the packages. On Fri, Nov 9, 2012 at 2:55 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello all, I'm unable to start glance. I upgraded it from Essex to Folsom on ubuntu 12.04. It produces the following output: 2012-11-09 14:51:27 29928 DEBUG glance.common.config [-] Loading glance-api-keystone from /etc/glance/glance-api-paste.ini load_paste_app /usr/lib/python2.7/dist-packages/glance/common/config.py:185 ERROR: Unable to load glance-api-keystone from configuration file /etc/glance/glance-api-paste.ini. Got: ImportError(module 'glance.common.wsgi' from '/usr/lib/python2.7/dist-packages/glance/common/wsgi.pyc' has no 'app_factory' attribute,) The file /etc/glance/glance-api-paste.ini exists and is the same as the one used before the upgrade. I'm following the details mentioned here[1] and none of them mention this particular error. [1] http://wiki.openstack.org/ReleaseNotes/Folsom Regards, Leander ___ 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] [OpenStack] Nova API does not start
For anyone with the same problem, I've managed to fix my problem by updating my old api-paste.ini with the one provided with the Folsom package. Regards, Leander On Fri, Nov 9, 2012 at 2:42 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I have just installed the Folsom package of Nova API and am unable to get it to start. Here's the error log: 2012-11-09 14:28:40 DEBUG nova.wsgi [-] Loading app metadata from /etc/nova/api-paste.ini from (pid=25593) load_app /usr/lib/python2.7/dist-packages/nova/wsgi.py:371 2012-11-09 14:28:40 CRITICAL nova [-] module 'nova.api.metadata.handler' from '/usr/lib/python2.7/dist-packages/nova/api/metadata/handler.pyc' has no 'Versions' attribute 2012-11-09 14:28:40 TRACE nova Traceback (most recent call last): 2012-11-09 14:28:40 TRACE nova File /usr/bin/nova-api, line 50, in module 2012-11-09 14:28:40 TRACE nova server = service.WSGIService(api) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 577, in __init__ 2012-11-09 14:28:40 TRACE nova self.app = self.loader.load_app(name) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 372, in load_app 2012-11-09 14:28:40 TRACE nova return deploy.loadapp(config:%s % self.config_path, name=name) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 247, in loadapp 2012-11-09 14:28:40 TRACE nova return loadobj(APP, uri, name=name, **kw) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 272, in loadobj 2012-11-09 14:28:40 TRACE nova return context.create() 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 710, in create 2012-11-09 14:28:40 TRACE nova return self.object_type.invoke(self) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 144, in invoke 2012-11-09 14:28:40 TRACE nova **context.local_conf) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/util.py, line 56, in fix_call 2012-11-09 14:28:40 TRACE nova val = callable(*args, **kw) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/urlmap.py, line 25, in urlmap_factory 2012-11-09 14:28:40 TRACE nova app = loader.get_app(app_name, global_conf=global_conf) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 350, in get_app 2012-11-09 14:28:40 TRACE nova name=name, global_conf=global_conf).create() 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 362, in app_context 2012-11-09 14:28:40 TRACE nova APP, name=name, global_conf=global_conf) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 450, in get_context 2012-11-09 14:28:40 TRACE nova global_additions=global_additions) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 559, in _pipeline_app_context 2012-11-09 14:28:40 TRACE nova APP, pipeline[-1], global_conf) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 458, in get_context 2012-11-09 14:28:40 TRACE nova section) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 517, in _context_from_explicit 2012-11-09 14:28:40 TRACE nova value = import_string(found_expr) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 22, in import_string 2012-11-09 14:28:40 TRACE nova return pkg_resources.EntryPoint.parse(x= + s).load(False) 2012-11-09 14:28:40 TRACE nova File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1994, in load 2012-11-09 14:28:40 TRACE nova raise ImportError(%r has no %r attribute % (entry,attr)) 2012-11-09 14:28:40 TRACE nova ImportError: module 'nova.api.metadata.handler' from '/usr/lib/python2.7/dist-packages/nova/api/metadata/handler.pyc' has no 'Versions' attribute 2012-11-09 14:28:40 TRACE nova A similar error has been posted on Launchpad, but it has expired [1]. Any ideas? [1] https://answers.launchpad.net/nova/+question/211675 ___ 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] [OpenStack] Upgrading from Essex to Folsom
Hello all, I'm trying to upgrade my current installation of OpenStack Essex running on ubuntu 12.04 to the Folsom release. I'm following the instructions from [1] but I can't get the new packages to appear. For instance, after following the instruction, the version parameter for the command apt-cache show keystone is Version: 2012.1-0ubuntu1. Is there something missing? Regards, Leander [1] https://wiki.ubuntu.com/ServerTeam/CloudArchive ___ 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] [OpenStack][Nova] Help with Cloudpipe setup
Hello, I've been trying to set up cloud pipe for OpenStack. I'm running OpenStack Essex on Ubuntu 12.04 with the default packages. I'm following the instructions from [1,2]. When i get to the part of generating certificates to connect to the cloudpipe instance i get this error [3]. Any ideas? [1] http://docs.openstack.org/developer/nova/devref/cloudpipe.html [2] http://docs.openstack.org/essex/openstack-compute/admin/content/cloudpipe-per-project-vpns.html [3] http://paste.openstack.org/show/20735/ -- Cumprimentos / Regards, Leander ___ 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] [OpenStack][Nova] Help with Cloudpipe setup
I'd like to add that i'm unable to ping or ssh this instance from any nodes in my setup. Ping and ssh are working on normal instances. On Fri, Sep 7, 2012 at 10:28 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I've been trying to set up cloud pipe for OpenStack. I'm running OpenStack Essex on Ubuntu 12.04 with the default packages. I'm following the instructions from [1,2]. When i get to the part of generating certificates to connect to the cloudpipe instance i get this error [3]. Any ideas? [1] http://docs.openstack.org/developer/nova/devref/cloudpipe.html [2] http://docs.openstack.org/essex/openstack-compute/admin/content/cloudpipe-per-project-vpns.html [3] http://paste.openstack.org/show/20735/ -- Cumprimentos / Regards, Leander -- Cumprimentos / Regards, Leander ___ 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] [OpenStack][Nova]Problems and questions regarding network and/or routing
After fixing the routing_ip in the nova.conf file, my instances can now connect to the outside world. However, i'm still unable to connect to any of my instances through ssh or ping from the controller node. The controller node is also running a nova-network, could that be the issue? On Wed, Sep 5, 2012 at 4:36 PM, George Mihaiescu george.mihaie...@q9.comwrote: ** No, if you run in a multi-host enabled mode there is no need for ip_forward enabled on the controller node. I would check iptables on the nova-compute hosts, arp tables in the instance, outside connectivity from the hosts, etc. ** ** ** ** -- *From:* Leander Bessa Beernaert [mailto:leande...@gmail.com] *Sent:* Wednesday, September 05, 2012 11:26 AM *To:* **George Mihaiescu ** *Cc:* openstack@lists.launchpad.net *Subject:* Re: [Openstack] [OpenStack][Nova]Problems and questions regarding network and/or routing ** ** Do i also need ip_forward enabled on the controller node? (sorry about the duplicate) On Wed, Sep 5, 2012 at 4:25 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Do i also no ip_forward enabled on the controller node? ** ** On Wed, Sep 5, 2012 at 3:18 PM, Leander Bessa Beernaert leande...@gmail.com wrote: All compute nodes have /proc/sys/net/ipv4/ip_forward set to 1. So that can't be the issue :s ** ** On Wed, Sep 5, 2012 at 3:11 PM, **George Mihaiescu** george.mihaie...@q9.com wrote: Hi Leander, Make sure you have ip forward enabled on the nova-compute nodes (that now act as nova-network as well). Second, each nova-network acts as a gateway for each project and it needs an IP address, so probably this explains the “phantom” 10.0.108.4, 10.0.108.6, 10.0.108.8 and 10.0.108.4.10 addresses. George -- *From:* openstack-bounces+george.mihaiescu=q9@lists.launchpad.net[mailto: openstack-bounces+george.mihaiescu=q9@lists.launchpad.net] *On Behalf Of *Leander Bessa Beernaert *Sent:* Wednesday, September 05, 2012 9:49 AM *To:* Vishvananda Ishaya *Cc:* openstack@lists.launchpad.net *Subject:* Re: [Openstack] [OpenStack][Nova]Problems and questions regarding network and/or routing I'm having the strangest issue. I have set up a separate OpenStack cluster to test out the multi-host setup. I have one controller node and 4 compute nodes. Each compute node is running nova-network, nova-compute and nova-api-metadata. I have set up a tenant with the a multi-host network on the address range 10.0.108.0/24. * *** I launched 4 instances to fill up the compute nodes: +--+--+++ | ID | Name | Status | Networks | +--+--+++ | 2c63cc3e-7c45-4e10-8ac5-480fa60d4f32 | Test | ACTIVE | project_network=10.0.108.7 | | c48f6aae-0d97-4e69-a398-8cda929c310d | Test | ACTIVE | project_network=10.0.108.3 | | ed8f11a4-5fc0-4437-9ae2-b6725126fca7 | Test | ACTIVE | project_network=10.0.108.5 | | fe39e586-030c-4bf4-9020-7ef773567913 | Test | ACTIVE | project_network=10.0.108.9 | +--+--+++ One thing i found odd at the beginning was the fact that the instances are using only odd addresses. **The** installation is clean and no instances have been launched before, so all the addresses are available. **The** problem now is that i can only ping instances form the compute nodes. I am unable to ping any instance from the controller node. Stranger yet, is the fact that i can ping non-existent address such as 10.0.108.4,10.0.108.6,10.0.108.8 and 10.0.108.4.10. I have also no connectivity from within the instances to the outside world. Has this happend to anyone before? On Tue, Sep 4, 2012 at 11:38 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: On Sep 4, 2012, at 3:01 PM, Leander Bessa Beernaert leande...@gmail.com wrote: ** ** Question follows inlined below. On Tue, Sep 4, 2012 at 6:48 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: On Sep 4, 2012, at 8:35 AM, Leander Bessa Beernaert leande...@gmail.com wrote: ** ** Hello all, I've had a few reports from users testing out the sample installation of OpenStack i setup. **The** reports were all related to problems with inter-vm network speeds and connection timeouts as well as the inability to connect to the outside word from within the VM (e.g.: ping www.google.com). I'm not sure if i setup something wrong, so i have a few questions. **The** current installation
[Openstack] [OpenStack][Nova] Cloudpipe creation error
Hello all, I'm trying to setup a cloudpipe for a project. I'm running OpenStack Essex on Ubuntu 12.04. I ran the command nova cloudpipe create [project_id] and i found this in the nova-api log: 2012-09-06 12:19:46 ERROR nova.api.openstack.wsgi [req-6f5432b5-026c-413f-bb78-558cabe67af5 project-vpn 4ebf76425efa4d01bc54a182185444a6] Exception handling resource: 'NoneType' object has no attribute '__getitem__' 2012-09-06 12:19:46 TRACE nova.api.openstack.wsgi Traceback (most recent call last): 2012-09-06 12:19:46 TRACE nova.api.openstack.wsgi File /usr/lib/python2.7/dist-packages/nova/api/openstack/wsgi.py, line 851, in _process_stack 2012-09-06 12:19:46 TRACE nova.api.openstack.wsgi action_result = self.dispatch(meth, request, action_args) 2012-09-06 12:19:46 TRACE nova.api.openstack.wsgi File /usr/lib/python2.7/dist-packages/nova/api/openstack/wsgi.py, line 926, in dispatch 2012-09-06 12:19:46 TRACE nova.api.openstack.wsgi return method(req=request, **action_args) 2012-09-06 12:19:46 TRACE nova.api.openstack.wsgi File /usr/lib/python2.7/dist-packages/nova/api/openstack/compute/contrib/cloudpipe.py, line 144, in create 2012-09-06 12:19:46 TRACE nova.api.openstack.wsgi instance = result[0][0] 2012-09-06 12:19:46 TRACE nova.api.openstack.wsgi TypeError: 'NoneType' object has no attribute '__getitem__' 2012-09-06 12:19:46 TRACE nova.api.openstack.wsgi 2012-09-06 12:19:46 INFO nova.api.openstack.wsgi [req-6f5432b5-026c-413f-bb78-558cabe67af5 project-vpn 4ebf76425efa4d01bc54a182185444a6] http://10.0.107.2:8774/v2/4ebf76425efa4d01bc54a182185444a6/os-cloudpipereturned with HTTP 400 I have these flags enables in my nova.conf file: vpn_image_id=859a2b4f-80e7-4fc2-a3e9-3c825811ac11 use_project_ca=True cnt_vpn_clients=5 Any idea what might be happening? -- Cumprimentos / Regards, Leander ___ 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] [OpenStack][Nova]Problems and questions regarding network and/or routing
I'm having the strangest issue. I have set up a separate OpenStack cluster to test out the multi-host setup. I have one controller node and 4 compute nodes. Each compute node is running nova-network, nova-compute and nova-api-metadata. I have set up a tenant with the a multi-host network on the address range 10.0.108.0/24. I launched 4 instances to fill up the compute nodes: +--+--+++ | ID | Name | Status | Networks | +--+--+++ | 2c63cc3e-7c45-4e10-8ac5-480fa60d4f32 | Test | ACTIVE | project_network=10.0.108.7 | | c48f6aae-0d97-4e69-a398-8cda929c310d | Test | ACTIVE | project_network=10.0.108.3 | | ed8f11a4-5fc0-4437-9ae2-b6725126fca7 | Test | ACTIVE | project_network=10.0.108.5 | | fe39e586-030c-4bf4-9020-7ef773567913 | Test | ACTIVE | project_network=10.0.108.9 | +--+--+++ One thing i found odd at the beginning was the fact that the instances are using only odd addresses. The installation is clean and no instances have been launched before, so all the addresses are available. The problem now is that i can only ping instances form the compute nodes. I am unable to ping any instance from the controller node. Stranger yet, is the fact that i can ping non-existent address such as 10.0.108.4,10.0.108.6,10.0.108.8 and 10.0.108.4.10. I have also no connectivity from within the instances to the outside world. Has this happend to anyone before? On Tue, Sep 4, 2012 at 11:38 PM, Vishvananda Ishaya vishvana...@gmail.comwrote: On Sep 4, 2012, at 3:01 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Question follows inlined below. On Tue, Sep 4, 2012 at 6:48 PM, Vishvananda Ishaya vishvana...@gmail.comwrote: On Sep 4, 2012, at 8:35 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello all, I've had a few reports from users testing out the sample installation of OpenStack i setup. The reports were all related to problems with inter-vm network speeds and connection timeouts as well as the inability to connect to the outside word from within the VM (e.g.: ping www.google.com). I'm not sure if i setup something wrong, so i have a few questions. The current installation of OpenStack is running with 1 controller node, and 8 compute nodes. Each node is running Ubuntu 12.04 and Essex with the default packages. I'm using the VLAN network manager. There is one peculiarity to this setup. Since each physical hosts only has 1 network interface, i came up with the following configuration: - For inter-node communications i set up a VLAN with the ID 107 - Each tentant has it's private network on a separate VLAN. Currently there are two tenant, one on VLAN 109 (network: 10.0.9.0/24) and another on VLAN 110 (network: 10.0.9.0/24). I'm not a network expert, so please bear with me if i make any outrages statements. 1) When communicating on the private network, the packets are not routed through the controller right? That only happens when the VM needs to contact an external source (e.g.: google), correct? This report originated from users from VLAN 109. They are using network intensive applications which send a lot of data between each of the instances. They reported various time-out and connection drops as well as slow transfer speeds. I'm no network expert, but could this be related to the routing, VLANs or is it a hardware issue? There are a lot of things that could cause this. You would need to do some extensive debugging to find the source of this. Any ideas where i can start looking? Also, communications between two VMs on different compute nodes from the same tenant do not need to be routed through the controller node right? in non-multi_host mode I believe it will go through the controller. Vish -- Cumprimentos / Regards, Leander ___ 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] [OpenStack][Nova]Problems and questions regarding network and/or routing
All compute nodes have /proc/sys/net/ipv4/ip_forward set to 1. So that can't be the issue :s On Wed, Sep 5, 2012 at 3:11 PM, George Mihaiescu george.mihaie...@q9.comwrote: ** Hi Leander, ** ** Make sure you have ip forward enabled on the nova-compute nodes (that now act as nova-network as well). Second, each nova-network acts as a gateway for each project and it needs an IP address, so probably this explains the “phantom” 10.0.108.4, 10.0.108.6, 10.0.108.8 and 10.0.108.4.10 addresses. ** ** George ** ** -- *From:* openstack-bounces+george.mihaiescu=q9@lists.launchpad.net[mailto: openstack-bounces+george.mihaiescu=q9@lists.launchpad.net] *On Behalf Of *Leander Bessa Beernaert *Sent:* Wednesday, September 05, 2012 9:49 AM *To:* Vishvananda Ishaya *Cc:* openstack@lists.launchpad.net *Subject:* Re: [Openstack] [OpenStack][Nova]Problems and questions regarding network and/or routing ** ** I'm having the strangest issue. I have set up a separate OpenStack cluster to test out the multi-host setup. ** ** I have one controller node and 4 compute nodes. Each compute node is running nova-network, nova-compute and nova-api-metadata. I have set up a tenant with the a multi-host network on the address range 10.0.108.0/24. * *** ** ** I launched 4 instances to fill up the compute nodes: ** ** +--+--+++ | ID | Name | Status | Networks | +--+--+++ | 2c63cc3e-7c45-4e10-8ac5-480fa60d4f32 | Test | ACTIVE | project_network=10.0.108.7 | | c48f6aae-0d97-4e69-a398-8cda929c310d | Test | ACTIVE | project_network=10.0.108.3 | | ed8f11a4-5fc0-4437-9ae2-b6725126fca7 | Test | ACTIVE | project_network=10.0.108.5 | | fe39e586-030c-4bf4-9020-7ef773567913 | Test | ACTIVE | project_network=10.0.108.9 | +--+--+++ ** ** One thing i found odd at the beginning was the fact that the instances are using only odd addresses. **The** installation is clean and no instances have been launched before, so all the addresses are available. ** ** **The** problem now is that i can only ping instances form the compute nodes. I am unable to ping any instance from the controller node. Stranger yet, is the fact that i can ping non-existent address such as 10.0.108.4,10.0.108.6,10.0.108.8 and 10.0.108.4.10. I have also no connectivity from within the instances to the outside world. ** ** Has this happend to anyone before? ** ** ** ** On Tue, Sep 4, 2012 at 11:38 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: ** ** On Sep 4, 2012, at 3:01 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Question follows inlined below. On Tue, Sep 4, 2012 at 6:48 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: ** ** On Sep 4, 2012, at 8:35 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello all, ** ** I've had a few reports from users testing out the sample installation of OpenStack i setup. **The** reports were all related to problems with inter-vm network speeds and connection timeouts as well as the inability to connect to the outside word from within the VM (e.g.: ping www.google.com). I'm not sure if i setup something wrong, so i have a few questions. ** ** **The** current installation of OpenStack is running with 1 controller node, and 8 compute nodes. Each node is running Ubuntu 12.04 and Essex with the default packages. I'm using the VLAN network manager. **The**re is one peculiarity to this setup. Since each physical hosts only has 1 network interface, i came up with the following configuration: - For inter-node communications i set up a VLAN with the ID 107 - Each tentant has it's private network on a separate VLAN. Currently there are two tenant, one on VLAN 109 (network: 10.0.9.0/24) and another on VLAN 110 (network: 10.0.9.0/24). ** ** I'm not a network expert, so please bear with me if i make any outrages statements. ** ** 1) When communicating on the private network, the packets are not routed through the controller right? That only happens when the VM needs to contact an external source (e.g.: google), correct? This report originated from users from VLAN 109. **The**y are using network intensive applications which send a lot of data between each of the instances. **The **y reported various time-out and connection drops as well as slow transfer speeds. I'm no network expert, but could this be related to the routing, VLANs or is it a hardware issue? ** ** **The**re are a lot of things that could cause this. You would
Re: [Openstack] [OpenStack][Nova]Problems and questions regarding network and/or routing
Do i also no ip_forward enabled on the controller node? On Wed, Sep 5, 2012 at 3:18 PM, Leander Bessa Beernaert leande...@gmail.com wrote: All compute nodes have /proc/sys/net/ipv4/ip_forward set to 1. So that can't be the issue :s On Wed, Sep 5, 2012 at 3:11 PM, George Mihaiescu george.mihaie...@q9.comwrote: ** Hi Leander, ** ** Make sure you have ip forward enabled on the nova-compute nodes (that now act as nova-network as well). Second, each nova-network acts as a gateway for each project and it needs an IP address, so probably this explains the “phantom” 10.0.108.4, 10.0.108.6, 10.0.108.8 and 10.0.108.4.10 addresses. ** ** George ** ** -- *From:* openstack-bounces+george.mihaiescu=q9@lists.launchpad.net[mailto: openstack-bounces+george.mihaiescu=q9@lists.launchpad.net] *On Behalf Of *Leander Bessa Beernaert *Sent:* Wednesday, September 05, 2012 9:49 AM *To:* Vishvananda Ishaya *Cc:* openstack@lists.launchpad.net *Subject:* Re: [Openstack] [OpenStack][Nova]Problems and questions regarding network and/or routing ** ** I'm having the strangest issue. I have set up a separate OpenStack cluster to test out the multi-host setup. ** ** I have one controller node and 4 compute nodes. Each compute node is running nova-network, nova-compute and nova-api-metadata. I have set up a tenant with the a multi-host network on the address range 10.0.108.0/24. ** ** I launched 4 instances to fill up the compute nodes: ** ** +--+--+++ | ID | Name | Status | Networks | +--+--+++ | 2c63cc3e-7c45-4e10-8ac5-480fa60d4f32 | Test | ACTIVE | project_network=10.0.108.7 | | c48f6aae-0d97-4e69-a398-8cda929c310d | Test | ACTIVE | project_network=10.0.108.3 | | ed8f11a4-5fc0-4437-9ae2-b6725126fca7 | Test | ACTIVE | project_network=10.0.108.5 | | fe39e586-030c-4bf4-9020-7ef773567913 | Test | ACTIVE | project_network=10.0.108.9 | +--+--+++ ** ** One thing i found odd at the beginning was the fact that the instances are using only odd addresses. **The** installation is clean and no instances have been launched before, so all the addresses are available. ** ** **The** problem now is that i can only ping instances form the compute nodes. I am unable to ping any instance from the controller node. Stranger yet, is the fact that i can ping non-existent address such as 10.0.108.4,10.0.108.6,10.0.108.8 and 10.0.108.4.10. I have also no connectivity from within the instances to the outside world. ** ** Has this happend to anyone before? ** ** ** ** On Tue, Sep 4, 2012 at 11:38 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: ** ** On Sep 4, 2012, at 3:01 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Question follows inlined below. On Tue, Sep 4, 2012 at 6:48 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: ** ** On Sep 4, 2012, at 8:35 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello all, ** ** I've had a few reports from users testing out the sample installation of OpenStack i setup. **The** reports were all related to problems with inter-vm network speeds and connection timeouts as well as the inability to connect to the outside word from within the VM (e.g.: ping www.google.com). I'm not sure if i setup something wrong, so i have a few questions. ** ** **The** current installation of OpenStack is running with 1 controller node, and 8 compute nodes. Each node is running Ubuntu 12.04 and Essex with the default packages. I'm using the VLAN network manager. **The**re is one peculiarity to this setup. Since each physical hosts only has 1 network interface, i came up with the following configuration: - For inter-node communications i set up a VLAN with the ID 107 - Each tentant has it's private network on a separate VLAN. Currently there are two tenant, one on VLAN 109 (network: 10.0.9.0/24) and another on VLAN 110 (network: 10.0.9.0/24). ** ** I'm not a network expert, so please bear with me if i make any outrages statements. ** ** 1) When communicating on the private network, the packets are not routed through the controller right? That only happens when the VM needs to contact an external source (e.g.: google), correct? This report originated from users from VLAN 109. **The**y are using network intensive applications which send a lot of data between each of the instances. ** The**y reported various time-out and connection drops as well as slow transfer speeds. I'm no network expert, but could
Re: [Openstack] Live Migration with libvirtError
Hello,
I'm no expert on the subject, but i think you should just use mount -t nfs
172.18.32.7:/ /var/lib/nova/instances instead of mount -t nfs 172.18.32.7:
/var/lib/nova/instances /var/lib/nova/instances. Also from the stack trace
it seems your libvirtd is not running.
On Thu, Aug 9, 2012 at 7:55 AM, 王鹏 breakwin...@gmail.com wrote:
HI everyone,
when I test live migration use NFS ,that's my sitting according to
http://docs.openstack.org/essex/openstack-compute/admin/content/configuring-live-migrations.html
1.add this line /var/lib/nova/instances *(rw,sync,fsid=0,no_root_squash)
in /etc/exports
2.mount -t nfs 172.18.32.7:/var/lib/nova/instances
/var/lib/nova/instances at compute
and change some setting in libvirt.conf and libvird-bin.conf add a option
-l
3.restart service
then I create instance in compute node ,find error
that's my nova-compute.log as follow:
2012-08-09 13:13:03 ERROR nova.manager [-] Error during
ComputeManager.update_available_resource: Failed to connect socket to
'/var/run/libvirt/libvirt-sock': No such file or directory
2012-08-09 13:13:03 TRACE nova.manager Traceback (most recent call last):
2012-08-09 13:13:03 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/manager.py, line 155, in
periodic_tasks
2012-08-09 13:13:03 TRACE nova.manager task(self, context)
2012-08-09 13:13:03 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2409, in
update_available_resource
2012-08-09 13:13:03 TRACE nova.manager
self.driver.update_available_resource(context, self.host)
2012-08-09 13:13:03 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line
1936, in update_available_resource
2012-08-09 13:13:03 TRACE nova.manager 'vcpus_used': self.get_vcpu_used(),
2012-08-09 13:13:03 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line
1742, in get_vcpu_used
2012-08-09 13:13:03 TRACE nova.manager for dom_id in
self._conn.listDomainsID():
2012-08-09 13:13:03 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line
298, in _get_connection
2012-08-09 13:13:03 TRACE nova.manager self.read_only)
2012-08-09 13:13:03 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line
341, in _connect
2012-08-09 13:13:03 TRACE nova.manager return libvirt.openAuth(uri, auth,
0)
2012-08-09 13:13:03 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/libvirt.py, line 102, in openAuth
2012-08-09 13:13:03 TRACE nova.manager if ret is None:raise
libvirtError('virConnectOpenAuth() failed')
2012-08-09 13:13:03 TRACE nova.manager libvirtError: Failed to connect
socket to '/var/run/libvirt/libvirt-sock': No such file or directory
2012-08-09 13:13:03 TRACE nova.manager
what's /var/run/libvirt/libvirt-sock'?
why this error?
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
Cumprimentos / Regards,
Leander
___
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] [OpenStack][Nova] Question regarding multiple network interfaces
So i have set up a small proof of concept, one controller node and two compute nodes. Since the switches do not support VLAN i'm using flat dhcp. Each machine has two network interfaces. Eth0 is connected to the public switch and eth1 to the private switch. The private switch has no access to the internet. Both compute nodes have the value of cat /proc/sys/net/ipv4/ip_forward set to 1. However, i still can't make an instance connect to the outside. Any thoughts? On Tue, Aug 7, 2012 at 11:32 PM, Sébastien Han han.sebast...@gmail.comwrote: It's part of the operating system # echo 1 /proc/sys/net/ipv4/ip_forward Then edit your /etc/sysctl.conf and uncomment net.ipv4.ip_forward=1 to make this persistent after reboot. Finally run -- # sysctl -p That's all, cheers! On Tue, Aug 7, 2012 at 11:50 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Is there a flag in the nova.conf file or is this something that needs to be done on the operating system? On Tue, Aug 7, 2012 at 8:26 PM, Sébastien Han han.sebast...@gmail.com wrote: Hi, If eth0 is connected to the public switch and if eth1 is connected to the private switch you can enable the ipv4 forwarding on the compute node. Thanks to this the VMs will have access to the outside world and the packet will be routed from eth1 to eth0 :). Cheers! On Tue, Aug 7, 2012 at 5:18 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I have a question regarding the use of two network interfaces. According to the official documentation, one of the interfaces is used for public access and the other for internal access (inter-vm communication). What i'd like to know is how does an instance connect to the outside world (internet access)? Is it done through the switch connected to the private interface or the public interface? -- Cumprimentos / Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Cumprimentos / Regards, Leander -- Cumprimentos / Regards, Leander ___ 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] [OpenStack][Nova] Question regarding multiple network interfaces
Hello, I have a question regarding the use of two network interfaces. According to the official documentation, one of the interfaces is used for public access and the other for internal access (inter-vm communication). What i'd like to know is how does an instance connect to the outside world (internet access)? Is it done through the switch connected to the private interface or the public interface? -- Cumprimentos / Regards, Leander ___ 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] [OpenStack][Nova] Question regarding multiple network interfaces
Is there a flag in the nova.conf file or is this something that needs to be done on the operating system? On Tue, Aug 7, 2012 at 8:26 PM, Sébastien Han han.sebast...@gmail.comwrote: Hi, If eth0 is connected to the public switch and if eth1 is connected to the private switch you can enable the ipv4 forwarding on the compute node. Thanks to this the VMs will have access to the outside world and the packet will be routed from eth1 to eth0 :). Cheers! On Tue, Aug 7, 2012 at 5:18 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I have a question regarding the use of two network interfaces. According to the official documentation, one of the interfaces is used for public access and the other for internal access (inter-vm communication). What i'd like to know is how does an instance connect to the outside world (internet access)? Is it done through the switch connected to the private interface or the public interface? -- Cumprimentos / Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Cumprimentos / Regards, Leander ___ 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] [OpenStack][Nova] Live Migration Error
Well i've checked the libvirt logs on both nodes and i found these two
lines:
2012-07-09 13:58:27.179+: 10227: warning : qemuDomainObjTaint:1134 :
Domain id=2 name='instance-0002'
uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges
2012-07-09 13:58:27.736+: 10226: error : qemuMonitorIORead:513 :
Unable to read from monitor: Connection reset by peer
The log is alos filled with the message below, it gets repeated over and
over and over.
2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 : Cannot
find 'pm-is-supported' in path: No such file or directory
2012-07-10 09:26:02.244+: 10229: warning : qemuCapsInit:856 : Failed
to get host power management capabilities
On Tue, Jul 10, 2012 at 8:16 AM, Razique Mahroua
razique.mahr...@gmail.comwrote:
Hi Leander,
try to check libvirtd.log files,
is the instance still running on the first node while you are lauching the
migration process ?
Razique
*Nuage Co - Razique Mahroua** *
razique.mahr...@gmail.com
Le 9 juil. 2012 à 16:09, Leander Bessa Beernaert a écrit :
Ok, so i've updated to the test packages from
The migration still fails, but i see no errors in the logs. I'm trying to
migrate a VM with the m1.tiny flavor from one machine to another. Their
hardware are identical and they have more than enough resources to support
the m1.tiny flavor:
cloud35 (total) 43867 186
cloud35 (used_now) 0 312 5
cloud35 (used_max) 0 0 0
These are the logs from the origin compute node:
http://paste.openstack.org/show/19319/ and the destination compute
node: http://paste.openstack.org/show/19318/ . The scheduler's log has no
visible errors or stack traces.
I'm still using nfsv4.
Any ideas?
On Fri, Jul 6, 2012 at 7:57 PM, Leander Bessa Beernaert
leande...@gmail.com wrote:
Thanks for the tip, it's a better than nothing :)
Regards,
Leander
On Fri, Jul 6, 2012 at 6:32 PM, Mandar Vaze / मंदार वझे
mandarv...@gmail.com wrote:
Not sure if you are able to debug this, but a while ago there was a bug
where instance.id was passed where instance.uuid was expected. This
used to cause some problem.
It looks like you are using distribution package rather than devstack
installation, so it is likely that the issue is now fixed. Can you try
latest packages (and/or try devstack if you can)
I wish I could help more.
-Mandar
On Fri, Jul 6, 2012 at 3:26 PM, Leander Bessa Beernaert
leande...@gmail.com wrote:
Hello,
I've recently setup a system to test out the live migration feature. So
far i've been able to launch the instances with the shared nfs folder.
However, when i run the live-migration command i encounter this error in
the destination compute node:
2012-07-05 09:33:48 ERROR nova.manager [-] Error during
ComputeManager.update_available_resource: Domain not found: no domain with
matching id 2
2012-07-05 09:33:48 TRACE nova.manager Traceback (most recent call
last):
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/manager.py, line 155, in
periodic_tasks
2012-07-05 09:33:48 TRACE nova.manager task(self, context)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2409, in
update_available_resource
2012-07-05 09:33:48 TRACE nova.manager
self.driver.update_available_resource(context, self.host)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line
1936, in update_available_resource
2012-07-05 09:33:48 TRACE nova.manager 'vcpus_used':
self.get_vcpu_used(),
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line
1743, in get_vcpu_used
2012-07-05 09:33:48 TRACE nova.manager dom =
self._conn.lookupByID(dom_id)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/libvirt.py, line 2363, in lookupByID
2012-07-05 09:33:48 TRACE nova.manager if ret is None:raise
libvirtError('virDomainLookupByID() failed', conn=self)
2012-07-05 09:33:48 TRACE nova.manager libvirtError: Domain not found:
no domain with matching id 2
Any ideas on how to solve this?
Regards,
Leander
___
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
NUAGECO-LOGO-Fblan_petit.jpg___
Mailing list: https://launchpad.net/~openstack
Post
Re: [Openstack] [OpenStack][Nova] Live Migration Error
If i don't run libvirt with root, it can't write to the shared folder. It's the only way i've been able to get this to work. :S Below follows the configuration of one of the compute nodes. 10.0.1.1 is the controller and 10.0.1.2 is the compute node. novncproxy_base_url=http://10.0.1.1:6080/vnc_auto.html xvpvncproxy_base_url=http://10.0.1.1:6081/console vncserver_proxyclient_address=10.0.1.2 vncserver_listen=10.0.1.2 On Tue, Jul 10, 2012 at 10:49 AM, Sébastien Han han.sebast...@gmail.comwrote: I forgot to ask, did you enable the vnc console? If so, with which parameters? On Tue, Jul 10, 2012 at 11:48 AM, Sébastien Han han.sebast...@gmail.comwrote: Hi! Usually you get: 2012-07-09 13:58:27.179+: 10227: warning : qemuDomainObjTaint:1134 : Domain id=2 name='instance-0002' uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges when you change permission in libvirt (root I presumed) which is not necessary. 2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 : Cannot find 'pm-is-supported' in path: No such file or directory This error is harmless and can be easily solved by installing the following package: sudo apt-get install pm-utils -y Do you have something in the nova-scheduler logs? Cheers! On Tue, Jul 10, 2012 at 11:29 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Well i've checked the libvirt logs on both nodes and i found these two lines: 2012-07-09 13:58:27.179+: 10227: warning : qemuDomainObjTaint:1134 : Domain id=2 name='instance-0002' uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges 2012-07-09 13:58:27.736+: 10226: error : qemuMonitorIORead:513 : Unable to read from monitor: Connection reset by peer The log is alos filled with the message below, it gets repeated over and over and over. 2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 : Cannot find 'pm-is-supported' in path: No such file or directory 2012-07-10 09:26:02.244+: 10229: warning : qemuCapsInit:856 : Failed to get host power management capabilities On Tue, Jul 10, 2012 at 8:16 AM, Razique Mahroua razique.mahr...@gmail.com wrote: Hi Leander, try to check libvirtd.log files, is the instance still running on the first node while you are lauching the migration process ? Razique *Nuage Co - Razique Mahroua** * razique.mahr...@gmail.com Le 9 juil. 2012 à 16:09, Leander Bessa Beernaert a écrit : Ok, so i've updated to the test packages from The migration still fails, but i see no errors in the logs. I'm trying to migrate a VM with the m1.tiny flavor from one machine to another. Their hardware are identical and they have more than enough resources to support the m1.tiny flavor: cloud35 (total) 43867 186 cloud35 (used_now) 0 312 5 cloud35 (used_max) 0 0 0 These are the logs from the origin compute node: http://paste.openstack.org/show/19319/ and the destination compute node: http://paste.openstack.org/show/19318/ . The scheduler's log has no visible errors or stack traces. I'm still using nfsv4. Any ideas? On Fri, Jul 6, 2012 at 7:57 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Thanks for the tip, it's a better than nothing :) Regards, Leander On Fri, Jul 6, 2012 at 6:32 PM, Mandar Vaze / मंदार वझे mandarv...@gmail.com wrote: Not sure if you are able to debug this, but a while ago there was a bug where instance.id was passed where instance.uuid was expected. This used to cause some problem. It looks like you are using distribution package rather than devstack installation, so it is likely that the issue is now fixed. Can you try latest packages (and/or try devstack if you can) I wish I could help more. -Mandar On Fri, Jul 6, 2012 at 3:26 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I've recently setup a system to test out the live migration feature. So far i've been able to launch the instances with the shared nfs folder. However, when i run the live-migration command i encounter this error in the destination compute node: 2012-07-05 09:33:48 ERROR nova.manager [-] Error during ComputeManager.update_available_resource: Domain not found: no domain with matching id 2 2012-07-05 09:33:48 TRACE nova.manager Traceback (most recent call last): 2012-07-05 09:33:48 TRACE nova.manager File /usr/lib/python2.7/dist-packages/nova/manager.py, line 155, in periodic_tasks 2012-07-05 09:33:48 TRACE nova.manager task(self, context) 2012-07-05 09:33:48 TRACE nova.manager File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2409, in update_available_resource 2012-07-05 09:33:48 TRACE nova.manager self.driver.update_available_resource(context, self.host) 2012-07-05 09:33:48 TRACE nova.manager File /usr/lib/python2.7/dist-packages/nova/virt
Re: [Openstack] [OpenStack][Nova] Live Migration Error
That did! Thanks :) Do you by change have any pointer on getting the live-migration to work without running libvirt under root? On Tue, Jul 10, 2012 at 10:55 AM, Sébastien Han han.sebast...@gmail.comwrote: Change the vncserver_listen to 0.0.0.0 and re-try the live-migration, you should get better results :) On Tue, Jul 10, 2012 at 11:52 AM, Leander Bessa Beernaert leande...@gmail.com wrote: If i don't run libvirt with root, it can't write to the shared folder. It's the only way i've been able to get this to work. :S Below follows the configuration of one of the compute nodes. 10.0.1.1 is the controller and 10.0.1.2 is the compute node. novncproxy_base_url=http://10.0.1.1:6080/vnc_auto.html xvpvncproxy_base_url=http://10.0.1.1:6081/console vncserver_proxyclient_address=10.0.1.2 vncserver_listen=10.0.1.2 On Tue, Jul 10, 2012 at 10:49 AM, Sébastien Han han.sebast...@gmail.comwrote: I forgot to ask, did you enable the vnc console? If so, with which parameters? On Tue, Jul 10, 2012 at 11:48 AM, Sébastien Han han.sebast...@gmail.com wrote: Hi! Usually you get: 2012-07-09 13:58:27.179+: 10227: warning : qemuDomainObjTaint:1134 : Domain id=2 name='instance-0002' uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges when you change permission in libvirt (root I presumed) which is not necessary. 2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 : Cannot find 'pm-is-supported' in path: No such file or directory This error is harmless and can be easily solved by installing the following package: sudo apt-get install pm-utils -y Do you have something in the nova-scheduler logs? Cheers! On Tue, Jul 10, 2012 at 11:29 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Well i've checked the libvirt logs on both nodes and i found these two lines: 2012-07-09 13:58:27.179+: 10227: warning : qemuDomainObjTaint:1134 : Domain id=2 name='instance-0002' uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges 2012-07-09 13:58:27.736+: 10226: error : qemuMonitorIORead:513 : Unable to read from monitor: Connection reset by peer The log is alos filled with the message below, it gets repeated over and over and over. 2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 : Cannot find 'pm-is-supported' in path: No such file or directory 2012-07-10 09:26:02.244+: 10229: warning : qemuCapsInit:856 : Failed to get host power management capabilities On Tue, Jul 10, 2012 at 8:16 AM, Razique Mahroua razique.mahr...@gmail.com wrote: Hi Leander, try to check libvirtd.log files, is the instance still running on the first node while you are lauching the migration process ? Razique *Nuage Co - Razique Mahroua** * razique.mahr...@gmail.com Le 9 juil. 2012 à 16:09, Leander Bessa Beernaert a écrit : Ok, so i've updated to the test packages from The migration still fails, but i see no errors in the logs. I'm trying to migrate a VM with the m1.tiny flavor from one machine to another. Their hardware are identical and they have more than enough resources to support the m1.tiny flavor: cloud35 (total) 43867 186 cloud35 (used_now) 0 312 5 cloud35 (used_max) 0 0 0 These are the logs from the origin compute node: http://paste.openstack.org/show/19319/ and the destination compute node: http://paste.openstack.org/show/19318/ . The scheduler's log has no visible errors or stack traces. I'm still using nfsv4. Any ideas? On Fri, Jul 6, 2012 at 7:57 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Thanks for the tip, it's a better than nothing :) Regards, Leander On Fri, Jul 6, 2012 at 6:32 PM, Mandar Vaze / मंदार वझे mandarv...@gmail.com wrote: Not sure if you are able to debug this, but a while ago there was a bug where instance.id was passed where instance.uuid was expected. This used to cause some problem. It looks like you are using distribution package rather than devstack installation, so it is likely that the issue is now fixed. Can you try latest packages (and/or try devstack if you can) I wish I could help more. -Mandar On Fri, Jul 6, 2012 at 3:26 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I've recently setup a system to test out the live migration feature. So far i've been able to launch the instances with the shared nfs folder. However, when i run the live-migration command i encounter this error in the destination compute node: 2012-07-05 09:33:48 ERROR nova.manager [-] Error during ComputeManager.update_available_resource: Domain not found: no domain with matching id 2 2012-07-05 09:33:48 TRACE nova.manager Traceback (most recent call last): 2012-07-05 09:33:48 TRACE nova.manager File /usr/lib/python2.7/dist-packages/nova/manager.py, line 155
Re: [Openstack] [OpenStack][Nova] Live Migration Error
Is GlusterFS be more viable for a production environment? On Tue, Jul 10, 2012 at 11:17 AM, Sébastien Han han.sebast...@gmail.comwrote: Great! The last time I ran the live-migration, it was with GlusterFS and CephFS and I didn't changed any permissions in libvirt. I did the live-migration with NFS once but it was in Diablo (horrible), I don't really remember my setup. Maybe you should consider to try GlusterFS. On Tue, Jul 10, 2012 at 12:07 PM, Leander Bessa Beernaert leande...@gmail.com wrote: That did! Thanks :) Do you by change have any pointer on getting the live-migration to work without running libvirt under root? On Tue, Jul 10, 2012 at 10:55 AM, Sébastien Han han.sebast...@gmail.comwrote: Change the vncserver_listen to 0.0.0.0 and re-try the live-migration, you should get better results :) On Tue, Jul 10, 2012 at 11:52 AM, Leander Bessa Beernaert leande...@gmail.com wrote: If i don't run libvirt with root, it can't write to the shared folder. It's the only way i've been able to get this to work. :S Below follows the configuration of one of the compute nodes. 10.0.1.1 is the controller and 10.0.1.2 is the compute node. novncproxy_base_url=http://10.0.1.1:6080/vnc_auto.html xvpvncproxy_base_url=http://10.0.1.1:6081/console vncserver_proxyclient_address=10.0.1.2 vncserver_listen=10.0.1.2 On Tue, Jul 10, 2012 at 10:49 AM, Sébastien Han han.sebast...@gmail.com wrote: I forgot to ask, did you enable the vnc console? If so, with which parameters? On Tue, Jul 10, 2012 at 11:48 AM, Sébastien Han han.sebast...@gmail.com wrote: Hi! Usually you get: 2012-07-09 13:58:27.179+: 10227: warning : qemuDomainObjTaint:1134 : Domain id=2 name='instance-0002' uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges when you change permission in libvirt (root I presumed) which is not necessary. 2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 : Cannot find 'pm-is-supported' in path: No such file or directory This error is harmless and can be easily solved by installing the following package: sudo apt-get install pm-utils -y Do you have something in the nova-scheduler logs? Cheers! On Tue, Jul 10, 2012 at 11:29 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Well i've checked the libvirt logs on both nodes and i found these two lines: 2012-07-09 13:58:27.179+: 10227: warning : qemuDomainObjTaint:1134 : Domain id=2 name='instance-0002' uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges 2012-07-09 13:58:27.736+: 10226: error : qemuMonitorIORead:513 : Unable to read from monitor: Connection reset by peer The log is alos filled with the message below, it gets repeated over and over and over. 2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 : Cannot find 'pm-is-supported' in path: No such file or directory 2012-07-10 09:26:02.244+: 10229: warning : qemuCapsInit:856 : Failed to get host power management capabilities On Tue, Jul 10, 2012 at 8:16 AM, Razique Mahroua razique.mahr...@gmail.com wrote: Hi Leander, try to check libvirtd.log files, is the instance still running on the first node while you are lauching the migration process ? Razique *Nuage Co - Razique Mahroua** * razique.mahr...@gmail.com Le 9 juil. 2012 à 16:09, Leander Bessa Beernaert a écrit : Ok, so i've updated to the test packages from The migration still fails, but i see no errors in the logs. I'm trying to migrate a VM with the m1.tiny flavor from one machine to another. Their hardware are identical and they have more than enough resources to support the m1.tiny flavor: cloud35 (total) 43867 186 cloud35 (used_now) 0 312 5 cloud35 (used_max) 0 0 0 These are the logs from the origin compute node: http://paste.openstack.org/show/19319/ and the destination compute node: http://paste.openstack.org/show/19318/ . The scheduler's log has no visible errors or stack traces. I'm still using nfsv4. Any ideas? On Fri, Jul 6, 2012 at 7:57 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Thanks for the tip, it's a better than nothing :) Regards, Leander On Fri, Jul 6, 2012 at 6:32 PM, Mandar Vaze / मंदार वझे mandarv...@gmail.com wrote: Not sure if you are able to debug this, but a while ago there was a bug where instance.id was passed where instance.uuid was expected. This used to cause some problem. It looks like you are using distribution package rather than devstack installation, so it is likely that the issue is now fixed. Can you try latest packages (and/or try devstack if you can) I wish I could help more. -Mandar On Fri, Jul 6, 2012 at 3:26 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I've recently setup a system to test out the live migration
Re: [Openstack] [OpenStack][Nova] Live Migration Error
Ok. Thx for the help :) On Tue, Jul 10, 2012 at 11:30 AM, Sébastien Han han.sebast...@gmail.comwrote: It's production ready, RedHat offers a commercial support on it. Just keep in mind that it's owned by Redhat ;) On Tue, Jul 10, 2012 at 12:24 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Is GlusterFS be more viable for a production environment? On Tue, Jul 10, 2012 at 11:17 AM, Sébastien Han han.sebast...@gmail.comwrote: Great! The last time I ran the live-migration, it was with GlusterFS and CephFS and I didn't changed any permissions in libvirt. I did the live-migration with NFS once but it was in Diablo (horrible), I don't really remember my setup. Maybe you should consider to try GlusterFS. On Tue, Jul 10, 2012 at 12:07 PM, Leander Bessa Beernaert leande...@gmail.com wrote: That did! Thanks :) Do you by change have any pointer on getting the live-migration to work without running libvirt under root? On Tue, Jul 10, 2012 at 10:55 AM, Sébastien Han han.sebast...@gmail.com wrote: Change the vncserver_listen to 0.0.0.0 and re-try the live-migration, you should get better results :) On Tue, Jul 10, 2012 at 11:52 AM, Leander Bessa Beernaert leande...@gmail.com wrote: If i don't run libvirt with root, it can't write to the shared folder. It's the only way i've been able to get this to work. :S Below follows the configuration of one of the compute nodes. 10.0.1.1 is the controller and 10.0.1.2 is the compute node. novncproxy_base_url=http://10.0.1.1:6080/vnc_auto.html xvpvncproxy_base_url=http://10.0.1.1:6081/console vncserver_proxyclient_address=10.0.1.2 vncserver_listen=10.0.1.2 On Tue, Jul 10, 2012 at 10:49 AM, Sébastien Han han.sebast...@gmail.com wrote: I forgot to ask, did you enable the vnc console? If so, with which parameters? On Tue, Jul 10, 2012 at 11:48 AM, Sébastien Han han.sebast...@gmail.com wrote: Hi! Usually you get: 2012-07-09 13:58:27.179+: 10227: warning : qemuDomainObjTaint:1134 : Domain id=2 name='instance-0002' uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges when you change permission in libvirt (root I presumed) which is not necessary. 2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 : Cannot find 'pm-is-supported' in path: No such file or directory This error is harmless and can be easily solved by installing the following package: sudo apt-get install pm-utils -y Do you have something in the nova-scheduler logs? Cheers! On Tue, Jul 10, 2012 at 11:29 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Well i've checked the libvirt logs on both nodes and i found these two lines: 2012-07-09 13:58:27.179+: 10227: warning : qemuDomainObjTaint:1134 : Domain id=2 name='instance-0002' uuid=57aca8a6-d062-4a08-8d87-e4d11d259ac7 is tainted: high-privileges 2012-07-09 13:58:27.736+: 10226: error : qemuMonitorIORead:513 : Unable to read from monitor: Connection reset by peer The log is alos filled with the message below, it gets repeated over and over and over. 2012-07-10 09:26:02.244+: 10229: error : virExecWithHook:328 : Cannot find 'pm-is-supported' in path: No such file or directory 2012-07-10 09:26:02.244+: 10229: warning : qemuCapsInit:856 : Failed to get host power management capabilities On Tue, Jul 10, 2012 at 8:16 AM, Razique Mahroua razique.mahr...@gmail.com wrote: Hi Leander, try to check libvirtd.log files, is the instance still running on the first node while you are lauching the migration process ? Razique *Nuage Co - Razique Mahroua** * razique.mahr...@gmail.com Le 9 juil. 2012 à 16:09, Leander Bessa Beernaert a écrit : Ok, so i've updated to the test packages from The migration still fails, but i see no errors in the logs. I'm trying to migrate a VM with the m1.tiny flavor from one machine to another. Their hardware are identical and they have more than enough resources to support the m1.tiny flavor: cloud35 (total) 43867 186 cloud35 (used_now) 0 312 5 cloud35 (used_max) 0 0 0 These are the logs from the origin compute node: http://paste.openstack.org/show/19319/ and the destination compute node: http://paste.openstack.org/show/19318/ . The scheduler's log has no visible errors or stack traces. I'm still using nfsv4. Any ideas? On Fri, Jul 6, 2012 at 7:57 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Thanks for the tip, it's a better than nothing :) Regards, Leander On Fri, Jul 6, 2012 at 6:32 PM, Mandar Vaze / मंदार वझे mandarv...@gmail.com wrote: Not sure if you are able to debug this, but a while ago there was a bug where instance.id was passed where instance.uuid was expected. This used to cause some problem. It looks like you are using distribution package rather than devstack
Re: [Openstack] [OpenStack][Nova] Live Migration Error
There is no error, it just doesn't do anything :s.
I've left the instance alone for 3 hours now and it's still stuck on the
original compute node.
On Mon, Jul 9, 2012 at 5:55 PM, Mandar Vaze / मंदार वझे
mandarv...@gmail.com wrote:
I see pre_live_migration in destination compute log, so migration at
least started.
Since there are no errors in either compute log, is it possible that
migration is taking long ? (Just a possibility)
When you say migration fails what error did you get ?
-Mandar
On Mon, Jul 9, 2012 at 7:39 PM, Leander Bessa Beernaert
leande...@gmail.com wrote:
Ok, so i've updated to the test packages from
The migration still fails, but i see no errors in the logs. I'm trying to
migrate a VM with the m1.tiny flavor from one machine to another. Their
hardware are identical and they have more than enough resources to support
the m1.tiny flavor:
cloud35 (total) 43867 186
cloud35 (used_now) 0 312 5
cloud35 (used_max) 0 0 0
These are the logs from the origin compute node:
http://paste.openstack.org/show/19319/ and the destination compute
node: http://paste.openstack.org/show/19318/ . The scheduler's log has
no visible errors or stack traces.
I'm still using nfsv4.
Any ideas?
On Fri, Jul 6, 2012 at 7:57 PM, Leander Bessa Beernaert
leande...@gmail.com wrote:
Thanks for the tip, it's a better than nothing :)
Regards,
Leander
On Fri, Jul 6, 2012 at 6:32 PM, Mandar Vaze / मंदार वझे
mandarv...@gmail.com wrote:
Not sure if you are able to debug this, but a while ago there was a bug
where instance.id was passed where instance.uuid was expected. This
used to cause some problem.
It looks like you are using distribution package rather than devstack
installation, so it is likely that the issue is now fixed. Can you try
latest packages (and/or try devstack if you can)
I wish I could help more.
-Mandar
On Fri, Jul 6, 2012 at 3:26 PM, Leander Bessa Beernaert
leande...@gmail.com wrote:
Hello,
I've recently setup a system to test out the live migration feature.
So far i've been able to launch the instances with the shared nfs folder.
However, when i run the live-migration command i encounter this error in
the destination compute node:
2012-07-05 09:33:48 ERROR nova.manager [-] Error during
ComputeManager.update_available_resource: Domain not found: no domain
with
matching id 2
2012-07-05 09:33:48 TRACE nova.manager Traceback (most recent call
last):
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/manager.py, line 155, in
periodic_tasks
2012-07-05 09:33:48 TRACE nova.manager task(self, context)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2409, in
update_available_resource
2012-07-05 09:33:48 TRACE nova.manager
self.driver.update_available_resource(context, self.host)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line
1936, in update_available_resource
2012-07-05 09:33:48 TRACE nova.manager 'vcpus_used':
self.get_vcpu_used(),
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line
1743, in get_vcpu_used
2012-07-05 09:33:48 TRACE nova.manager dom =
self._conn.lookupByID(dom_id)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/libvirt.py, line 2363, in lookupByID
2012-07-05 09:33:48 TRACE nova.manager if ret is None:raise
libvirtError('virDomainLookupByID() failed', conn=self)
2012-07-05 09:33:48 TRACE nova.manager libvirtError: Domain not
found: no domain with matching id 2
Any ideas on how to solve this?
Regards,
Leander
___
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
[Openstack] [OpenStack][Nova] Live Migration Error
Hello,
I've recently setup a system to test out the live migration feature. So far
i've been able to launch the instances with the shared nfs folder. However,
when i run the live-migration command i encounter this error in the
destination compute node:
2012-07-05 09:33:48 ERROR nova.manager [-] Error during
ComputeManager.update_available_resource: Domain not found: no domain with
matching id 2
2012-07-05 09:33:48 TRACE nova.manager Traceback (most recent call last):
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/manager.py, line 155, in
periodic_tasks
2012-07-05 09:33:48 TRACE nova.manager task(self, context)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2409, in
update_available_resource
2012-07-05 09:33:48 TRACE nova.manager
self.driver.update_available_resource(context, self.host)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line
1936, in update_available_resource
2012-07-05 09:33:48 TRACE nova.manager 'vcpus_used':
self.get_vcpu_used(),
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line
1743, in get_vcpu_used
2012-07-05 09:33:48 TRACE nova.manager dom =
self._conn.lookupByID(dom_id)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/libvirt.py, line 2363, in lookupByID
2012-07-05 09:33:48 TRACE nova.manager if ret is None:raise
libvirtError('virDomainLookupByID() failed', conn=self)
2012-07-05 09:33:48 TRACE nova.manager libvirtError: Domain not found: no
domain with matching id 2
Any ideas on how to solve this?
Regards,
Leander
___
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] [OpenStack][Nova] Help with libvirt unit-test - get_diagnostics command
Hello, I've been working on implementing the diagnostics command for libvirt - https://review.openstack.org/#/c/8839/ . Now i need to create the unit test for this new operation. I've been looking at the code to try and figure out an easy way to replicate this, but i'm a bit lost. What i need to do is simulate a connection to libvirt, create a fake instance with a predefined characteristics, retrieve the virtdomain and then verify the results from the get_diagnostics command. I'm more at loss as to how exactly do i setup a fake connection a create a fake instance? I thought about creating a dummy implementation as i've seen being used around the tests, however that doesn't give me any access to real method. Do note that I'm relatively new to python world, so there's a lot of things i can't grasp yes :s. Regards, Leander ___ 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] [OpenStack][Nova] Help with libvirt unit-test - get_diagnostics command
Daniel, thank you very much for your help!
However, i'm running into my infamous import libvirt problem again when
running the tests (see output below), i really though i'd fixed that one
for sure -.-'.
==
ERROR: test_diagnostic_full (nova.tests.test_libvirt.LibvirtConnTestCase)
--
Traceback (most recent call last):
File /home/gsd/nova/nova/tests/test_libvirt.py, line 1923, in
test_diagnostic_full
actual = conn.get_diagnostics({name: testvirt})
File /home/gsd/nova/nova/virt/libvirt/driver.py, line 2678, in
get_diagnostics
return diagnostics.get_diagnostics(dom)
File /home/gsd/nova/nova/virt/libvirt/diagnostics.py, line 97, in
get_diagnostics
import libvirt
ImportError: No module named libvirt
On Fri, Jul 6, 2012 at 1:11 PM, Daniel P. Berrange berra...@redhat.comwrote:
On Fri, Jul 06, 2012 at 11:59:51AM +0100, Leander Bessa Beernaert wrote:
Hello,
I've been working on implementing the diagnostics command for libvirt -
https://review.openstack.org/#/c/8839/ . Now i need to create the unit
test
for this new operation. I've been looking at the code to try and figure
out
an easy way to replicate this, but i'm a bit lost.
What i need to do is simulate a connection to libvirt, create a fake
instance with a predefined characteristics, retrieve the virtdomain and
then verify the results from the get_diagnostics command. I'm more at
loss
as to how exactly do i setup a fake connection a create a fake instance?
I
thought about creating a dummy implementation as i've seen being used
around the tests, however that doesn't give me any access to real method.
Do note that I'm relatively new to python world, so there's a lot of
things
i can't grasp yes :s.
As you say, figuring out the libvirt Nova test framework is not entirely
easy, particularly if you're new to Python / Nova. So to help you get
your patch through review, here is one suitable test case you can add to
test_libvirt.py for exercising the get_diagnostics API:
diff --git a/nova/tests/test_libvirt.py b/nova/tests/test_libvirt.py
index eed43b8..f3fa5ff 100644
--- a/nova/tests/test_libvirt.py
+++ b/nova/tests/test_libvirt.py
@@ -1938,6 +1938,91 @@ class LibvirtConnTestCase(test.TestCase):
got = jsonutils.loads(conn.get_cpu_info())
self.assertEqual(want, got)
+def test_diagnostic_full(self):
+xml =
+domain type='kvm'
+devices
+disk type='file'
+source file='filename'/
+target dev='vda' bus='virtio'/
+/disk
+disk type='block'
+source dev='/path/to/dev/1'/
+target dev='vdb' bus='virtio'/
+/disk
+interface type='network'
+mac address='52:54:00:a4:38:38'/
+source network='default'/
+target dev='vnet0'/
+/interface
+/devices
+/domain
+
+
+class DiagFakeDomain(FakeVirtDomain):
+
+def __init__(self):
+super(DiagFakeDomain, self).__init__(fake_xml=xml)
+
+def vcpus(self):
+return ([(0, 1, 1534000L, 0),
+ (1, 1, 164000L, 0),
+ (2, 1, 304000L, 0),
+ (3, 1, 142000L, 0)],
+[(True, False),
+ (True, False),
+ (True, False),
+ (True, False)])
+
+def blockStats(self, path):
+return (169L, 688640L, 0L, 0L, -1L)
+
+def interfaceStats(self, path):
+return (4408L, 82L, 0L, 0L, 0L, 0L, 0L, 0L)
+
+def memoryStats(self):
+return {'actual': 220160L, 'rss': 200164L}
+
+def maxMemory(self):
+return 280160L
+
+def fake_lookup_name(name):
+return DiagFakeDomain()
+
+self.mox.StubOutWithMock(libvirt_driver.LibvirtDriver, '_conn')
+libvirt_driver.LibvirtDriver._conn.lookupByName = fake_lookup_name
+
+conn = libvirt_driver.LibvirtDriver(False)
+actual = conn.get_diagnostics( { name: testvirt })
+expect = {'cpu0_time': 1534000L,
+ 'cpu1_time': 164000L,
+ 'cpu2_time': 304000L,
+ 'cpu3_time': 142000L,
+ 'vda_read': 688640L,
+ 'vda_read_req': 169L,
+ 'vda_write': 0L,
+ 'vda_write_req': 0L,
+ 'vda_errors
Re: [Openstack] 答复: [OpenStack][Nova] Live Migration + NFSv4 - Permission issues
I'm still using nfsv4 so far, still haven't tried with nfs3. I will give it shot on monday though. On Fri, Jul 6, 2012 at 6:24 PM, Anne Gentle anne.gen...@rackspace.comwrote: Sure, please make a doc bug at http://bugs.launchpad.net/Openstack-manuals and we'll triage it by linking to the conclusions posted here. Anne Gentle Content Stacker a...@openstack.org On Jul 6, 2012, at 1:11 PM, Mandar Vaze / मंदार वझे mandarv...@gmail.com wrote: So i've managed to get my instances to launch, thx Mandar! Does that mean you used nfsv3 ? Based on the comments on the URL, several people (all ??) seems to have problem with nfsv4 *Anne, Is it possible to add this to FAQ (or relevant document(s) )? *(after Leander confirms that nfs v3 solved the problem) (See https://answers.launchpad.net/nova/+question/164689, specifically comment #11) -Mandar ___ 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] [OpenStack][Nova] Live Migration Error
Thanks for the tip, it's a better than nothing :)
Regards,
Leander
On Fri, Jul 6, 2012 at 6:32 PM, Mandar Vaze / मंदार वझे
mandarv...@gmail.com wrote:
Not sure if you are able to debug this, but a while ago there was a bug
where instance.id was passed where instance.uuid was expected. This used
to cause some problem.
It looks like you are using distribution package rather than devstack
installation, so it is likely that the issue is now fixed. Can you try
latest packages (and/or try devstack if you can)
I wish I could help more.
-Mandar
On Fri, Jul 6, 2012 at 3:26 PM, Leander Bessa Beernaert
leande...@gmail.com wrote:
Hello,
I've recently setup a system to test out the live migration feature. So
far i've been able to launch the instances with the shared nfs folder.
However, when i run the live-migration command i encounter this error in
the destination compute node:
2012-07-05 09:33:48 ERROR nova.manager [-] Error during
ComputeManager.update_available_resource: Domain not found: no domain with
matching id 2
2012-07-05 09:33:48 TRACE nova.manager Traceback (most recent call last):
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/manager.py, line 155, in
periodic_tasks
2012-07-05 09:33:48 TRACE nova.manager task(self, context)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2409, in
update_available_resource
2012-07-05 09:33:48 TRACE nova.manager
self.driver.update_available_resource(context, self.host)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line
1936, in update_available_resource
2012-07-05 09:33:48 TRACE nova.manager 'vcpus_used':
self.get_vcpu_used(),
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line
1743, in get_vcpu_used
2012-07-05 09:33:48 TRACE nova.manager dom =
self._conn.lookupByID(dom_id)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/libvirt.py, line 2363, in lookupByID
2012-07-05 09:33:48 TRACE nova.manager if ret is None:raise
libvirtError('virDomainLookupByID() failed', conn=self)
2012-07-05 09:33:48 TRACE nova.manager libvirtError: Domain not found:
no domain with matching id 2
Any ideas on how to solve this?
Regards,
Leander
___
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] 答复: [OpenStack][Nova] Live Migration + NFSv4 - Permission issues
@Romi, check if the libvirt-bin is running, that usually means its not.
So i've managed to get my instances to launch, thx Mandar!
However, when i try to migrate i get this error:
2012-07-05 09:33:48 ERROR nova.manager [-] Error during
ComputeManager.update_available_resource: Domain not found: no domain with
matching id 2
2012-07-05 09:33:48 TRACE nova.manager Traceback (most recent call last):
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/manager.py, line 155, in
periodic_tasks
2012-07-05 09:33:48 TRACE nova.manager task(self, context)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2409, in
update_available_resource
2012-07-05 09:33:48 TRACE nova.manager
self.driver.update_available_resource(context, self.host)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line
1936, in update_available_resource
2012-07-05 09:33:48 TRACE nova.manager 'vcpus_used':
self.get_vcpu_used(),
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line
1743, in get_vcpu_used
2012-07-05 09:33:48 TRACE nova.manager dom =
self._conn.lookupByID(dom_id)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/libvirt.py, line 2363, in lookupByID
2012-07-05 09:33:48 TRACE nova.manager if ret is None:raise
libvirtError('virDomainLookupByID() failed', conn=self)
2012-07-05 09:33:48 TRACE nova.manager libvirtError: Domain not found: no
domain with matching id 2
Any ideas on how to debug solve this?
On Thu, Jul 5, 2012 at 9:03 AM, romi zhang romizhang1...@163.com wrote:
I am also met the problem when I restart nova-compute “libvirtError:
Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file
or directory” after modify factors of libvirt, also use NFS as share
storage.
** **
Romi
** **
** **
*发件人:* openstack-bounces+romizhang1968=163@lists.launchpad.net[mailto:
openstack-bounces+romizhang1968=163@lists.launchpad.net] *代表 *Mandar
Vaze / ? ???
*发送时间:* 2012年7月5日 星期四 12:14
*收件人:* Leander Bessa Beernaert
*抄送:* openstack@lists.launchpad.net
*主题:* Re: [Openstack] [OpenStack][Nova] Live Migration + NFSv4 -
Permission issues
** **
See if mounting as nfsv3 helps
See https://answers.launchpad.net/nova/+question/164689,
specifically comment #11
** **
-Mandar
On Tue, Jul 3, 2012 at 7:18 PM, Leander Bessa Beernaert
leande...@gmail.com wrote:
Hello all,
** **
I've been trying to get the live migration to work according to the guide
http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-live-migrations.html.
** **
So far i've setup 2 compute nodes and 1 controller node. They all share
the /var/lib/nova/instances dir. I've already verified that the nova user
id is the same across all the servers.
** **
Currently i'm running into this error when i launch an instance:
http://paste.openstack.org/show/19221/
** **
It's certainly a permission issue, so i tried adding the group nova to
the user libvirt-qemu. However, it still doesn't work. To which user must
i give the nova group permission in order to be able to write in that
directory?
** **
Regards,
Leander
___
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] [OpenStack][Nova] Live Migration + NFSv4 - Permission issues
Ok. so i have added the option you mentioned, restarted nfs and remounted on the compute nodes. Now i get this error: http://paste.openstack.org/show/19260/ :S On Wed, Jul 4, 2012 at 4:18 PM, Daniel P. Berrange berra...@redhat.comwrote: On Tue, Jul 03, 2012 at 02:48:05PM +0100, Leander Bessa Beernaert wrote: Hello all, I've been trying to get the live migration to work according to the guide http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-live-migrations.html . So far i've setup 2 compute nodes and 1 controller node. They all share the /var/lib/nova/instances dir. I've already verified that the nova user id is the same across all the servers. Currently i'm running into this error when i launch an instance: http://paste.openstack.org/show/19221/ It's certainly a permission issue, so i tried adding the group nova to the user libvirt-qemu. However, it still doesn't work. To which user must i give the nova group permission in order to be able to write in that directory? So the error message you get here: libvirtError: Unable to pre-create chardev file '/var/lib/nova/instances/instance-0004/console.log': Permission denied is coming from the libvirt QEMU driver code. This code runs as root:root in the libvirtd daemon. As such, ordinarily permissions would not be a problem that blocks libvirtd doing what it wants. NFS is horrible / special though, and has this capability root squash which causes any client host processes running as root to be treated as if they were running as 'nfsnobody' or a similar unprivileged user. So if you want libvirtd to be able to use this mount point you'll need to make sure that your NFS server has root squash disabled. eg by adding the option 'no_root_squash' to the /etc/exports file for that mount. Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/:| |: http://libvirt.org -o- http://virt-manager.org:| |: http://autobuild.org -o- http://search.cpan.org/~danberr/:| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc:| ___ 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] [OpenStack][Nova] Live Migration + NFSv4 - Permission issues
Can't seem to get around it .. Below are the current permissions on the folder in one of the compute nodes. I've already tried chmod o+x /var/lib/nova/instances/ but nothing happend :/ gsd@cloud33:~$ ls -l /var/lib/nova/instances/ total 4 drwxrwxr-x 2 nova nova 4096 Jul 3 13:33 _base gsd@cloud33:~$ ls -l /var/lib/nova/ total 136 drwxr-xr-x 6 nova nova 4096 Jul 3 13:11 CA drwxr-xr-x 2 nova nova 4096 Jun 25 20:11 buckets drwxr-xr-x 2 nova nova 4096 Jun 25 20:11 images drwxr-xr-x 3 nova nova 4096 Jul 4 15:45 instances drwxr-xr-x 2 nova nova 4096 Jun 25 20:11 keys drwxr-xr-x 2 nova nova 4096 Jun 25 20:11 networks -rw--- 1 nova nova 104448 Jul 3 13:13 nova.sqlite drwxr-xr-x 2 nova nova 4096 Jun 25 20:11 tmp On Wed, Jul 4, 2012 at 4:35 PM, Daniel P. Berrange berra...@redhat.comwrote: On Wed, Jul 04, 2012 at 04:24:42PM +0100, Leander Bessa Beernaert wrote: Ok. so i have added the option you mentioned, restarted nfs and remounted on the compute nodes. Now i get this error: http://paste.openstack.org/show/19260/ libvirtError: internal error Process exited while reading console log output: chardev: opening backend file failed: Permission denied This is an error from QEMU itself. So it shows libvirtd has successfully done its part of the work. Unless you have changed your qemu.conf file, then QEMU will normally run as the 'qemu:qemu' user/group pair. So you should make sure that user account has r-x permission on the directory where the images are stored. QEMU doesn't need write permission on the directory - libvirtd makes sure the files themselves are writable Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/:| |: http://libvirt.org -o- http://virt-manager.org:| |: http://autobuild.org -o- http://search.cpan.org/~danberr/:| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc:| ___ 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] [OpenStack][Nova] Live Migration + NFSv4 - Permission issues
Hello all, I've been trying to get the live migration to work according to the guide http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-live-migrations.html. So far i've setup 2 compute nodes and 1 controller node. They all share the /var/lib/nova/instances dir. I've already verified that the nova user id is the same across all the servers. Currently i'm running into this error when i launch an instance: http://paste.openstack.org/show/19221/ It's certainly a permission issue, so i tried adding the group nova to the user libvirt-qemu. However, it still doesn't work. To which user must i give the nova group permission in order to be able to write in that directory? Regards, Leander ___ 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] [OpenStack][Nova] Live Migration + NFSv4 - Permission issues
Currently it's using the default permission. Everything belongs to user nova and the group nova. On Tue, Jul 3, 2012 at 4:23 PM, Sébastien Han han.sebast...@gmail.comwrote: Which permissions did you set on /var/lib/nova/instances? On Tue, Jul 3, 2012 at 3:48 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello all, I've been trying to get the live migration to work according to the guide http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-live-migrations.html. So far i've setup 2 compute nodes and 1 controller node. They all share the /var/lib/nova/instances dir. I've already verified that the nova user id is the same across all the servers. Currently i'm running into this error when i launch an instance: http://paste.openstack.org/show/19221/ It's certainly a permission issue, so i tried adding the group nova to the user libvirt-qemu. However, it still doesn't work. To which user must i give the nova group permission in order to be able to write in that directory? Regards, Leander ___ 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] [OpenStack][Nova] Live Migration + NFSv4 - Permission issues
Here's an output from ls -l: drwxr-xr-x 3 nova nova 4096 Jul 3 14:10 instances On Tue, Jul 3, 2012 at 4:25 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Currently it's using the default permission. Everything belongs to user nova and the group nova. On Tue, Jul 3, 2012 at 4:23 PM, Sébastien Han han.sebast...@gmail.comwrote: Which permissions did you set on /var/lib/nova/instances? On Tue, Jul 3, 2012 at 3:48 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello all, I've been trying to get the live migration to work according to the guide http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-live-migrations.html. So far i've setup 2 compute nodes and 1 controller node. They all share the /var/lib/nova/instances dir. I've already verified that the nova user id is the same across all the servers. Currently i'm running into this error when i launch an instance: http://paste.openstack.org/show/19221/ It's certainly a permission issue, so i tried adding the group nova to the user libvirt-qemu. However, it still doesn't work. To which user must i give the nova group permission in order to be able to write in that directory? Regards, Leander ___ 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] [OpenStack][Nova] Live Migration + NFSv4 - Permission issues
Still the same problem :S On Tue, Jul 3, 2012 at 4:46 PM, Marnus van Niekerk m...@mjvn.net wrote: Have you tried setting the ownership of /var/lib/nova/instances to the nova user? sudo chown -R nova:nova /var/lib/nova/instances M On 03/07/2012 15:48, Leander Bessa Beernaert wrote: Hello all, I've been trying to get the live migration to work according to the guide http://docs.openstack.org/**trunk/openstack-compute/admin/** content/configuring-live-**migrations.htmlhttp://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-live-migrations.html. So far i've setup 2 compute nodes and 1 controller node. They all share the /var/lib/nova/instances dir. I've already verified that the nova user id is the same across all the servers. Currently i'm running into this error when i launch an instance: http://paste.openstack.org/**show/19221/http://paste.openstack.org/show/19221/ It's certainly a permission issue, so i tried adding the group nova to the user libvirt-qemu. However, it still doesn't work. To which user must i give the nova group permission in order to be able to write in that directory? Regards, Leander __**_ Mailing list: https://launchpad.net/~**openstackhttps://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~**openstackhttps://launchpad.net/~openstack More help : https://help.launchpad.net/**ListHelphttps://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] [OpenStack][Nova] Issues with run_tests.sh, no tests are run when import libvirt is present
Thanks, that let me see the real problem now:
./tools/with_venv.sh nosetests -svx nova
nose.config: INFO: Set working dir to /home/gsd/nova/nova/tests
nose.config: INFO: Working directory /home/gsd/nova/nova/tests is a
package; adding to sys.path
nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$']
nose.plugins.cover: INFO: Coverage report will include only packages:
['nova']
nose.selector: INFO: /home/gsd/nova/nova/auth/opendj.sh is executable;
skipped
nose.selector: INFO: /home/gsd/nova/nova/auth/slap.sh is executable;
skipped
nose.selector: INFO: /home/gsd/nova/nova/cloudpipe/bootscript.template is
executable; skipped
Failure: ImportError (No module named libvirt) ... ERROR
==
ERROR: Failure: ImportError (No module named libvirt)
--
Traceback (most recent call last):
File
/home/gsd/nova/.venv/local/lib/python2.7/site-packages/nose/loader.py,
line 390, in loadTestsFromName
addr.filename, addr.module)
File
/home/gsd/nova/.venv/local/lib/python2.7/site-packages/nose/importer.py,
line 39, in importFromPath
return self.importFromDir(dir_path, fqname)
File
/home/gsd/nova/.venv/local/lib/python2.7/site-packages/nose/importer.py,
line 86, in importFromDir
mod = load_module(part_fqname, fh, filename, desc)
File /home/gsd/nova/nova/test.py, line 41, in module
from nova.tests import fake_flags
File /home/gsd/nova/nova/tests/fake_flags.py, line 24, in module
flags.DECLARE('compute_scheduler_driver', 'nova.scheduler.multi')
File /home/gsd/nova/nova/flags.py, line 52, in DECLARE
__import__(module_string, globals(), locals())
File /home/gsd/nova/nova/scheduler/multi.py, line 27, in module
from nova.scheduler import driver
File /home/gsd/nova/nova/scheduler/driver.py, line 53, in module
flags.DECLARE('libvirt_type', 'nova.virt.libvirt.connection')
File /home/gsd/nova/nova/flags.py, line 52, in DECLARE
__import__(module_string, globals(), locals())
File /home/gsd/nova/nova/virt/libvirt/connection.py, line 73, in
module
from nova.virt.libvirt import diagnostics as libvirt_diagnostics
File /home/gsd/nova/nova/virt/libvirt/diagnostics.py, line 75, in
module
import libvirt as virt
ImportError: No module named libvirt
--
Ran 1 test in 0.002s
FAILED (errors=1)
Libvirt is present on my system, i can import it through the python
interpreter from any location. Yet, it still says it is not present. Could
this have to do with the virtual_env or fakelibvirt?
On Fri, Jun 29, 2012 at 6:54 PM, Jay Pipes jaypi...@gmail.com wrote:
Hi Leander,
I've noticed some weirdness with the openstack.nose_plugin (which is used
by default for the Nova test runner) sometimes either throwing errors
(particularly errors raised by nosetests) away and/or coming up with a
different set of skip tests than when running just with nosetests.
So, I'd recommend running just this:
./tools/with_venv.sh nosetests -svx nova
That will stop at the first error and probably will give you better
insight into the actual errors that are likely being suppressed by the
openstack nose plugin.
best,
-jay
On 06/29/2012 09:02 AM, Leander Bessa Beernaert wrote:
Hello,
I'm sorry to restart the topic
(https://lists.launchpad.net/**openstack/msg13621.htmlhttps://lists.launchpad.net/openstack/msg13621.html),
but
i accidentally deleted the message in my inbox :S.
I'm still having the same problem, each time i add import libvirt to
the file diangostics.py
(https://review.openstack.org/**#/c/8839/https://review.openstack.org/#/c/8839/)
the
entire test suit won't run.
*With the import* present i get the following output:
--**--**
--
Ran 0 tests in 0.000s
OK Running PEP8 and HACKING compliance check...
2 imports missing in this test environment
*Without the import *present it get this output:
--**--**
--
Ran 3030 tests in 233.326s
OK (SKIP=22) Running PEP8 and HACKING compliance check...
11 imports missing in this test environment
The problem now is that, according to the OpenStack conventions, the
import must be present. However, with the import present i can't get any
of the tests to run.
I'm no expert in Python, so could someone please help me out here?
Regards,
Leander
__**_
Mailing list:
https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe :
https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
More help :
https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp
Re: [Openstack] [OpenStack][Nova] Issues with run_tests.sh, no tests are run when import libvirt is present
So, if no system packages can be imported, how do you test the connection
class for the libvirt driver?
How does that particular test case wrap around the fact that it requires
the libvirt module? The only thing i could find are these lines of code in
the driver's __init__ method. Do these somehow detect if this is a unit
test environment and import the fakelibvirt driver instead? I'm no expert
in python so i'm not sure what's happening there :s
global libvirt
if libvirt is None:
libvirt = __import__('libvirt')
Regards,
Leander
On Mon, Jul 2, 2012 at 1:27 PM, Monty Taylor mord...@inaugust.com wrote:
On 07/02/2012 06:02 AM, Leander Bessa Beernaert wrote:
Thanks, that let me see the real problem now:
./tools/with_venv.sh nosetests -svx nova
nose.config: INFO: Set working dir to /home/gsd/nova/nova/tests
nose.config: INFO: Working directory /home/gsd/nova/nova/tests is a
package; adding to sys.path
nose.config: INFO: Ignoring files matching ['^\\.', '^_',
'^setup\\.py$']
nose.plugins.cover: INFO: Coverage report will include only
packages: ['nova']
nose.selector: INFO: /home/gsd/nova/nova/auth/opendj.sh is
executable; skipped
nose.selector: INFO: /home/gsd/nova/nova/auth/slap.sh is executable;
skipped
nose.selector: INFO:
/home/gsd/nova/nova/cloudpipe/bootscript.template is executable;
skipped
Failure: ImportError (No module named libvirt) ... ERROR
==
ERROR: Failure: ImportError (No module named libvirt)
--
Traceback (most recent call last):
File
/home/gsd/nova/.venv/local/lib/python2.7/site-packages/nose/loader.py,
line 390, in loadTestsFromName
addr.filename, addr.module)
File
/home/gsd/nova/.venv/local/lib/python2.7/site-packages/nose/importer.py,
line 39, in importFromPath
return self.importFromDir(dir_path, fqname)
File
/home/gsd/nova/.venv/local/lib/python2.7/site-packages/nose/importer.py,
line 86, in importFromDir
mod = load_module(part_fqname, fh, filename, desc)
File /home/gsd/nova/nova/test.py, line 41, in module
from nova.tests import fake_flags
File /home/gsd/nova/nova/tests/fake_flags.py, line 24, in
module
flags.DECLARE('compute_scheduler_driver', 'nova.scheduler.multi')
File /home/gsd/nova/nova/flags.py, line 52, in DECLARE
__import__(module_string, globals(), locals())
File /home/gsd/nova/nova/scheduler/multi.py, line 27, in module
from nova.scheduler import driver
File /home/gsd/nova/nova/scheduler/driver.py, line 53, in
module
flags..DECLARE('libvirt_type', 'nova.virt.libvirt.connection')
File /home/gsd/nova/nova/flags.py, line 52, in DECLARE
__import__(module_string, globals(), locals())
File /home/gsd/nova/nova/virt/libvirt/connection.py, line 73, in
module
from nova.virt.libvirt import diagnostics as libvirt_diagnostics
File /home/gsd/nova/nova/virt/libvirt/diagnostics.py, line 75,
in module
import libvirt as virt
ImportError: No module named libvirt
--
Ran 1 test in 0.002s
FAILED (errors=1)
Libvirt is present on my system, i can import it through the python
interpreter from any location. Yet, it still says it is not present.
Could this have to do with the virtual_env or fakelibvirt?
Yes. Our virtualenvs are currently configured to not allow system
packages to be used (so that they only use python libs installed into
the virtualenv. However, libvirt is not installable via pip, which is a
problem.
We've recently added a new tox environment to help with this, so try
running:
tox -v -efull
Which is set up to allow system site packages.
However, if you're adding unittests, you should look at the other ones
which test for libvirt existence and skip the tests if they can't find it.
On Fri, Jun 29, 2012 at 6:54 PM, Jay Pipes jaypi...@gmail.com
mailto:jaypi...@gmail.com wrote:
Hi Leander,
I've noticed some weirdness with the openstack.nose_plugin (which is
used by default for the Nova test runner) sometimes either throwing
errors (particularly errors raised by nosetests) away and/or coming
up with a different set of skip tests than when running just with
nosetests.
So, I'd recommend running just this:
./tools/with_venv.sh nosetests -svx nova
That will stop at the first error and probably will give you better
insight into the actual errors that are likely being suppressed by
the openstack nose plugin.
best,
-jay
On 06/29/2012 09:02 AM, Leander Bessa Beernaert wrote:
Hello
Re: [Openstack] [OpenStack][Nova] Issues with run_tests.sh, no tests are run when import libvirt is present
I'm developing on custom branch and haven't updated the repository for at
least 3 weeks.
Do i fetch the lastest changes like this:
git remote update
git checkout master
git pull origin master
git checkout branch
git pull master
?
On Mon, Jul 2, 2012 at 1:44 PM, Monty Taylor mord...@inaugust.com wrote:
On 07/02/2012 08:43 AM, Leander Bessa Beernaert wrote:
So, if no system packages can be imported, how do you test the
connection class for the libvirt driver?
We're working on that - but as I said, please try running tox -efull
which _should_ run tests with libvirt support enabled.
How does that particular test case wrap around the fact that it requires
the libvirt module? The only thing i could find are these lines of code
in the driver's __init__ method. Do these somehow detect if this is a
unit test environment and import the fakelibvirt driver instead? I'm no
expert in python so i'm not sure what's happening there :s
global libvirt
if libvirt is None:
libvirt = __import__('libvirt')
Regards,
Leander
On Mon, Jul 2, 2012 at 1:27 PM, Monty Taylor mord...@inaugust.com
mailto:mord...@inaugust.com wrote:
On 07/02/2012 06:02 AM, Leander Bessa Beernaert wrote:
Thanks, that let me see the real problem now:
./tools/with_venv.sh nosetests -svx nova
nose.config: INFO: Set working dir to /home/gsd/nova/nova/tests
nose.config: INFO: Working directory /home/gsd/nova/nova/tests
is a
package; adding to sys.path
nose.config: INFO: Ignoring files matching ['^\\.', '^_',
'^setup\\.py$']
nose.plugins.cover: INFO: Coverage report will include only
packages: ['nova']
nose.selector: INFO: /home/gsd/nova/nova/auth/opendj.sh is
executable; skipped
nose.selector: INFO: /home/gsd/nova/nova/auth/slap.sh is
executable;
skipped
nose.selector: INFO:
/home/gsd/nova/nova/cloudpipe/bootscript.template is
executable; skipped
Failure: ImportError (No module named libvirt) ... ERROR
==
ERROR: Failure: ImportError (No module named libvirt)
--
Traceback (most recent call last):
File
/home/gsd/nova/.venv/local/lib/python2.7/site-packages/nose/loader.py,
line 390, in loadTestsFromName
addr.filename, addr.module)
File
/home/gsd/nova/.venv/local/lib/python2.7/site-packages/nose/importer.py,
line 39, in importFromPath
return self.importFromDir(dir_path, fqname)
File
/home/gsd/nova/.venv/local/lib/python2.7/site-packages/nose/importer.py,
line 86, in importFromDir
mod = load_module(part_fqname, fh, filename, desc)
File /home/gsd/nova/nova/test.py, line 41, in module
from nova.tests import fake_flags
File /home/gsd/nova/nova/tests/fake_flags.py, line 24, in
module
flags.DECLARE('compute_scheduler_driver',
'nova.scheduler.multi')
File /home/gsd/nova/nova/flags.py, line 52, in DECLARE
__import__(module_string, globals(), locals())
File /home/gsd/nova/nova/scheduler/multi.py, line 27, in
module
from nova.scheduler import driver
File /home/gsd/nova/nova/scheduler/driver.py, line 53, in
module
flags..DECLARE('libvirt_type',
'nova.virt.libvirt.connection')
File /home/gsd/nova/nova/flags.py, line 52, in DECLARE
__import__(module_string, globals(), locals())
File /home/gsd/nova/nova/virt/libvirt/connection.py, line
73, in
module
from nova.virt.libvirt import diagnostics as
libvirt_diagnostics
File /home/gsd/nova/nova/virt/libvirt/diagnostics.py, line
75,
in module
import libvirt as virt
ImportError: No module named libvirt
--
Ran 1 test in 0.002s
FAILED (errors=1)
Libvirt is present on my system, i can import it through the python
interpreter from any location. Yet, it still says it is not
present.
Could this have to do with the virtual_env or fakelibvirt?
Yes. Our virtualenvs are currently configured to not allow system
packages to be used (so that they only use python libs installed into
the virtualenv. However, libvirt is not installable via pip, which
is a
problem.
We've recently added a new tox environment to help with this, so try
running:
tox -v -efull
Which is set up to allow
Re: [Openstack] [OpenStack][Nova] Issues with run_tests.sh, no tests are run when import libvirt is present
@Jay Thx. @Monty I'm unable to run tox -efull, it keeps saying the command could not be located. I'm supposed to run this from the same place i run run_tests.sh right? On Mon, Jul 2, 2012 at 2:08 PM, Jay Pipes jaypi...@gmail.com wrote: On 07/02/2012 08:57 AM, Leander Bessa Beernaert wrote: I'm developing on custom branch and haven't updated the repository for at least 3 weeks. Do i fetch the lastest changes like this: git remote update git checkout master git pull origin master git checkout branch git pull master Remember to git stash your current working changes first... # Ensure you are in your local working git branch # (not your local master) git stash --all git checkout master git pull git checkout $WORKINGBRANCH git rebase master git stash pop and then handle any merge conflicts that may pop up. Best, -jay ___ 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] [OpenStack][Nova] Issues with run_tests.sh, no tests are run when import libvirt is present
Running with ./run_tests.sh -N nova.tests.test_libvirt works just fine,
however i don't know if this is enough to get it past jenkins :/
On Mon, Jul 2, 2012 at 3:26 PM, Daniel P. Berrange berra...@redhat.comwrote:
On Mon, Jul 02, 2012 at 01:43:31PM +0100, Leander Bessa Beernaert wrote:
So, if no system packages can be imported, how do you test the
connection
class for the libvirt driver?
How does that particular test case wrap around the fact that it requires
the libvirt module? The only thing i could find are these lines of code
in
the driver's __init__ method. Do these somehow detect if this is a unit
test environment and import the fakelibvirt driver instead? I'm no expert
in python so i'm not sure what's happening there :s
global libvirt
if libvirt is None:
libvirt = __import__('libvirt')
If you have installed all the neccessary python packages on your
local host, then it is entirely possible to run the Nova test
suites without using virtualenv. You just need to pass the '-N'
arg to the run_tests.sh script, eg on my Fedora 17 host, I can
run
./run_tests.sh -N nova.tests.test_libvirt
Regards,
Daniel
--
|: http://berrange.com -o-http://www.flickr.com/photos/dberrange/:|
|: http://libvirt.org -o- http://virt-manager.org:|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/:|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc:|
___
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] [OpenStack][Nova] Issues with run_tests.sh, no tests are run when import libvirt is present
I have never tested it on a machine which doesn't have libvirt, i'll get
back to you on that.
I've ran tox -v -epy27 and it produced this ouput
--
Ran 0 tests in 0.001s
OK
_
summary
_
py27: commands succeeded
congratulations :)
and this is the output produced by tox -v -efull:
--
Ran 3046 tests in 217.842s
OK (SKIP=5)
Exception KeyError: KeyError(25433840,) in module 'threading' from
'/usr/lib/python2.7/threading.pyc' ignored
_
summary
_
full: commands succeeded
congratulations :)
I think the problem still remains :S
On Mon, Jul 2, 2012 at 4:48 PM, Monty Taylor mord...@inaugust.com wrote:
Run:
sudo pip install tox
And you will get the tox command.
Does ./run_tests.sh -N nova.tests.test_libvirt work fine when you
_don't_ have libvirt? It needs to skip the test if you don't have
libvirt installed, and it needs to run it and pass if you do.
Jenkins is going to run tox -v -epy27 and then eventually also tox -v
-efull - so make sure both of those work and you'll be set.
Monty
On 07/02/2012 10:30 AM, Leander Bessa Beernaert wrote:
Running with ./run_tests.sh -N nova.tests.test_libvirt works just
fine, however i don't know if this is enough to get it past jenkins :/
On Mon, Jul 2, 2012 at 3:26 PM, Daniel P. Berrange berra...@redhat.com
mailto:berra...@redhat.com wrote:
On Mon, Jul 02, 2012 at 01:43:31PM +0100, Leander Bessa Beernaert
wrote:
So, if no system packages can be imported, how do you test the
connection
class for the libvirt driver?
How does that particular test case wrap around the fact that it
requires
the libvirt module? The only thing i could find are these lines of
code in
the driver's __init__ method. Do these somehow detect if this is a
unit
test environment and import the fakelibvirt driver instead? I'm no
expert
in python so i'm not sure what's happening there :s
global libvirt
if libvirt is None:
libvirt = __import__('libvirt')
If you have installed all the neccessary python packages on your
local host, then it is entirely possible to run the Nova test
suites without using virtualenv. You just need to pass the '-N'
arg to the run_tests.sh script, eg on my Fedora 17 host, I can
run
./run_tests.sh -N nova.tests.test_libvirt
Regards,
Daniel
--
|: http://berrange.com -o-
http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o-
http://virt-manager.org :|
|: http://autobuild.org -o-
http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o-
http://live.gnome.org/gtk-vnc :|
___
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] [OpenStack][Nova] Issues with run_tests.sh, no tests are run when import libvirt is present
Hello, I'm sorry to restart the topic ( https://lists.launchpad.net/openstack/msg13621.html), but i accidentally deleted the message in my inbox :S. I'm still having the same problem, each time i add import libvirt to the file diangostics.py (https://review.openstack.org/#/c/8839/) the entire test suit won't run. *With the import* present i get the following output: -- Ran 0 tests in 0.000s OK Running PEP8 and HACKING compliance check... 2 imports missing in this test environment *Without the import *present it get this output: -- Ran 3030 tests in 233.326s OK (SKIP=22) Running PEP8 and HACKING compliance check... 11 imports missing in this test environment The problem now is that, according to the OpenStack conventions, the import must be present. However, with the import present i can't get any of the tests to run. I'm no expert in Python, so could someone please help me out here? Regards, Leander ___ 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] [OpenStack][Nova] Possible inconsistency between devstack/nova execution and test_virt_drivers.py
Ok. I will add the required methods to the fakelbvirt. Regards, Leander On Wed, Jun 27, 2012 at 4:50 PM, Jay Pipes jaypi...@gmail.com wrote: On 06/27/2012 10:17 AM, Leander Bessa Beernaert wrote: snip How do I proceed now? Should i ate the required methods to the fake_libvirt? Do note that i dont have the latest libvirt installed and am therefore missing another set of crucial methods which i can't test. :s No. In general, you only want to put methods into the fake driver that are *called* by the OpenStack code. If you are calling methods on the VirDomain with your new diagnostics code, then yes, you will need to implement corresponding fake methods in the fake driver. All the best, -jay __**_ Mailing list: https://launchpad.net/~**openstackhttps://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~**openstackhttps://launchpad.net/~openstack More help : https://help.launchpad.net/**ListHelphttps://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] [OpenStack][Nova] Snapshot stuck in Queued state, no erros found in compute log
I've tried to snapshot again today and i found this error in the compute.log: http://paste.openstack.org/show/18882/ Any ideas? On Tue, Jun 26, 2012 at 9:26 AM, Leander Bessa Beernaert leande...@gmail.com wrote: I can't find any error traces in the glance api and registry log. On Mon, Jun 25, 2012 at 7:39 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: Usually queued means it didn't ever get uploaded into glance. Any errors in the glance log? I have never seen the error below, but it could be related. Vish On Jun 25, 2012, at 3:50 AM, Leander Bessa Beernaert wrote: Hello, I've performed snapshots over and over without ever running into trouble, however now one of them is stuck in the Queued state. I've searched the machine's compute.log for any indication of an error, but nothing showed up. I did a quick search and usually the erros appear in the compute.log or the libivirtd.log. The only thing i found in the libvirtd.log were these two lines: 2012-06-25 10:37:05.957+: 6830: warning : qemuCapsInit:856 : Failed to get host power management capabilities 2012-06-25 10:37:06.612+: 6831: error : virExecWithHook:328 : Cannot find 'pm-is-supported' in path: No such file or director Could that be the problem? Regards, Leander ___ 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] [OpenStack][Nova] Possible inconsistency between devstack/nova execution and test_virt_drivers.py
I've been looking at the implementation of the tests and i the fake_libvirt is a bit incomplete and lacks a lot of methods. This lack of methods causes my diagnostics code to fail the test since an error is produced. For instance this is the output from dir(virDomain) from the fake_libvirt: ['UUIDString', 'XMLDesc', '__class__', '__delattr__', '__dict__', '__doc__', '__format__', '__getattribute__', '__hash__', '__init__', '__module__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__weakref__', '_connection', '_def', '_has_saved_state', '_parse_definition', '_snapshots', '_state', '_transient', 'attachDevice', 'blockStats', 'create', 'createWithFlags', 'destroy', 'detachDevice', 'hasManagedSaveImage', 'info', 'interfaceStats', 'isActive', 'managedSave', 'managedSaveRemove', 'name', 'reset', 'resume', 'shutdown', 'snapshotCreateXML', 'suspend', 'undefine'] and below from the real libvirt: ['ID', 'OSType', 'UUID', 'UUIDString', 'XMLDesc', '__del__', '__doc__', '__init__', '__module__', '_conn', '_o', 'abortJob', 'attachDevice', 'attachDeviceFlags', 'autostart', 'blkioParameters', 'blockInfo', 'blockIoTune', 'blockJobAbort', 'blockJobInfo', 'blockJobSetSpeed', 'blockPeek', 'blockPull', 'blockResize', 'blockStats', 'blockStatsFlags', 'connect', 'controlInfo', 'coreDump', 'create', 'createWithFlags', 'destroy', 'destroyFlags', 'detachDevice', 'detachDeviceFlags', 'hasCurrentSnapshot', 'hasManagedSaveImage', 'info', 'injectNMI', 'interfaceStats', 'isActive', 'isPersistent', 'isUpdated', 'jobInfo', 'managedSave', 'managedSaveRemove', 'maxMemory', 'maxVcpus', 'memoryParameters', 'memoryPeek', 'memoryStats', 'migrate', 'migrate2', 'migrateGetMaxSpeed', 'migrateSetMaxDowntime', 'migrateSetMaxSpeed', 'migrateToURI', 'migrateToURI2', 'name', 'openConsole', 'openGraphics', 'pinVcpu', 'pinVcpuFlags', 'reboot', 'reset', 'resume', 'revertToSnapshot', 'save', 'saveFlags', 'schedulerParameters', 'schedulerParametersFlags', 'schedulerType', 'screenshot', 'sendKey', 'setAutostart', 'setBlkioParameters', 'setBlockIoTune', 'setMaxMemory', 'setMemory', 'setMemoryFlags', 'setMemoryParameters', 'setSchedulerParameters', 'setSchedulerParametersFlags', 'setVcpus', 'setVcpusFlags', 'shutdown', 'snapshotCreateXML', 'snapshotCurrent', 'snapshotListNames', 'snapshotLookupByName', 'snapshotNum', 'state', 'suspend', 'undefine', 'undefineFlags', 'updateDeviceFlags', 'vcpuPinInfo', 'vcpus', 'vcpusFlags'] How do I proceed now? Should i ate the required methods to the fake_libvirt? Do note that i dont have the latest libvirt installed and am therefore missing another set of crucial methods which i can't test. :s On Mon, Jun 25, 2012 at 4:43 PM, Leander Bessa Beernaert leande...@gmail.com wrote: I've implemented a diagnostics method for libvirt. The code works perfectly with the devstack installation. However, when i run the test from run_tests.sh this happens: http://paste.openstack.org/show/18754/. From what i've been told from the irc channel, the data supplied by the test is different than the one i'm currently receiving. Now, i'm unsure which data type i should except from the get_diagnostics method. On Mon, Jun 25, 2012 at 4:01 PM, Sean Dague sda...@linux.vnet.ibm.comwrote: On 06/25/2012 10:41 AM, Leander Bessa Beernaert wrote: Hello, I'm working on the diagnostics method for libvirt. I've successfully managed to test it while running it manually and with devstack. However, the test case in test_virt_drivers.py fails since it supplies a different data type to the method. Could it be possible that there's a certain mismatch between the two or that this particular method accepts multiple sorts of data-types? Can you be more specific with the issue? I've been in that code recently, so I might be able to help sort this out. -Sean -- Sean Dague IBM Linux Technology Center email: sda...@linux.vnet.ibm.com alt-email: slda...@us.ibm.com __**_ Mailing list: https://launchpad.net/~**openstackhttps://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~**openstackhttps://launchpad.net/~openstack More help : https://help.launchpad.net/**ListHelphttps://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] [OpenStack][Nova] Snapshot stuck in Queued state, no erros found in compute log
You sir a my hero! I turned out someone altered the filesystem before installing OpenStack leaving me with 3gb partition for the operating system. Thanks. Leander On Wed, Jun 27, 2012 at 4:32 PM, Jay Pipes jaypi...@gmail.com wrote: This looks very familiar :) Make sure that you have enough space in the partition that houses /tmp (usually whatever partition has / mounted). The snapshot operation requires at least as much space in /tmp as the size of the snapshot to be made. If you have improperly given yourself a very small root partition (likely if you are using devstack or devstack's PXE images), then you can remedy the situation using a bit of a hack: ln -s /tmp /some/mount/with/space Best, -jay On 06/27/2012 08:52 AM, Leander Bessa Beernaert wrote: I've tried to snapshot again today and i found this error in the compute.log: http://paste.openstack.org/**show/18882/http://paste.openstack.org/show/18882/ Any ideas? On Tue, Jun 26, 2012 at 9:26 AM, Leander Bessa Beernaert leande...@gmail.com mailto:leande...@gmail.com wrote: I can't find any error traces in the glance api and registry log. On Mon, Jun 25, 2012 at 7:39 PM, Vishvananda Ishaya vishvana...@gmail.com mailto:vishvana...@gmail.com** wrote: Usually queued means it didn't ever get uploaded into glance. Any errors in the glance log? I have never seen the error below, but it could be related. Vish On Jun 25, 2012, at 3:50 AM, Leander Bessa Beernaert wrote: Hello, I've performed snapshots over and over without ever running into trouble, however now one of them is stuck in the Queued state. I've searched the machine's compute.log for any indication of an error, but nothing showed up. I did a quick search and usually the erros appear in the compute.log or the libivirtd.log. The only thing i found in the libvirtd.log were these two lines: 2012-06-25 10:37:05.957+: 6830: warning : qemuCapsInit:856 : Failed to get host power management capabilities 2012-06-25 10:37:06.612+: 6831: error : virExecWithHook:328 : Cannot find 'pm-is-supported' in path: No such file or director Could that be the problem? Regards, Leander __**_ Mailing list: https://launchpad.net/~**openstackhttps://launchpad.net/~openstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.**launchpad.netopenstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~**openstackhttps://launchpad.net/~openstack More help : https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp __**_ Mailing list: https://launchpad.net/~**openstackhttps://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~**openstackhttps://launchpad.net/~openstack More help : https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp __**_ Mailing list: https://launchpad.net/~**openstackhttps://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~**openstackhttps://launchpad.net/~openstack More help : https://help.launchpad.net/**ListHelphttps://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] [OpenStack][Nova] Multi-host ip mix up.
I've tried again this morning: The ip adress assigned to the vm in the dashboard is 10.0.9.3, however the instances only responds to pings on the compute node where it was launched and with the ip address 10.0.9.7. Here's the vm's log: http://paste.openstack.org/show/18796/ and the ip is assigned to br109 with the ip 10.0.9.7. I'm using a vlan configuration, the instances for this project are all launched on a network assigned to vlan109. On Mon, Jun 25, 2012 at 9:03 PM, Vishvananda Ishaya vishvana...@gmail.comwrote: 10.0.9.5 is probably the ip that nova assigned to your compute host for the bridge. ip addr show should show it on br100 There is likely something else going on that is causing your instance to fail to network properly. I would check the console output of the vm first, make sure it is getting an ip address. If that looks good, check for security group rules, then start doing tcpdump to see where you are losing packets. Vish On Jun 25, 2012, at 9:08 AM, Leander Bessa Beernaert wrote: Hello, I've setup OpenStack with a multi-host configuration. Everything appears to be working fine. However, when i launch an instance, it get's assigned an ip (10.0.9.3) and when i ping that IP i get this output: ping 10.0.9.3 PING 10.0.9.3 (10.0.9.3) 56(84) bytes of data. From 10.0.9.5 icmp_seq=1 Destination Host Unreachable From 10.0.9.5 icmp_seq=2 Destination Host Unreachable From 10.0.9.5 icmp_seq=3 Destination Host Unreachable If i ping the adress 10.0.9.5 i get a response. ping 10.0.9.5 PING 10.0.9.5 (10.0.9.5) 56(84) bytes of data. 64 bytes from 10.0.9.5: icmp_req=1 ttl=64 time=0.043 ms 64 bytes from 10.0.9.5: icmp_req=2 ttl=64 time=0.035 ms 64 bytes from 10.0.9.5: icmp_req=3 ttl=64 time=0.036 ms Any idea what's happening here? Regards, Leander ___ 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] [OpenStack][Nova] No tests available in custom branch
I'v tried doing those modifications directly on the master branch, just to see if the tests would run. Sadly, i get the same output. Am i supposed to change something when adding new files before running the tests? On Tue, Jun 26, 2012 at 9:36 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Performing the alteration you suggested did not change anything, the output from run_tests.sh is still the same: ./run_tests.sh -- Ran 0 tests in 0.000s OK Running PEP8 and HACKING compliance check... 4 imports missing in this test environment Any ideas? On Mon, Jun 25, 2012 at 7:01 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote: On Mon, 2012-06-25 at 16:56 +0100, Leander Bessa Beernaert wrote: Here's the diff http://paste.openstack.org/show/18756/ Change import diagnostics to from nova.virt.libvirt import diagnostics. (Also note that you may need to add a space between your name and your email address in Authors, and if you mean to submit this to the trunk, it'd be nice to put your entry in the alphabetically-appropriate place…) -- Kevin L. Mitchell kevin.mitch...@rackspace.com ___ 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] [OpenStack][Nova] No tests available in custom branch
I've successfully imported the diagnostics.py in the interpreter, so that can't be the problem. On Tue, Jun 26, 2012 at 3:40 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote: On Tue, 2012-06-26 at 09:36 +0100, Leander Bessa Beernaert wrote: Any ideas? My gut instinct is that you have a syntax error as well, somewhere in diagnostics.py. Try running the python interpreter and manually trying that import; if it fails, you should have an error message that will help you track down what the problem is. -- Kevin L. Mitchell kevin.mitch...@rackspace.com ___ 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] [OpenStack][Nova] No tests available in custom branch
You sir are my hero! File stdin, line 1, in module File connection.py, line 73, in module from nova.virt.libvirt import diagnostics ImportError: cannot import name diagnostics The file, is right there in the same directory. I have double checked the names but it still keeps failing :s On Tue, Jun 26, 2012 at 3:56 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote: On Tue, 2012-06-26 at 15:50 +0100, Leander Bessa Beernaert wrote: I've successfully imported the diagnostics.py in the interpreter, so that can't be the problem. Then try importing the other file you modified. If that still doesn't help you find the problem, then I'm all out of ideas… -- Kevin L. Mitchell kevin.mitch...@rackspace.com ___ 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] [OpenStack][Nova] No tests available in custom branch
It works from the top level, but fails if i try to import it directly from the same dir (nova/virt/libvirt). The other files there import just fine :/ On Tue, Jun 26, 2012 at 4:17 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote: On Tue, 2012-06-26 at 16:05 +0100, Leander Bessa Beernaert wrote: The file, is right there in the same directory. I have double checked the names but it still keeps failing :s The first thing I'd try is clearing out all your *.pyc files. (run_tests.sh should do this for you, so I don't expect this to actually fix your problem, but it's a place to start…) Also, double-check the permissions on the diagnostics.py file. Finally, verify that your current directory is the top-level directory of the repository, not the nova subdirectory of the repository… -- Kevin L. Mitchell kevin.mitch...@rackspace.com ___ 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] [OpenStack][Nova] No tests available in custom branch
I'm not calling run_tests.sh from the nova subdirectory. I'm saying that from the location where nova_tests.sh is located, i can import connection.py. However, when i try to import connection.py from with cd=nova/virt/libvirt, it fails. The funny thing is i can import all the modules int that directory perfectly, except connection.py. On Tue, Jun 26, 2012 at 4:28 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote: On Tue, 2012-06-26 at 16:21 +0100, Leander Bessa Beernaert wrote: It works from the top level, but fails if i try to import it directly from the same dir (nova/virt/libvirt). The other files there import just fine :/ Relative imports are iffy at best; imports should ideally always be absolute. This is why I suggest that you should always call run_tests.sh from the top-level of the repository, not from the nova subdirectory… -- Kevin L. Mitchell kevin.mitch...@rackspace.com ___ 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] [OpenStack][Nova] No tests available in custom branch
I've managed to fix it by removing the import libvirt from diagnostics.py. I've got the answer to this through sdague in the openstack-dev irc channel. I'ts now running :) On Tue, Jun 26, 2012 at 4:44 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote: On Tue, 2012-06-26 at 16:33 +0100, Leander Bessa Beernaert wrote: I'm not calling run_tests.sh from the nova subdirectory. I'm saying that from the location where nova_tests.sh is located, i can import connection.py. However, when i try to import connection.py from with cd=nova/virt/libvirt, it fails. The funny thing is i can import all the modules int that directory perfectly, except connection.py. That's expected. Whenever you run Python, the current directory is added to the import path. connection.py has several absolute imports that it depends on being able to import; when you run from the top-level of the repo, things like nova.virt.libvirt.utils can be found, whereas importing from the nova/virt/libvirt directory means that nova.virt.libvirt makes no sense. -- Kevin L. Mitchell kevin.mitch...@rackspace.com ___ 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] [OpenStack][Nova] Snapshot stuck in Queued state, no erros found in compute log
Hello, I've performed snapshots over and over without ever running into trouble, however now one of them is stuck in the Queued state. I've searched the machine's compute.log for any indication of an error, but nothing showed up. I did a quick search and usually the erros appear in the compute.log or the libivirtd.log. The only thing i found in the libvirtd.log were these two lines: 2012-06-25 10:37:05.957+: 6830: warning : qemuCapsInit:856 : Failed to get host power management capabilities 2012-06-25 10:37:06.612+: 6831: error : virExecWithHook:328 : Cannot find 'pm-is-supported' in path: No such file or director Could that be the problem? Regards, Leander ___ 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] [OpenStack][Swift] Global data backup, possible or not?
Hello, I've been tasked with finding out if Swift has any means of performing a consistent global backup of all the information stored, which then could easily be restored in case of failure. I've been reading the documentation and these are my conclusions so far are: - Swift maintains a copy of the data throughout each storage node; - The data contained in these nodes, might or not be up to date. It depends mainly on whether the replicator has propagated all the changes or not. Is there a way in which i could backup the data from swift and ensure that the backed-up data is up to date at the time of the backup? Regards, Leander ___ 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] [OpenStack][Nova] No tests available in custom branch
I've tried all the options and the output is always, even with -V and -f: -- Ran 0 tests in 0.000s OK Running PEP8 and HACKING compliance check... 5 imports missing in this test environment The tests run just fine on the master branch :/ On Mon, Jun 25, 2012 at 2:39 PM, Joseph Suh j...@isi.edu wrote: Leander, Did you give -V -f option? If you post your log, it would be easier to help. Thanks, Joseph (w) 703-248-6160 (c) 571-340-2434 (f) 703-812-3712 3811 N. Fairfax Drive Suite 200 Arlington, VA, 22203, USA http://www.east.isi.edu/~jsuh - Original Message - From: Leander Bessa Beernaert leande...@gmail.com To: openstack@lists.launchpad.net Sent: Monday, June 25, 2012 9:13:43 AM Subject: [Openstack] [OpenStack][Nova] No tests available in custom branch Hello, I've created a separate branch in Nova to test my code out. However, every time i attempt to run the command run_tests.sh it says it has 0 tests to be run. I followed the guide from http://wiki.openstack.org/GerritWorkflowto setup the branch. Did i miss something? Regards, Leander ___ 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] [OpenStack][Nova] No tests available in custom branch
I've just added a new file and added a new method in the connection.py of libvirt. Those are the changes i made, surely they haven' screwed up the test system :/ On Mon, Jun 25, 2012 at 3:00 PM, Joseph Suh j...@isi.edu wrote: Leander, If it works fine in master branch, the problem must be due to some changes in your own branch. Thanks, Joseph (w) 703-248-6160 (c) 571-340-2434 (f) 703-812-3712 3811 N. Fairfax Drive Suite 200 Arlington, VA, 22203, USA http://www.east.isi.edu/~jsuh - Original Message - From: Leander Bessa Beernaert leande...@gmail.com To: Joseph Suh j...@isi.edu Cc: openstack@lists.launchpad.net Sent: Monday, June 25, 2012 9:45:51 AM Subject: Re: [Openstack] [OpenStack][Nova] No tests available in custom branch I've tried all the options and the output is always, even with -V and -f: -- Ran 0 tests in 0.000s OK Running PEP8 and HACKING compliance check... 5 imports missing in this test environment The tests run just fine on the master branch :/ On Mon, Jun 25, 2012 at 2:39 PM, Joseph Suh j...@isi.edu wrote: Leander, Did you give -V -f option? If you post your log, it would be easier to help. Thanks, Joseph (w) 703-248-6160 (c) 571-340-2434 (f) 703-812-3712 3811 N. Fairfax Drive Suite 200 Arlington, VA, 22203, USA http://www.east.isi.edu/~jsuh - Original Message - From: Leander Bessa Beernaert leande...@gmail.com To: openstack@lists.launchpad.net Sent: Monday, June 25, 2012 9:13:43 AM Subject: [Openstack] [OpenStack][Nova] No tests available in custom branch Hello, I've created a separate branch in Nova to test my code out. However, every time i attempt to run the command run_tests.sh it says it has 0 tests to be run. I followed the guide from http://wiki.openstack.org/GerritWorkflowto setup the branch. Did i miss something? Regards, Leander ___ 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
[Openstack] [OpenStack][Nova] Possible inconsistency between devstack/nova execution and test_virt_drivers.py
Hello, I'm working on the diagnostics method for libvirt. I've successfully managed to test it while running it manually and with devstack. However, the test case in test_virt_drivers.py fails since it supplies a different data type to the method. Could it be possible that there's a certain mismatch between the two or that this particular method accepts multiple sorts of data-types? Regards, Leander ___ 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] [OpenStack][Nova] Possible inconsistency between devstack/nova execution and test_virt_drivers.py
Sorry, forgot to add the code: *This is my method (this worked with devstack):* def get_diagnostics(self, instance): dom = self._lookup_by_name(instance['name']) return diagnostics.get_diagnostics(dom) *and this the test method*: def test_get_diagnostics(self): instance_ref, network_info = self._get_running_instance() self.connection.get_diagnostics(instance_ref['name']) On Mon, Jun 25, 2012 at 3:41 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm working on the diagnostics method for libvirt. I've successfully managed to test it while running it manually and with devstack. However, the test case in test_virt_drivers.py fails since it supplies a different data type to the method. Could it be possible that there's a certain mismatch between the two or that this particular method accepts multiple sorts of data-types? Regards, Leander ___ 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] [OpenStack][Nova] Possible inconsistency between devstack/nova execution and test_virt_drivers.py
I would like to add that I did not implement the test method, it was already there. Also it supplies a different set of data than the one i received when working with devstack. Which of the data types should i assume to be correct, the one from devstack or the one from the test? On Mon, Jun 25, 2012 at 4:10 PM, Jay Pipes jaypi...@gmail.com wrote: You are not returning the data in the test method, whereas you are in the real method :) -jay On 06/25/2012 10:44 AM, Leander Bessa Beernaert wrote: Sorry, forgot to add the code: *This is my method (this worked with devstack):* def get_diagnostics(self, instance): dom = self._lookup_by_name(instance[**'name']) return diagnostics.get_diagnostics(**dom) *and this the test method*: def test_get_diagnostics(self): instance_ref, network_info = self._get_running_instance() self.connection.get_**diagnostics(instance_ref['**name']) On Mon, Jun 25, 2012 at 3:41 PM, Leander Bessa Beernaert leande...@gmail.com mailto:leande...@gmail.com wrote: Hello, I'm working on the diagnostics method for libvirt. I've successfully managed to test it while running it manually and with devstack. However, the test case in test_virt_drivers.py fails since it supplies a different data type to the method. Could it be possible that there's a certain mismatch between the two or that this particular method accepts multiple sorts of data-types? Regards, Leander __**_ Mailing list: https://launchpad.net/~**openstackhttps://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~**openstackhttps://launchpad.net/~openstack More help : https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp __**_ Mailing list: https://launchpad.net/~**openstackhttps://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~**openstackhttps://launchpad.net/~openstack More help : https://help.launchpad.net/**ListHelphttps://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] [OpenStack][Nova] Possible inconsistency between devstack/nova execution and test_virt_drivers.py
I've implemented a diagnostics method for libvirt. The code works perfectly with the devstack installation. However, when i run the test from run_tests.sh this happens: http://paste.openstack.org/show/18754/. From what i've been told from the irc channel, the data supplied by the test is different than the one i'm currently receiving. Now, i'm unsure which data type i should except from the get_diagnostics method. On Mon, Jun 25, 2012 at 4:01 PM, Sean Dague sda...@linux.vnet.ibm.comwrote: On 06/25/2012 10:41 AM, Leander Bessa Beernaert wrote: Hello, I'm working on the diagnostics method for libvirt. I've successfully managed to test it while running it manually and with devstack. However, the test case in test_virt_drivers.py fails since it supplies a different data type to the method. Could it be possible that there's a certain mismatch between the two or that this particular method accepts multiple sorts of data-types? Can you be more specific with the issue? I've been in that code recently, so I might be able to help sort this out. -Sean -- Sean Dague IBM Linux Technology Center email: sda...@linux.vnet.ibm.com alt-email: slda...@us.ibm.com __**_ Mailing list: https://launchpad.net/~**openstackhttps://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~**openstackhttps://launchpad.net/~openstack More help : https://help.launchpad.net/**ListHelphttps://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] [OpenStack][Nova] No tests available in custom branch
Here's the diff http://paste.openstack.org/show/18756/ On Mon, Jun 25, 2012 at 4:53 PM, Brian Waldon brian.wal...@rackspace.comwrote: I usually run into this kind of problem when I break an import or add an unfulfillable import somewhere in Nova or Glance. Could you post a diff for us to take a look at? Brian On Jun 25, 2012, at 7:03 AM, Leander Bessa Beernaert wrote: I've just added a new file and added a new method in the connection.py of libvirt. Those are the changes i made, surely they haven' screwed up the test system :/ On Mon, Jun 25, 2012 at 3:00 PM, Joseph Suh j...@isi.edu wrote: Leander, If it works fine in master branch, the problem must be due to some changes in your own branch. Thanks, Joseph (w) 703-248-6160 (c) 571-340-2434 (f) 703-812-3712 3811 N. Fairfax Drive Suite 200 Arlington, VA, 22203, USA http://www.east.isi.edu/~jsuh - Original Message - From: Leander Bessa Beernaert leande...@gmail.com To: Joseph Suh j...@isi.edu Cc: openstack@lists.launchpad.net Sent: Monday, June 25, 2012 9:45:51 AM Subject: Re: [Openstack] [OpenStack][Nova] No tests available in custom branch I've tried all the options and the output is always, even with -V and -f: -- Ran 0 tests in 0.000s OK Running PEP8 and HACKING compliance check... 5 imports missing in this test environment The tests run just fine on the master branch :/ On Mon, Jun 25, 2012 at 2:39 PM, Joseph Suh j...@isi.edu wrote: Leander, Did you give -V -f option? If you post your log, it would be easier to help. Thanks, Joseph (w) 703-248-6160 (c) 571-340-2434 (f) 703-812-3712 3811 N. Fairfax Drive Suite 200 Arlington, VA, 22203, USA http://www.east.isi.edu/~jsuh - Original Message - From: Leander Bessa Beernaert leande...@gmail.com To: openstack@lists.launchpad.net Sent: Monday, June 25, 2012 9:13:43 AM Subject: [Openstack] [OpenStack][Nova] No tests available in custom branch Hello, I've created a separate branch in Nova to test my code out. However, every time i attempt to run the command run_tests.sh it says it has 0 tests to be run. I followed the guide from http://wiki.openstack.org/GerritWorkflow to setup the branch. Did i miss something? Regards, Leander ___ 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 ___ 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] [OpenStack][Nova] Multi-host ip mix up.
Hello, I've setup OpenStack with a multi-host configuration. Everything appears to be working fine. However, when i launch an instance, it get's assigned an ip (10.0.9.3) and when i ping that IP i get this output: ping 10.0.9.3 PING 10.0.9.3 (10.0.9.3) 56(84) bytes of data. From 10.0.9.5 icmp_seq=1 Destination Host Unreachable From 10.0.9.5 icmp_seq=2 Destination Host Unreachable From 10.0.9.5 icmp_seq=3 Destination Host Unreachable If i ping the adress 10.0.9.5 i get a response. ping 10.0.9.5 PING 10.0.9.5 (10.0.9.5) 56(84) bytes of data. 64 bytes from 10.0.9.5: icmp_req=1 ttl=64 time=0.043 ms 64 bytes from 10.0.9.5: icmp_req=2 ttl=64 time=0.035 ms 64 bytes from 10.0.9.5: icmp_req=3 ttl=64 time=0.036 ms Any idea what's happening here? Regards, Leander ___ 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] [OpenStack][Nova] Can't access the outside from inside my instances.
Hello, I'm having trouble accessing the outside world from within my instances. For instance, i can ping other instances on my network but i am unable to ping www.google.com. Any ideas? Regards, Leander ___ 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] [OpenStack][Nova] Can't access the outside from inside my instances.
On Wed, Jun 6, 2012 at 2:33 PM, Anton Haldin ahal...@griddynamics.comwrote: Do you have default router in VM ? netstat -rn Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 10.0.8.10.0.0.0 UG0 0 0 eth0 10.0.8.00.0.0.0 255.255.255.192 U 0 0 0 eth0 Do you have multinode configuration ? if all services on one node, do you have ip_forward enabled? sysctl net.ipv4.ip_forward I have one controller node and 4 compute nodes. On Wed, Jun 6, 2012 at 5:16 PM, Leander Bessa Beernaert leande...@gmail.com wrote: This is what i find inside my vms: domain novalocal search novalocal nameserver 10.0.8.1 I believe the name resolution is working (see output bellow from the ping command), but the vm's seem unable to access the ip. ping www.google.com PING www.l.google.com (74.125.230.16) 56(84) bytes of data. On Wed, Jun 6, 2012 at 2:12 PM, Anton Haldin ahal...@griddynamics.comwrote: dns ? resolv.conf in VM On Wed, Jun 6, 2012 at 4:51 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having trouble accessing the outside world from within my instances. For instance, i can ping other instances on my network but i am unable to ping www.google.com. Any ideas? Regards, Leander ___ 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] [OpenStack][Nova] Can't access the outside from inside my instances.
I turned out to be a routing problem with the vlan configuration i was using. Thanks for the help nonetheless! Regards, Leander On Wed, Jun 6, 2012 at 2:50 PM, Leander Bessa Beernaert leande...@gmail.com wrote: On the host node, the value of /proc/sys/net/ipv4/ip_forward is 1. On Wed, Jun 6, 2012 at 2:39 PM, Anton Haldin ahal...@griddynamics.comwrote: you can check net.ipv4.ip_forward on machine with ip interface 10.0.8.1 i think on this machine you should have nova-network ( it manages iptables rules, brctl( bridges)) also you can use tcpdump on interface of VM to search icmp packets. On Wed, Jun 6, 2012 at 5:34 PM, Leander Bessa Beernaert leande...@gmail.com wrote: On Wed, Jun 6, 2012 at 2:33 PM, Anton Haldin ahal...@griddynamics.comwrote: Do you have default router in VM ? netstat -rn Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 10.0.8.10.0.0.0 UG0 0 0 eth0 10.0.8.00.0.0.0 255.255.255.192 U 0 0 0 eth0 Do you have multinode configuration ? if all services on one node, do you have ip_forward enabled? sysctl net.ipv4.ip_forward I have one controller node and 4 compute nodes. On Wed, Jun 6, 2012 at 5:16 PM, Leander Bessa Beernaert leande...@gmail.com wrote: This is what i find inside my vms: domain novalocal search novalocal nameserver 10.0.8.1 I believe the name resolution is working (see output bellow from the ping command), but the vm's seem unable to access the ip. ping www.google.com PING www.l.google.com (74.125.230.16) 56(84) bytes of data. On Wed, Jun 6, 2012 at 2:12 PM, Anton Haldin ahal...@griddynamics.com wrote: dns ? resolv.conf in VM On Wed, Jun 6, 2012 at 4:51 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having trouble accessing the outside world from within my instances. For instance, i can ping other instances on my network but i am unable to ping www.google.com. Any ideas? Regards, Leander ___ 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] [Nova] Instances which use flavors with disk space fail to spawn
The host has a swap partition of 4GB :/
On Wed, May 30, 2012 at 9:59 PM, Vishvananda Ishaya v...@kokkocloud.comwrote:
The scheduler by default has a ram overcommit of 1.5. Instances should be
able to launch correctly and use swap, so I suspect you have no swap setup
on the host?
you can change the commit ratio using the config option
ram_allocation_ratio
Vish
On May 30, 2012, at 2:31 AM, Leander Bessa Beernaert wrote:
I'm using the filter scheduler.
On Wed, May 30, 2012 at 5:44 AM, Vaze, Mandar mandar.v...@nttdata.comwrote:
I'm a bit disappointed that the request even went through to the
compute node to build the instance, as the scheduler *should* already know
the memory exceeds the available memory on the box.
FilterScheduler (and chanceScheduler?) checks this condition before
sending to Compute, SimpleScheduler does not.
Leander : Which scheduler are you using ?
-Mandar
-Original Message-
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net[mailto:
openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf
Of Jay Pipes
Sent: Wednesday, May 30, 2012 12:58 AM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] [Nova] Instances which use flavors with disk
space fail to spawn
Leander, I would submit a bug about this. The error message is cryptic
(to say the least!) and I think it would be better if the scheduler
determined if the flavor requested has a memory request greater than the
total amount available on the server! I'm a bit disappointed that the
request even went through to the compute node to build the instance, as the
scheduler *should* already know the memory exceeds the available memory on
the box.
Best,
-jay
On 05/29/2012 11:07 AM, Leander Bessa Beernaert wrote:
For anyone interested, i've figured out that the instances were not
getting spawned because the amount of memory in the flavor was equal to
the maximum memory available through the underlying hardware.
On Tue, May 29, 2012 at 11:10 AM, Leander Bessa Beernaert
leande...@gmail.com mailto:leande...@gmail.com wrote:
Hello,
I'm unable to boot any image with a flavor that has a disk space
associated with it. It always fails at the spawning state. Below it
the log output of nova-compute:
2012-05-28 16:20:25 ERROR nova.compute.manager
[req-1c725f9c-acae-47c4-b5ae-9ed5d2d9830c
9494d025721c4d7bb28a16fa796f9414
04282e9aff474d2383bb4d4417673e0a] [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] Instance failed to
spawn
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] Traceback (most recent
call last):
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py,
line 592, in _spawn
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7]
self._legacy_nw_info(network_info), block_device_info)
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] File
/usr/lib/python2.7/dist-packages/nova/exception.py, line
114, in wrapped
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] return f(*args,
**kw)
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py,
line 922, in spawn
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7]
self._create_new_domain(xml)
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py,
line 1575, in _create_new_domain
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7]
domain.createWithFlags(launch_flags)
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] File
/usr/lib/python2.7/dist-packages/libvirt.py, line 581, in
createWithFlags
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] if ret == -1:
raise libvirtError ('virDomainCreateWithFlags() failed',
dom=self)
2012-05-28 16:20:25 TRACE nova.compute.manager
[Openstack] [OpenStack][Nova][libvirt] libvirtError: Unable to read from monitor: Connection reset by peer
Hello, I'm having the following output http://paste.openstack.org/show/18275/ when i try to run an instance on another compute node. I have no idea why this is happening. I'm using the m1.tiny flavor for testing purposes. I have 3 separate compute nodes and one all-in-one node , 4 compute nodes total. The error is similar to the one i posted a while back ( https://lists.launchpad.net/openstack/msg12427.html), but it now occurs under different circumstances. Any help is really appreciated, i've been stuck with this for the past 4 hours. I've tried restarting all compute services, libvirt, the host itself but nothing helps. Regards, Leander ___ 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] [OpenStack][Nova][libvirt] libvirtError: Unable to read from monitor: Connection reset by peer
I think this solved it: https://answers.launchpad.net/nova/+question/198270 On Thu, May 31, 2012 at 5:29 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having the following output http://paste.openstack.org/show/18275/ when i try to run an instance on another compute node. I have no idea why this is happening. I'm using the m1.tiny flavor for testing purposes. I have 3 separate compute nodes and one all-in-one node , 4 compute nodes total. The error is similar to the one i posted a while back ( https://lists.launchpad.net/openstack/msg12427.html), but it now occurs under different circumstances. Any help is really appreciated, i've been stuck with this for the past 4 hours. I've tried restarting all compute services, libvirt, the host itself but nothing helps. Regards, Leander ___ 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] Instances which use flavors with disk space fail to spawn
I'm using the filter scheduler.
On Wed, May 30, 2012 at 5:44 AM, Vaze, Mandar mandar.v...@nttdata.comwrote:
I'm a bit disappointed that the request even went through to the compute
node to build the instance, as the scheduler *should* already know the
memory exceeds the available memory on the box.
FilterScheduler (and chanceScheduler?) checks this condition before
sending to Compute, SimpleScheduler does not.
Leander : Which scheduler are you using ?
-Mandar
-Original Message-
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net[mailto:
openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf
Of Jay Pipes
Sent: Wednesday, May 30, 2012 12:58 AM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] [Nova] Instances which use flavors with disk
space fail to spawn
Leander, I would submit a bug about this. The error message is cryptic (to
say the least!) and I think it would be better if the scheduler determined
if the flavor requested has a memory request greater than the total amount
available on the server! I'm a bit disappointed that the request even went
through to the compute node to build the instance, as the scheduler
*should* already know the memory exceeds the available memory on the box.
Best,
-jay
On 05/29/2012 11:07 AM, Leander Bessa Beernaert wrote:
For anyone interested, i've figured out that the instances were not
getting spawned because the amount of memory in the flavor was equal to
the maximum memory available through the underlying hardware.
On Tue, May 29, 2012 at 11:10 AM, Leander Bessa Beernaert
leande...@gmail.com mailto:leande...@gmail.com wrote:
Hello,
I'm unable to boot any image with a flavor that has a disk space
associated with it. It always fails at the spawning state. Below it
the log output of nova-compute:
2012-05-28 16:20:25 ERROR nova.compute.manager
[req-1c725f9c-acae-47c4-b5ae-9ed5d2d9830c
9494d025721c4d7bb28a16fa796f9414
04282e9aff474d2383bb4d4417673e0a] [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] Instance failed to
spawn
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] Traceback (most recent
call last):
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py,
line 592, in _spawn
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7]
self._legacy_nw_info(network_info), block_device_info)
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] File
/usr/lib/python2.7/dist-packages/nova/exception.py, line
114, in wrapped
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] return f(*args,
**kw)
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py,
line 922, in spawn
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7]
self._create_new_domain(xml)
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py,
line 1575, in _create_new_domain
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7]
domain.createWithFlags(launch_flags)
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] File
/usr/lib/python2.7/dist-packages/libvirt.py, line 581, in
createWithFlags
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] if ret == -1:
raise libvirtError ('virDomainCreateWithFlags() failed',
dom=self)
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] libvirtError: Unable
to read from monitor: Connection reset by peer
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7]
2012-05-28 16:20:25 DEBUG nova.compute.manager
[req-1c725f9c-acae-47c4-b5ae-9ed5d2d9830c
9494d025721c4d7bb28a16fa796f9414
Re: [Openstack] [Nova] Instances which use flavors with disk space fail to spawn
Bug submitted: https://bugs.launchpad.net/nova/+bug/1006322
On Wed, May 30, 2012 at 10:31 AM, Leander Bessa Beernaert
leande...@gmail.com wrote:
I'm using the filter scheduler.
On Wed, May 30, 2012 at 5:44 AM, Vaze, Mandar mandar.v...@nttdata.comwrote:
I'm a bit disappointed that the request even went through to the
compute node to build the instance, as the scheduler *should* already know
the memory exceeds the available memory on the box.
FilterScheduler (and chanceScheduler?) checks this condition before
sending to Compute, SimpleScheduler does not.
Leander : Which scheduler are you using ?
-Mandar
-Original Message-
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net[mailto:
openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf
Of Jay Pipes
Sent: Wednesday, May 30, 2012 12:58 AM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] [Nova] Instances which use flavors with disk
space fail to spawn
Leander, I would submit a bug about this. The error message is cryptic
(to say the least!) and I think it would be better if the scheduler
determined if the flavor requested has a memory request greater than the
total amount available on the server! I'm a bit disappointed that the
request even went through to the compute node to build the instance, as the
scheduler *should* already know the memory exceeds the available memory on
the box.
Best,
-jay
On 05/29/2012 11:07 AM, Leander Bessa Beernaert wrote:
For anyone interested, i've figured out that the instances were not
getting spawned because the amount of memory in the flavor was equal to
the maximum memory available through the underlying hardware.
On Tue, May 29, 2012 at 11:10 AM, Leander Bessa Beernaert
leande...@gmail.com mailto:leande...@gmail.com wrote:
Hello,
I'm unable to boot any image with a flavor that has a disk space
associated with it. It always fails at the spawning state. Below it
the log output of nova-compute:
2012-05-28 16:20:25 ERROR nova.compute.manager
[req-1c725f9c-acae-47c4-b5ae-9ed5d2d9830c
9494d025721c4d7bb28a16fa796f9414
04282e9aff474d2383bb4d4417673e0a] [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] Instance failed to
spawn
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] Traceback (most recent
call last):
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py,
line 592, in _spawn
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7]
self._legacy_nw_info(network_info), block_device_info)
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] File
/usr/lib/python2.7/dist-packages/nova/exception.py, line
114, in wrapped
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] return f(*args,
**kw)
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py,
line 922, in spawn
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7]
self._create_new_domain(xml)
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py,
line 1575, in _create_new_domain
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7]
domain.createWithFlags(launch_flags)
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] File
/usr/lib/python2.7/dist-packages/libvirt.py, line 581, in
createWithFlags
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] if ret == -1:
raise libvirtError ('virDomainCreateWithFlags() failed',
dom=self)
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7] libvirtError: Unable
to read from monitor: Connection reset by peer
2012-05-28 16:20:25 TRACE nova.compute.manager [instance:
10d7c8e0-e05b-4e57-b722-dab5771261b7]
2012-05
[Openstack] [OpenStack][Horizon] Can't list users
Hello, I'm unable to list users in the openstack dashboard. I'm using the packages provided with ubuntu 12.04. Here's the log outputted by horizon: http://paste.openstack.org/show/18228/ Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
