Port quota padding - Githubissues

CCI-MOC / moc-openstack-tools

Tools for OpenStack administration, user/project management, etc.

Apache License 2.0

0 stars 8 forks source link

Port quota padding #97

Open ianballou opened 6 years ago

ianballou commented 6 years ago

In response to #91:

Port padding is introduced based off of (3 VM quota network quota) + 5.
Initial port quota is padded along with any quota increases.

ianballou commented 6 years ago

Looks like this is failing because of some unspecified except blocks in a couple other files. Those should probably fixed by excepting a specific error. Other than that, do folks think this solution I discussed with Rado is ok?

jeremyfreudberg commented 6 years ago

Looks ok to me. Assuming you've tested it. The quota audit script could also eventually be updated to reflect this.

ianballou commented 6 years ago

Thanks, I still need to test this out with Rado. Just wanted to check first that nothing was blatantly off.

ianballou commented 6 years ago

We've tested this now, and the port padding works fine.

ianballou commented 6 years ago

It seems that there might be some possibly unrelated issues with the port updates. If it's true then I'll close this for further investigation.

Edit: We realized that users have the option of inputting how many ports they want. Since the # of ports is behind-the-scenes to Kaizen users, they shouldn't be able to edit this. There is one recent account of a person requesting 20 ports and 20 VMs, but they ended up with 10 ports.

ianballou commented 6 years ago

Blocked until #102 is merged or until #103 is fixed.