On Tue, 2010-10-26 at 14:11 +0200, [email protected] wrote:
> From: Ladislav Martincik <[email protected]>
> 
> ---
>  src/app/models/user.rb                         |    2 +-
>  src/app/services/registration_service.rb       |   45 ++++++------
>  src/spec/factories/metadata_object.rb          |   20 +++++-
>  src/spec/factories/role.rb                     |    4 +
>  src/spec/services/registration_service_spec.rb |   87 
> ++++++++++++++++++++++++
>  5 files changed, 133 insertions(+), 25 deletions(-)
>  create mode 100644 src/spec/factories/role.rb
>  create mode 100644 src/spec/services/registration_service_spec.rb
> 
In testing this, the quota usage still does seem to be updated with this
patch applied.  Now, I could have done something wrong here (I can test
tomorrow with a full setup pushing actual instances to ec2), but I
applied this on top of Jan's patch to set the correct user as owner for
an instance.  It appears that the quota is being set correctly, however,
it does not appear to be enforced, so I think only half of the problem
has been solved with this patch.  IOW, I can launch 3 instances with a
quota of 2 for that user, and the instance page will happily show 150%
quota usage.

If this is not the behavior you experienced, I will apply it to a full
end-to-end test in the morning, rather than updating state in the rails
console, in case there is some other place the quota is being enforced
that I have bypassed by doing it this way (condor, I'm looking at
you).  
A quick look at condormatic just now tells me this may be the case, but
I am not doing another full test right now - just wanted you to know
someone had looked at this today.

-j

_______________________________________________
deltacloud-devel mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/deltacloud-devel

Reply via email to