Re: [Openstack-community] [Question #181560]: Multi node nova installation
Question #181560 on OpenStack Compute (nova) changed: https://answers.launchpad.net/nova/+question/181560 Status: Open = Expired Launchpad Janitor expired the question: This question was expired because it remained in the 'Open' state without activity for the last 15 days. -- You received this question notification because you are a direct subscriber of the question. -- Mailing list: https://launchpad.net/~openstack-community Post to : openstack-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-community More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Automatically confirmed after 24 hours on Resize API
We should file a bug saying we have missing functionality and link to the spec for a definition of that functionality. The spec itself doesn't need to change. Brian On Dec 27, 2011, at 10:20 AM, Nachi Ueno wrote: Hi Biran Thank you for your reply. So this is a bug of the doc for now? 2011/12/27 Brian Waldon brian.wal...@rackspace.com: Hi Nachi! You are 100% correct, we have not yet implemented that in Nova. I don't see any bugs/blueprints referencing this, so maybe if one was created we could make sure it gets done. Thanks! Brian On Dec 26, 2011, at 11:48 PM, Nachi Ueno wrote: Hi folks The doc says *All resizes are automatically confirmed after 24 hours if they are not explicitly confirmed or reverted*, but I couldn't found such implementations. Is this a bug of Nova? or Is this a bug of doc? The resize function converts an existing server to a different flavor, in essence, scaling the server up or down. The original server is saved for a period of time to allow rollback if there is a problem. All resizes should be tested and explicitly confirmed, at which time the original server is removed. *All resizes are automatically confirmed after 24 hours if they are not explicitly confirmed or reverted*. http://docs.openstack.org/api/openstack-compute/1.1/content/Resize_Server-d1e3707.html Cheers Nachi Ueno ___ 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] Automatically confirmed after 24 hours on Resize API
Hi Biran Thank you for your reply. So this is a bug of the doc for now? 2011/12/27 Brian Waldon brian.wal...@rackspace.com: Hi Nachi! You are 100% correct, we have not yet implemented that in Nova. I don't see any bugs/blueprints referencing this, so maybe if one was created we could make sure it gets done. Thanks! Brian On Dec 26, 2011, at 11:48 PM, Nachi Ueno wrote: Hi folks The doc says *All resizes are automatically confirmed after 24 hours if they are not explicitly confirmed or reverted*, but I couldn't found such implementations. Is this a bug of Nova? or Is this a bug of doc? The resize function converts an existing server to a different flavor, in essence, scaling the server up or down. The original server is saved for a period of time to allow rollback if there is a problem. All resizes should be tested and explicitly confirmed, at which time the original server is removed. *All resizes are automatically confirmed after 24 hours if they are not explicitly confirmed or reverted*. http://docs.openstack.org/api/openstack-compute/1.1/content/Resize_Server-d1e3707.html Cheers Nachi Ueno ___ 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]Instances are running, but they cannot be pinged.
Hi. What are your images types? I had this problem with raw and qcow2 images. AMI images work fine for me. qcow2 does not work and raw images worked in a first time and no more. Have you checked your log files? 2011/12/27 Xuyun Zhang xyzhan...@gmail.com Hi folks, It appears that I have successfully run my instances with the 'running' status. However, I can't ping to the instance and get the console output. I have authorized the ping and ssh. There is no directory like /var/lib/nova/instance/instance-/ So I guess the instances actually have terminated. What's the possible causes? Are there any guys who had the same experience? Your information will be highly appreciated. Regards, Sean ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Alisson Pontes __ Network Technology Evolution Researcher CPqD - Center for Research and Development in Telecommunications Tel.: +55 19 3705-4996 apon...@cpqd.com.br apo...@cpqd.com.br www.cpqd.com.br ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [OpenStack]Instances are running, but they cannot be pinged.
Hi! Which one hypervisor are you using? Also cloud you check nova-compute.log? 27 декабря 2011 г. 18:29 пользователь Alisson Soares Limeira Pontes apon...@cpqd.com.br написал: Hi. What are your images types? I had this problem with raw and qcow2 images. AMI images work fine for me. qcow2 does not work and raw images worked in a first time and no more. Have you checked your log files? 2011/12/27 Xuyun Zhang xyzhan...@gmail.com Hi folks, It appears that I have successfully run my instances with the 'running' status. However, I can't ping to the instance and get the console output. I have authorized the ping and ssh. There is no directory like /var/lib/nova/instance/instance-/ So I guess the instances actually have terminated. What's the possible causes? Are there any guys who had the same experience? Your information will be highly appreciated. Regards, Sean ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Alisson Pontes __ Network Technology Evolution Researcher CPqD - Center for Research and Development in Telecommunications Tel.: +55 19 3705-4996 apon...@cpqd.com.br apo...@cpqd.com.br www.cpqd.com.br ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] Automatically confirmed after 24 hours on Resize API
I'm more inclined to not call this a doc bug. There isn't anything wrong with the docs, we just have an incomplete implementation. Brian On Dec 27, 2011, at 11:10 AM, Anne Gentle wrote: Let's call it a doc bug - although that doc is a spec to indicate how the api should work. Still, we need to track this type of discrepancy so that we can be accurate on the API site. I can't log it easily this week (on vacay with only my cell phone) but I please log it on Openstack-manuals with a compute-API tag. Thanks, Anne Gentle Content Stacker a...@openstack.org On Dec 27, 2011, at 7:48 AM, Brian Waldon brian.wal...@rackspace.com wrote: Hi Nachi! You are 100% correct, we have not yet implemented that in Nova. I don't see any bugs/blueprints referencing this, so maybe if one was created we could make sure it gets done. Thanks! Brian On Dec 26, 2011, at 11:48 PM, Nachi Ueno wrote: Hi folks The doc says *All resizes are automatically confirmed after 24 hours if they are not explicitly confirmed or reverted*, but I couldn't found such implementations. Is this a bug of Nova? or Is this a bug of doc? The resize function converts an existing server to a different flavor, in essence, scaling the server up or down. The original server is saved for a period of time to allow rollback if there is a problem. All resizes should be tested and explicitly confirmed, at which time the original server is removed. *All resizes are automatically confirmed after 24 hours if they are not explicitly confirmed or reverted*. http://docs.openstack.org/api/openstack-compute/1.1/content/Resize_Server-d1e3707.html Cheers Nachi Ueno ___ 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] Automatically confirmed after 24 hours on Resize API
I'm with Waldon on this. This is a spec...the implementation hasnt caught up. Sent from my Motorola Smartphone on the Now Network from Sprint! -Original message- From: Brian Waldon brian.wal...@rackspace.com To: Anne Gentle annegen...@justwriteclick.com Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net Sent: Tue, Dec 27, 2011 10:20:30 CST Subject: Re: [Openstack] Automatically confirmed after 24 hours on Resize API I'm more inclined to not call this a doc bug. There isn't anything wrong with the docs, we just have an incomplete implementation. Brian On Dec 27, 2011, at 11:10 AM, Anne Gentle wrote: Let's call it a doc bug - although that doc is a spec to indicate how the api should work. Still, we need to track this type of discrepancy so that we can be accurate on the API site. I can't log it easily this week (on vacay with only my cell phone) but I please log it on Openstack-manuals with a compute-API tag. Thanks, Anne Gentle Content Stacker a...@openstack.org On Dec 27, 2011, at 7:48 AM, Brian Waldon brian.wal...@rackspace.com wrote: Hi Nachi! You are 100% correct, we have not yet implemented that in Nova. I don't see any bugs/blueprints referencing this, so maybe if one was created we could make sure it gets done. Thanks! Brian On Dec 26, 2011, at 11:48 PM, Nachi Ueno wrote: Hi folks The doc says *All resizes are automatically confirmed after 24 hours if they are not explicitly confirmed or reverted*, but I couldn't found such implementations. Is this a bug of Nova? or Is this a bug of doc? The resize function converts an existing server to a different flavor, in essence, scaling the server up or down. The original server is saved for a period of time to allow rollback if there is a problem. All resizes should be tested and explicitly confirmed, at which time the original server is removed. *All resizes are automatically confirmed after 24 hours if they are not explicitly confirmed or reverted*. http://docs.openstack.org/api/openstack-compute/1.1/content/Resize_Server-d1e3707.html Cheers Nachi Ueno ___ 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 ___ 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] dashboard image page throws 500 page
Hi! Please log potential bugs to the appropriate project on Launchpad. In this case, the project is Horizone (the Dashboard): https://bugs.launchpad.net/horizon/+filebug Cheers! -jay 2011/12/20 シ傻そ銘..(.。o 0 O泡泡) 501640...@qq.com: dashboard image page throws 500 page when I go into page http://localhost/syspanel/images/,It just throws OpenStack Dashboard NOT _LOGGED_IN_TOPBAR as Available Tenants Sign Out Internal Server Error An unexpected error occurred while processing your request. Please try your request again. I think it would be because I can't pass the authorization of glance ,But I don't know how and where to set it correct.. Thx and waitting for you help. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Automatically confirmed after 24 hours on Resize API
Hi Nachi! You are 100% correct, we have not yet implemented that in Nova. I don't see any bugs/blueprints referencing this, so maybe if one was created we could make sure it gets done. Thanks! Brian On Dec 26, 2011, at 11:48 PM, Nachi Ueno wrote: Hi folks The doc says *All resizes are automatically confirmed after 24 hours if they are not explicitly confirmed or reverted*, but I couldn't found such implementations. Is this a bug of Nova? or Is this a bug of doc? The resize function converts an existing server to a different flavor, in essence, scaling the server up or down. The original server is saved for a period of time to allow rollback if there is a problem. All resizes should be tested and explicitly confirmed, at which time the original server is removed. *All resizes are automatically confirmed after 24 hours if they are not explicitly confirmed or reverted*. http://docs.openstack.org/api/openstack-compute/1.1/content/Resize_Server-d1e3707.html Cheers Nachi Ueno ___ 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] Multinode installation (with devstack on the master)
Hi, I'm planning to perform a 5 node installation of openstack with the first node being the master and the rest being compute nodes. I have the following setup: Master node: eth0: 10.2.0.1 (public ip) eth1: 192.168.2.1 (private ip) Will use devstack to deploy openstack on this node Compute nodes: eth0: will not be used eth1: 192.168.2.2 - 192.168.2.5 (private ips) Will run 'apt-get install nova-compute' alone I'm using ubuntu 11.10 (oneiric). With the above setup, what should be the contents of nova.conf on the compute nodes? Should I specify anything particular in localrc before installing devstack? Is it possible to get openstack running and working with this setup? Thanks in advance for your suggestions. Regards, Sagar ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] git-review ready for general use
Hey guys, We've been having various people test the new git-review tool for a while now, and believe that it is ready for prime time as a replacement for the git review alias and tools/rfc.sh. We've also sent an email to our fine friends at glusterfs (from whom we got rfc.sh in the first place) and at gerrit to announce the tool to them. We're going to start a phased approach of rolling this out. Phase 1 - Get everyone to install git-review. Phase 2 - Add a deprecation warning message to tools/rfc.sh to catch stragglers. Phase 3 - Remove tools/rfc.sh from the repos. The only phase there that you need to really worry with is Phase 1 - because that's the one in which you install the tool. It's really quite easy. It works like this: 'sudo pip install git-review' And just go on about your day. When you run 'git review' to submit changes to gerrit, the git-review program will take precedence and do all of the appropriate things. There is a README file at https://github.com/openstack-ci/git-review with more information for those who care. However, notable features which were lacking with rfc.sh: git review -v prints out all of the git commands that are being run, for those who are interested in that sort of thing git review $branch_name will submit reviews to branches that are not master git review -d $review_number will download the code for a gerrit review into a local branch Enjoy! Monty PS. Not that there are any bugs, but git-review is managed via the same process as all other openstack code - so bugs can be filed at bugs.launchpad.net/git-review and patches are accepted via gerrit. You can submit them using git review. :) PPS. If you want, after installing git-review, you can remove the review alias from ~/.gitconfig. It's not necessary, as the git-review executable does take precedence. ___ 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] quantum error (essex-2)
2011/12/21 darkfower atk...@gmail.com: hi, bard: no , i exec quantum-server of the quantum-e2 version, but i see quantum is stable/diablo in the horizon/openstack-dashboard/tools/src/quantum. why ? Because interdependencies between projects is HARD :) Basically, Horizon is choosing to code its interfaces to Quantum based on the Diablo/stable branch of Quantum, to avoid any possible problems with trying to keep Horizon updated to the latest Quantum API changes. We do a similar thing in Glance for Keystone (see our pip-requires. we have a specific changeset/SHA1 hash of Keystone that we target in order to have some level of sanity in our development environments). After E3, when projects start to focus less on features and have a more stable trunk (stable in regards to API changes), then you will see projects update their pip-requires to point to more recent versions of dependent OpenStack projects. Cheers! -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] Multinode installation (with devstack on the master)
It sounds like you are trying to use devstack for a production install, this is not recommended. As the name implies, devstack is for a development rather than production install of OpenStack.. You would be better off using either the native Ubuntu packages (unless you plan on using keystone or horizon/dashboard[1]) or 3rd party or DIY native packages.. I've created updated packages based on the Ubuntu ones that work for all services, and scripted the install along the lines of devstack if they are of any use to you, I keep them relatively up to date with the latest diablo bug files: Packages @ https://launchpad.net/~managedit/+archive/openstack Scripts @ https://github.com/managedit/openstack-setup Note 1: The Oneiric keystone/dashboard packages do not currently work. The Ubuntu guys are working to fix this, but I don't believe the fixed packages have landed yet. Some of them are on this list, they can correct me if I'm wrong, or maybe provide an ETA. To reiterate: If you do not plan to use keystone/dashboard, then the stock Ubuntu Oneiric packages are fine. Thanks, Kiall On Tue, Dec 27, 2011 at 12:49 PM, Frost Dragon frostdragon...@gmail.comwrote: Hi, I'm planning to perform a 5 node installation of openstack with the first node being the master and the rest being compute nodes. I have the following setup: Master node: eth0: 10.2.0.1 (public ip) eth1: 192.168.2.1 (private ip) Will use devstack to deploy openstack on this node Compute nodes: eth0: will not be used eth1: 192.168.2.2 - 192.168.2.5 (private ips) Will run 'apt-get install nova-compute' alone I'm using ubuntu 11.10 (oneiric). With the above setup, what should be the contents of nova.conf on the compute nodes? Should I specify anything particular in localrc before installing devstack? Is it possible to get openstack running and working with this setup? Thanks in advance for your suggestions. Regards, Sagar ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Compute API Versioning
On Wed, 2011-12-21 at 11:41 -0600, Bryan Taylor wrote: I would suggest taking at least learning something from libtool. libtool does this stuff really well if you pay attention to the rules. They are as follows: Libtool is not a web service API. I don't see the analogy here. It's a fine tool for what it does - encapsulating shared software libraries. No, it isn't. But the point is that it does *API* versioning, not code versioning. The docs actually tell you that if you want to lock your API versioning to your code versioning, you're doing it wrong (though they also tell you how, and tell you what will break if you do). That said, it's hard for me to see how we could effectively communicate current and age to clients. (revision doesn't really have a place, except possibly advertising that certain bugs got fixed…) -- 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] Multinode installation (with devstack on the master)
Devstack isn't for production. I recommend using packages (even if they are your own). repeat: WHAT FOLLOWS IS NOT FOR PRODUCTION! If you are just experimenting with a multi-node dev deploy - you can set a few options in your nova.conf: --sql_connection=mysql://$MYSQL_USER:$PASS@$MASTER_IP/nova --rabbit_host=$MASTER_IP --rabbit_password=$RABBIT_PASS --glance_api_servers=$MASTER_IP:9292 My team (creators of devstack) do a multi-node devstack deploys every day (for development - for production we use crowbar/chef, ubuntu, and package) With devstack on multiple nodes you can create a localrc how you normally would then add: master node: you need all the services ENABLED_SERVICES=n-vol,g-api,g-reg,key,n-api,n-cpu,n-net,n-sch,n-vnc,horizon,mysql,rabbit,swift,openstackx child nodes: you only need the workers MYSQL_HOST=$MASTER_IP RABBIT_HOST=$MASTER_IP GLANCE_HOSTPORT=$MASTER_IP:9292 ENABLED_SERVICES=n-vol,n-cpu,n-net,n-api notes: * we run n-api on each node to provide the metadata service (you can also setup iptables routes to forward requests to the metadata service to the main nova-api node). We plan on switching to https://github.com/openstack/nova/blob/master/bin/nova-api-metadata on the child nodes. * we use --network_manager=nova.network.manager.FlatDHCPManager with --force_dhcp_release --multi_host and --send_arp_for_ha On Tue, Dec 27, 2011 at 10:05 AM, Kiall Mac Innes ki...@managedit.ie wrote: It sounds like you are trying to use devstack for a production install, this is not recommended. As the name implies, devstack is for a development rather than production install of OpenStack.. You would be better off using either the native Ubuntu packages (unless you plan on using keystone or horizon/dashboard[1]) or 3rd party or DIY native packages.. I've created updated packages based on the Ubuntu ones that work for all services, and scripted the install along the lines of devstack if they are of any use to you, I keep them relatively up to date with the latest diablo bug files: Packages @ https://launchpad.net/~managedit/+archive/openstack Scripts @ https://github.com/managedit/openstack-setup Note 1: The Oneiric keystone/dashboard packages do not currently work. The Ubuntu guys are working to fix this, but I don't believe the fixed packages have landed yet. Some of them are on this list, they can correct me if I'm wrong, or maybe provide an ETA. To reiterate: If you do not plan to use keystone/dashboard, then the stock Ubuntu Oneiric packages are fine. Thanks, Kiall On Tue, Dec 27, 2011 at 12:49 PM, Frost Dragon frostdragon...@gmail.com wrote: Hi, I'm planning to perform a 5 node installation of openstack with the first node being the master and the rest being compute nodes. I have the following setup: Master node: eth0: 10.2.0.1 (public ip) eth1: 192.168.2.1 (private ip) Will use devstack to deploy openstack on this node Compute nodes: eth0: will not be used eth1: 192.168.2.2 - 192.168.2.5 (private ips) Will run 'apt-get install nova-compute' alone I'm using ubuntu 11.10 (oneiric). With the above setup, what should be the contents of nova.conf on the compute nodes? Should I specify anything particular in localrc before installing devstack? Is it possible to get openstack running and working with this setup? Thanks in advance for your suggestions. Regards, Sagar ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] Configure Rate limits on OS API
You can configure those values thru the paste conf. [filter:ratelimit] paste.filter_factory = nova.api.openstack.limits:RateLimitingMiddleware.factory limits =(POST, *, .*, 10, MINUTE);(POST, */servers, ^/servers, 50, DAY);(PUT, *, .*, 10, MINUTE);(GET, *changes-since*, .*changes-since.*, 3, MINUTE);(DELETE, *, .*, 100, MINUTE) On Mon, Dec 19, 2011 at 1:28 PM, Day, Phil philip@hp.com wrote: Hi Folks, ** ** Is there a file that can be used to configure the API rate limits for the OS API on a per user basis ? ** ** I can see where the default values are set in the code, but it looks as if there should be a less brutal configuration mechanism to go along with this ? ** ** Thanks Phil ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Nirmal http://rnirmal.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] swift enforcing ssl?
Does the swift proxy enforce SSL connections if it's configured with a cert/key file? Or is it assumed that there's an external entity performing that? ___ 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] Gerrit Workflow Changes
cor...@inaugust.com (James E. Blair) writes: Hi, Monty and I have been working on a solution to a number of problems and suggested enhancements to Gerrit. In short, we're planning on adding a new review type to Gerrit so that a core reviewer can specifically mark a review as Approved for Jenkins to test and merge. This will end our overloading of the +2 code review for that purpose. We're planning on upgrading Jenkins and making these changes on Tuesday, December 27th. This work is complete. Here's what you (particularly core reviewers) need to know about reviewing changes: * Code review +2 votes will no longer trigger Jenkins. * Core reviewers may now feel free to vote with any value between -2 and +2 on any change. They should vote +2 if they want their vote to be counted as meeting the inclusion criteria of positive reviews from at least 2 core developers. Such votes from core reviewers are now easily visible on the review page. * To approve a change and start the merge process, core reviewers should vote +1 in the Approved category (click the review button again, and only change the value for the Approved category). * Core reviewers should periodically scan for reviews that are ready for approval and approve them if they feel they have been sufficiently reviewed and the inclusion criteria are met. * There is a new column, labeled A, on all the pages where changes are listed that corresponds to the Approved category (V and R are Verified and Code Review respectively). That should help make visible reviews that have at least one core reviewer but haven't yet been approved. Here is an example of what the votes for a review should look like now; this review has 2 reviews from core reviewers, was then approved, and then Jenkins verified the change and merged it: https://review.openstack.org/#change,2287 Please contact me (jeblair) or Monty (mtaylor) on IRC if you run into a problem or need any help with the new process. Thanks, Jim ___ 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] how to re-attach volume after vm and host down unexpectedly
I have write a blog about re-attach http://livemoon.dyndns.org/life/2011/12/how-to-re-attach-volume-in-openstack-if-vm-down-since-of-host-down.html I think my way is stupid . Better way should exists. The case is: The vm using volume, and then host where vm is runnning down because some reason. After host up, we can reboot vm using nova reboot server, but the disk(filesystem mounted) in vm will be lost. In novaclient, using nova volume-list, it show volume status is still in-used by this vm. At first, I want to detach it and re-attach it again. This way can work if we reboot vm in normal(host not down unexpectedly), but now it will show error like this: * * *2011-12-28 14:30:08,269 AUDIT nova.compute.manager [661dae13-05ec-4365-9f44-15d9072e000a admin 1] Detach volume 6 from mountpoint /dev/vdb on instance 74* *(nova.rpc): TRACE: DiskNotFound: No disk at vdb* I don't know how to write vdb to somewhere. But I think I can clear the database about it. So following steps I do: - update nova database, volumes table, found this vm, set mountpoint to NULL, set status='available' , set attach_status='detach' - logout iscsi volume in host where vm running, like this: $ sudo iscsiadm -m node -T iqn.2010-10.org.openstack:volume-0006 -p 10.200.200.5:23260 --logout - attach volume again using nova volume-attach server volume /dev/vdb It can work, but I want to know , is this way correct ? -- 非淡薄无以明志，非宁静无以致远 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack-poc] [Question #181560]: Multi node nova installation
Question #181560 on OpenStack Compute (nova) changed: https://answers.launchpad.net/nova/+question/181560 Status: Open = Expired Launchpad Janitor expired the question: This question was expired because it remained in the 'Open' state without activity for the last 15 days. -- You received this question notification because you are a direct subscriber of the question. ___ Mailing list: https://launchpad.net/~openstack-poc Post to : openstack-poc@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
Re: [Openstack-volume] [Question #181560]: Multi node nova installation
Question #181560 on OpenStack Compute (nova) changed: https://answers.launchpad.net/nova/+question/181560 Status: Open = Expired Launchpad Janitor expired the question: This question was expired because it remained in the 'Open' state without activity for the last 15 days. -- You received this question notification because you are a direct subscriber of the question. -- Mailing list: https://launchpad.net/~openstack-volume Post to : openstack-volume@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-volume More help : https://help.launchpad.net/ListHelp
