hit OpenStack quota limits
Bug #1366027 reported by
Dustin Kirkland
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloudfoundry |
New
|
Undecided
|
Unassigned | ||
| juju-core |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
Not sure where this bug will be triaged ultimately (OpenStack, Juju, CloudFoundry charms), but filing it now anyway...
When deploying the CloudFoundry charm via Juju on top of OpenStack, it fails, due to exhausted resource limits.
Specifically, a user is limited to 10 Security Groups. It seems that Juju (or the charm) blew through this limit very quickly, and the deploy failed.
At this point, I entered the Horizon GUI and increased all limits by a factor of 10 (probably overkill, but it was already annoying to have to destroy my environment and restart this *very* long running deploy).
| Changed in juju-core: | |
| status: | New → Triaged |
| tags: | added: feature openstack-provider |
| Changed in juju-core: | |
| importance: | Undecided → Low |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #1 |
| Changed in juju-core: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
It might be possible for juju to query openstack to learn the quotas, and refuse actions that will exceed those quotas. For example, we know deploying a service without specifying a machine will create a new instance and use a security group. it may even use a floating IP. Juju could warn that the action cannot be completed because of limits.
juju cannot know about what a charm is doing so there could be cases where the charm is exceeding limits.