Re: [openstack-dev] [nova] nova default quotas
Hi Kieran, What do you think about the approach proposed in https://review.openstack.org/#/c/94519/ ? What we are trying to do is to simplify the way to manage default quotas through an API and keeping backward compatibility. So doing this is not needed to restart any service once a default quota is changed, something that could be painful when there are many services running in parallel. From: Kieran Spear [mailto:kisp...@gmail.com] Sent: Wednesday, May 28, 2014 2:05 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova] nova default quotas Hi Joe, On 28/05/2014, at 11:21 AM, Joe Gordon joe.gord...@gmail.com wrote: On Tue, May 27, 2014 at 1:30 PM, Kieran Spear kisp...@gmail.com wrote: On 28/05/2014, at 6:11 AM, Vishvananda Ishaya vishvana...@gmail.com wrote: Phil, You are correct and this seems to be an error. I don't think in the earlier ML thread[1] that anyone remembered that the quota classes were being used for default quotas. IMO we need to revert this removal as we (accidentally) removed a Havana feature with no notification to the community. I've reactivated a bug[2] and marked it critical. +1. We rely on this to set the default quotas in our cloud. Hi Kieran, Can you elaborate on this point. Do you actually use the full quota-class functionality that allows for quota classes, if so what provides the quota classes? If you only use this for setting the default quotas, why do you prefer the API and not setting the config file? We just need the defaults. My comment was more to indicate that yes, this is being used by people. I'm sure we could switch to using the config file, and generally I prefer to keep configuration in code, but finding out about this half way through a release cycle isn't ideal. I notice that only the API has been removed in Icehouse, so I'm assuming the impact is limited to *changing* the defaults, which we don't do often. I was initially worried that after upgrading to Icehouse we'd be left with either no quotas or whatever the config file defaults are, but it looks like this isn't the case. Unfortunately the API removal in Nova was followed by similar changes in novaclient and Horizon, so fixing Icehouse at this point is probably going to be difficult. Cheers, Kieran Kieran Vish [1] http://lists.openstack.org/pipermail/openstack-dev/2014-February/027574.html [2] https://bugs.launchpad.net/nova/+bug/1299517 On May 27, 2014, at 12:19 PM, Day, Phil philip@hp.com wrote: Hi Vish, I think quota classes have been removed from Nova now. Phil Sent from Samsung Mobile Original message From: Vishvananda Ishaya Date:27/05/2014 19:24 (GMT+00:00) To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova] nova default quotas Are you aware that there is already a way to do this through the cli using quota-class-update? http://docs.openstack.org/user-guide-admin/content/cli_set_quotas.html (near the bottom) Are you suggesting that we also add the ability to use just regular quota-update? I'm not sure i see the need for both. Vish On May 20, 2014, at 9:52 AM, Cazzolato, Sergio J sergio.j.cazzol...@intel.com wrote: I would to hear your thoughts about an idea to add a way to manage the default quota values through the API. The idea is to use the current quota api, but sending ''default' instead of the tenant_id. This change would apply to quota-show and quota-update methods. This approach will help to simplify the implementation of another blueprint named per-flavor-quotas Feedback? Suggestions? Sergio Juan Cazzolato Intel Software Argentina ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] nova default quotas
I have created a blueprint to add this functionality to nova. https://review.openstack.org/#/c/94519/ -Original Message- From: Vishvananda Ishaya [mailto:vishvana...@gmail.com] Sent: Tuesday, May 27, 2014 5:11 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova] nova default quotas Phil, You are correct and this seems to be an error. I don't think in the earlier ML thread[1] that anyone remembered that the quota classes were being used for default quotas. IMO we need to revert this removal as we (accidentally) removed a Havana feature with no notification to the community. I've reactivated a bug[2] and marked it critcal. Vish [1] http://lists.openstack.org/pipermail/openstack-dev/2014-February/027574.html [2] https://bugs.launchpad.net/nova/+bug/1299517 On May 27, 2014, at 12:19 PM, Day, Phil philip@hp.com wrote: Hi Vish, I think quota classes have been removed from Nova now. Phil Sent from Samsung Mobile Original message From: Vishvananda Ishaya Date:27/05/2014 19:24 (GMT+00:00) To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova] nova default quotas Are you aware that there is already a way to do this through the cli using quota-class-update? http://docs.openstack.org/user-guide-admin/content/cli_set_quotas.html (near the bottom) Are you suggesting that we also add the ability to use just regular quota-update? I'm not sure i see the need for both. Vish On May 20, 2014, at 9:52 AM, Cazzolato, Sergio J sergio.j.cazzol...@intel.com wrote: I would to hear your thoughts about an idea to add a way to manage the default quota values through the API. The idea is to use the current quota api, but sending ''default' instead of the tenant_id. This change would apply to quota-show and quota-update methods. This approach will help to simplify the implementation of another blueprint named per-flavor-quotas Feedback? Suggestions? Sergio Juan Cazzolato Intel Software Argentina ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] nova default quotas
I would to hear your thoughts about an idea to add a way to manage the default quota values through the API. The idea is to use the current quota api, but sending ''default' instead of the tenant_id. This change would apply to quota-show and quota-update methods. This approach will help to simplify the implementation of another blueprint named per-flavor-quotas Feedback? Suggestions? Sergio Juan Cazzolato Intel Software Argentina ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder] cinder not support quota for user
There is a blueprint to add this to cinder https://blueprints.launchpad.net/cinder/+spec/per-project-user-quotas-support It has been implemented and then rejected due to there are some issues around the current quota implementation to be fixed before introduce this new feature. From: Harshada Kakad [mailto:harshada.ka...@izeltech.com] Sent: Friday, April 25, 2014 8:28 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [cinder] cinder not support quota for user Hi Everyone, I see most of the project allows quota for tenant as well as user. Here is example of nova supporting quota for both tenant and user. ubuntu@harshada-dev:~/harshada/temp/cinder$ nova help quota-show usage: nova quota-show [--tenant tenant-id] [--user user-id] List the quotas for a tenant/user. Optional arguments: --tenant tenant-id ID of tenant to list the quotas for. --user user-id ID of user to list the quotas for. But cinder allows quota for just tenant only. Why is it so designed, I am actually not aware about it. Ideally it show also allow quota for user. Could any one let me know why is it so designed only for tenant and not for user? ubuntu@harshada-dev:~/harshada/temp/cinder$ cinder help quota-show usage: cinder quota-show tenant_id List the quotas for a tenant. Positional arguments: tenant_id UUID of tenant to list the quotas for. -- Regards, Harshada Kakad Sr. Software Engineer C3/101, Saudamini Complex, Right Bhusari Colony, Paud Road, Pune - 411013, India Mobile-9689187388 Email-Id : harshada.ka...@izeltech.com website : www.izeltech.com *Disclaimer* The information contained in this e-mail and any attachment(s) to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information of Izel Technologies Pvt. Ltd. If you are not the intended recipient, you are notified that any review, use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail message, contents or its attachment(s) is strictly prohibited and you are requested to notify us the same immediately by e-mail and delete this mail immediately. Izel Technologies Pvt. Ltd accepts no liability for virus infected e-mail or errors or omissions or consequences which may arise as a result of this e-mail transmission. *End of Disclaimer* ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Openstack-operators] Quota Templates
Adding the dev list. I would to see also the devs opinion in this blueprint, we need to discuss the approach for this. https://review.openstack.org/#/c/84432/9 -Original Message- From: Cazzolato, Sergio J Sent: Wednesday, April 16, 2014 5:47 PM To: Cazzolato, Sergio J; James Penick; Tim Bell; Narayan Desai; Jay Pipes Cc: openstack-operat...@lists.openstack.org Subject: RE: [Openstack-operators] Quota Templates I would to see the operators opinion in this blueprint, we need to understand if it is useful or it is confusing for you. https://review.openstack.org/#/c/84432/9 -Original Message- From: Cazzolato, Sergio J [mailto:sergio.j.cazzol...@intel.com] Sent: Friday, April 11, 2014 12:38 PM To: James Penick; Tim Bell; Narayan Desai; Jay Pipes Cc: openstack-operat...@lists.openstack.org Subject: Re: [Openstack-operators] Quota Templates Thanks James! I think we will need some help for code review and to test this in a real cluster. -Original Message- From: James Penick [mailto:pen...@yahoo-inc.com] Sent: Thursday, April 10, 2014 2:44 PM To: Cazzolato, Sergio J; Tim Bell; Narayan Desai; Jay Pipes Cc: openstack-operat...@lists.openstack.org Subject: Re: [Openstack-operators] Quota Templates This certainly covers our immediate needs. Longer term we should consider how to cascade this concept through cells, and allow someone to have a quota for a given flavor in a given cell type. For example, I may allow them 100 m1.medium flavors in a 0 over provisioning cell, but 500 in a highly over provisioned cell. Something to consider. That said, there are some dev resources that we have available to us. Want some help getting this in? -James :)= On 4/9/14, 2:17 PM, Cazzolato, Sergio J sergio.j.cazzol...@intel.com wrote: So far the plan is to make it by project/user. The idea for the flavor quotas is that could be used combined with other resources or alone. Example: Suppose this scenario: . flavor medium has 2 cores and 4GB ram . flavor large has 4 cores and 8GB ram Today we can assign in this way the quotas per user: . Instances: 4 . Cores: 8 . Ram: 16GB Through this feature: . flavor medium: 4 Or . flavor large: 2 Or . flavor medium: 2 . flavor large: 1 Or .flavor medium: 4 . Instances: 4 . Cores: 8 . Ram: 16GB So, In case the quotas for a user is flavor_medium: 4 The idea is that when the user creates a machine and it is based on a flavor medium, if the user has already created 4 machines the system will not allow this, otherwise it will allow it. And in case the user wants to create a large one, the system will deny that. Does it make sense? Do you think it is enough to cover the scenarios for specific hardware as you mention in previous emails? From: Tim Bell [mailto:tim.b...@cern.ch] Sent: Wednesday, April 09, 2014 5:16 PM To: Cazzolato, Sergio J; James Penick; Narayan Desai; Jay Pipes Cc: openstack-operat...@lists.openstack.org Subject: RE: [Openstack-operators] Quota Templates Addressing all of CERN’s needs would be a big patch ☺ I can see a few scenarios which may be overlapping The quota for a project should be (optionally) set such that the number of a particular flavour is limited. Examples would be very large VMs or flavors which match specific aggregates on a different allocation scheme. Can you clarify the scope of the quota ? Are we setting it per user, per group (with Keystone V3 this is supported) and/or per project ? Tim From: Cazzolato, Sergio J [mailto:sergio.j.cazzol...@intel.com] Sent: 09 April 2014 21:28 To: James Penick; Tim Bell; Narayan Desai; Jay Pipes Cc: openstack-operat...@lists.openstack.org Subject: RE: [Openstack-operators] Quota Templates Hi James, thanks for sharing with us. I am working in the blueprint “per-flavor-quotas” and I would to know based on your datacenter needs, if this feature is covering all the problems you have regarding this topic? Or we should complement that with something else? https://review.openstack.org/#/c/84432/7 Thanks From: James Penick [mailto:pen...@yahoo-inc.com] Sent: Tuesday, April 08, 2014 6:37 PM To: Tim Bell; Narayan Desai; Jay Pipes Cc: openstack-operat...@lists.openstack.org Subject: Re: [Openstack-operators] Quota Templates This all seems to be going in a great direction. One of the things I’ve been working on at Yahoo is integrating Openstack VMs and Bare metal into our larger finance process. We have a couple interesting problems presented by the current quota management system. When one of our Projects on our internal cloud wants to increase their quota they’ll need to file a request. That request will be compared against projected cluster capacity as well as certain financial models. If the request falls within certain parameters it’ll need larger finance approval before the quota can be allocated. There are a number of capacity folks who would be handling these requests, so there could be a race condition when multiple Projects request
[openstack-dev] Quota Management
Hi All, I'd like to know your thoughts regarding Quota Management... I've been contributing to this topic for icehouse and noticed some issues and discussions around its implementation like code is duplicated, synch problems with database, not having an homogeneous logic, etc... so I was thinking that maybe a centralized implementation could be a solution for this... As far as I know there was a discussion during the last summit and the decision was to use Keystone for a Centralized Quota Management solution but I don't have the details on that discussion... Also I was looking at Boson (https://wiki.openstack.org/wiki/Boson) that seems to be a nice solution for this and also addresses the scenario where Nova is deployed in a multi-cell manner and some other interesting things. Sergio ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Quota Management
Jay, thanks for taking ownership on this idea, we are really interested to contribute to this, so what do you think are the next steps to move on? Please let me know whatever you need to accelerate on this. Sergio Cazzolato -Original Message- From: Kevin L. Mitchell [mailto:kevin.mitch...@rackspace.com] Sent: Thursday, April 03, 2014 3:13 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] Quota Management On Thu, 2014-04-03 at 10:54 -0700, Jay Pipes wrote: On Thu, 2014-04-03 at 12:13 -0500, Kevin L. Mitchell wrote: On Thu, 2014-04-03 at 09:22 -0700, Jay Pipes wrote: Boson does indeed look interesting, but who is working on it, if anyone at this point? I agree that having a centralized quota management system makes sense, in order to make the handling of quotas and reservations consistent across projects as well as to deal with global quota management properly (i.e. quotas that span multiple cells/AZs) At present, no one is really working on Boson. The CERN folks were interested in it, but I wasn't able to free up the time I would have needed to actually develop on it, partly because of lack of interest from the rest of the community at the time. I'd say that, currently, Boson is facing the chicken-and-egg problem—no one works on it because no one is working on it. I would personally be interested in picking up the work. Kevin, any issues with me moving the code on your GitHub repo into stackforge and linking up the upstream CI harness? None at all; please do so! :) -- Kevin L. Mitchell kevin.mitch...@rackspace.com Rackspace ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Quota Management
+1 -Original Message- From: Kevin L. Mitchell [mailto:kevin.mitch...@rackspace.com] Sent: Thursday, April 03, 2014 4:42 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] Quota Management On Thu, 2014-04-03 at 19:16 +, Cazzolato, Sergio J wrote: Jay, thanks for taking ownership on this idea, we are really interested to contribute to this, so what do you think are the next steps to move on? Perhaps a summit session on quota management would be in order? -- Kevin L. Mitchell kevin.mitch...@rackspace.com Rackspace ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Quota Management
Glad to see that, for sure I'll participate of this session. Thanks -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: Thursday, April 03, 2014 7:21 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] Quota Management On Thu, 2014-04-03 at 14:41 -0500, Kevin L. Mitchell wrote: On Thu, 2014-04-03 at 19:16 +, Cazzolato, Sergio J wrote: Jay, thanks for taking ownership on this idea, we are really interested to contribute to this, so what do you think are the next steps to move on? Perhaps a summit session on quota management would be in order? Done: http://summit.openstack.org/cfp/details/221 Best, -jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] nova-api fails to start
Hi, I had the same issue and fixed that doing a chwon and changing the
ownership to my user of the files in /etc/nova where the owner was the user
nova.
In my case the files were: api-paste.ini and policy.json
I posted the solution there too:
http://stackoverflow.com/questions/19843239/getting-nova628die-trying-to-start-openstack-nova-module
Thanks
From: Krishanu Dhar [mailto:rony.k...@gmail.com]
Sent: Thursday, November 07, 2013 3:40 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] nova-api fails to start
Any other recommendations on how to have a successful devstack installation?
On Thu, Nov 7, 2013 at 11:37 PM, Krishanu Dhar
rony.k...@gmail.commailto:rony.k...@gmail.com wrote:
below is an error that's probably the cause...
2013-11-07 23:24:14.758 TRACE nova IOError: [Errno 13] Permission denied:
'/etc/nova/api-paste.ini'
2013-11-07 23:24:14.758 TRACE nova
n-api failed to start
krish@krish-VirtualBox:/opt/stack/nova$ ls -l /etc/nova/api-paste.ini
-rw--- 1 nova nova 4260 Apr 23 2013 /etc/nova/api-paste.ini
isn't it expected to fail if the file is owned by nova... weird.
On Thu, Nov 7, 2013 at 11:18 PM, Krishanu Dhar
rony.k...@gmail.commailto:rony.k...@gmail.com wrote:
it did not even start the process in my case.
I tried looking up email threads in google and looks like quite a few have run
into this before, but couldn't find a working fix.
On Thu, Nov 7, 2013 at 11:15 PM, Telles Nobrega
tellesnobr...@gmail.commailto:tellesnobr...@gmail.com wrote:
Weird, i had the same problem, but when i kill the processes it works
On Thu, Nov 7, 2013 at 2:34 PM, Krishanu Dhar
rony.k...@gmail.commailto:rony.k...@gmail.com wrote:
Nothing was left behind.
#ps aux|grep -ie nova did not return anything.
On Thu, Nov 7, 2013 at 11:01 PM, Telles Nobrega
tellesnobr...@gmail.commailto:tellesnobr...@gmail.com wrote:
Did you check if there are any nova process left running?
On Thu, Nov 7, 2013 at 2:28 PM, Krishanu Dhar
rony.k...@gmail.commailto:rony.k...@gmail.com wrote:
Appreciate the responses. But there is something wrong with this. I ran
unstack.sh again and retried the installation. it failed with the same message.
So, what are my options right now?
On Thu, Nov 7, 2013 at 7:31 PM, Telles Nobrega
tellesnobr...@gmail.commailto:tellesnobr...@gmail.com wrote:
Sometimes after ./unstack is ran, some process are still runnning for nova.
Try running this to kill them all (ps aux | grep -ie nova | awk '{print $2}' |
xargs kill -9) and try ./stack again
On Thu, Nov 7, 2013 at 9:14 AM, Noorul Islam K M
noo...@noorul.commailto:noo...@noorul.com wrote:
Krishanu Dhar rony.k...@gmail.commailto:rony.k...@gmail.com writes:
Hi,
I was trying to install the devstack and it failed while starting the nova
api. below is a snippet from the console. Is it a bug?
+ screen -S stack -p n-api -X stuff 'cd /opt/stack/nova
/usr/local/bin/nova-a'i || echo n-api failed to start | tee
/opt/stack/status/stack/n-api.failure
+ echo 'Waiting for nova-api to start...'
Waiting for nova-api to start...
+ wait_for_service 60 http://10.0.2.15:8774
+ local timeout=60
+ local url=http://10.0.2.15:8774
+ timeout 60 sh -c 'while ! curl --noproxy '\''*'\'' -s
http://10.0.2.15:8774 /dev/null; do sleep 1; done'
+ die 628 'nova-api did not start'
+ local exitcode=0
+ set +o xtrace
[Call Trace]
./stack.sh:1084:start_nova_api
/home/krish/devstack/lib/nova:628:die
[ERROR] /home/krish/devstack/lib/nova:628 nova-api did not start
krish@krish-VirtualBox:~/devstack$
Did you try screen -x stack ?
Regards,
Noorul
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
--
Telles Mota Vidal Nobrega
Developer at PulsarOpenStack Project - HP/LSD-UFCG
--
Krishanu
--
Krishanu
--
Krishanu
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
