Page MenuHomePhabricator

Requesting Trove quota for deployment-prep
Closed, ResolvedPublic

Description

Project Name: deployment-prep
Type of quota increase requested: Trove
Amount to increase: 2 instances, 2 vCPUs, 4 GB RAM, 2 GB storage space
Reason: experimenting with terraform's Postgres backend .

Side note, if there is a terraform user group at WMF, let me know! I'd love to join.

Event Timeline

+1

Side note, if there is a terraform user group at WMF, let me know! I'd love to join.

Not as far as I know, but I would also be interested :)

aborrero claimed this task.
aborrero added a subscriber: aborrero.

I think the project already had quotas for this, but anyway I set it to the requested values:

aborrero@cloudcontrol1006:~ $ sudo wmcs-openstack database quota show deployment-prep
+-----------+--------+----------+-------+
| Resource  | In Use | Reserved | Limit |
+-----------+--------+----------+-------+
| backups   |      0 |        0 |     2 |
| instances |      0 |        0 |     2 |
| ram       |      0 |        0 |     4 |
| volumes   |      0 |        0 |     2 |
+-----------+--------+----------+-------+

@aborrero sorry to bug again , but I'm getting the following error when I try to build 1G or 2G flavors:

Quota exceeded for resources: ['ram']. (HTTP 413)

It's OK not to spend much time on this. If it doesn't work, I'd be in favor of pursuing the Gitlab backend as mentioned in T318360 .

I cannot look into this right now but I'm reopening the task because I think it would be useful for us to understand why it's not working. It will probably be next week though.

I think we had a MB vs GB problem here. I've updated the docs, and adjusted the quotas again:

root@cloudcontrol1005:~# openstack database quota show deployment-prep
+-----------+--------+----------+-------+
| Resource  | In Use | Reserved | Limit |
+-----------+--------+----------+-------+
| backups   |      0 |        0 |     2 |
| instances |      0 |        0 |     2 |
| ram       |      0 |        0 |  4096 |
| volumes   |      0 |        0 |    20 |
+-----------+--------+----------+-------+

Please re-open if it still doesn't work!

Thanks @Andrew . I can send a build request now, but it goes into error immediately:

Failed to create User port for instance 9cc9f5b5-133e-4245-9723-4e55d4d40e35: Subnet a69bdfad-d7d2-4cfa-8231-3d6d3e0074c9 is not associated with router.

Looks like a neutron thing? This link should get you the full error message if you're already in the deployment-prep horizon project.

There was a known issue with new VM creation during the day (although it doesn't perfectly fit the error message you saw.) Can you try deleting and re-creating? It seems to be working for me right now.

Thanks again. The error was probably related to my checking the "public" box when building the instance (didn't actually want it to be public but was also afraid of default deny).

I was able to provision the instance, but cannot create databases. Error message is:

Operation not supported for datastore postgresql. (HTTP 422)

My instance is up here, feel free to add databases/users or anything needed for further troubleshooting.

I'm sorry to say that the actual db-management integration doesn't work very well with postgres, it's clear that the devs only test on mysql/mariadb. This is still useful, though, as the provisioning bits are adequately handled by Trove. Your remaining steps will have to happen via the psql interface -- iirc you can get a connection line from Horizon after you enable the root user.