Hey. I have two concerns in particular here that I'd like your input on:

• First, the project scope. As the description of Cloud-VPS (Project-requests) says, we prefer that projects are scoped to individual software projects, not groups of people working on them. So an "eseap" project for hosting an ESEAP hub landing page might be fine, having a project for anything certain people affiliated with that group is working on would not be. In particular, based on what I've heard and read elsewhere about that scholarship review app project, my understanding is that the plan is to make it useful also for projects not organized by the ESEAP Hub, so that should live in a different project.
• Second, duplication. The movement already has a Phorge instance (you're on it right now), why do you need to run your own? Similarly I'm curious what kind of content you're planning to host on the website and why that can't be done on Meta or some other wiki on the main wikifarm.

And finally a procedural note: This request is non-standard enough that I plan to take it up for discussion in the cloud-services-team weekly meeting instead of the usual async process.

Taavi,

Thanks for the response. Upon further discussions with Chlod, we would like to refine to the following: a project just for hosting eseap.org website.
We have not considered the main wikifarm primarily because we would likely be using something like WMAU skin if it is on MediaWiki and of course using the eseap.org domain, unless the main wikifarm can support both options.

For the scholarship app, we will request again a separate project when it closer to be used. For the phorge, we will request a separate space and project separately.

Again: What kind of content are you planning to host on the website?

@Aklapper: Tentatively: about us, projects we are working on, team(s) composition, contact us form. Admittedly the content can mostly be done on meta or the main wikifarm, but the key things are the skin and domain name.

We talked about this in the WMCS team meeting. We encourage you to take advantage of existing resources, but if you are aware of the extra effort and responsibilities self-managing brings then we are willing to create the project.

I am aware of the extra effort and responsibilities required to self manage and willing to take it up.

Likewise, I'm aware of the effort and responsibilities, and I'll help out with managing project resources.

group_199_bot_333a6c67971a471aeb1cf0b14ccf9f49 opened https://gitlab.wikimedia.org/repos/cloud/cloud-vps/tofu-infra/-/merge_requests/265

projects: added project eseap

raymond-ndibe merged https://gitlab.wikimedia.org/repos/cloud/cloud-vps/tofu-infra/-/merge_requests/265

projects: added project eseap

Mentioned in SAL (#wikimedia-cloud-feed) [2025-08-24T04:46:04Z] <raymond-ndibe@cloudcumin1001> END (PASS) - Cookbook wmcs.vps.create_project (exit_code=0) for project eseap in eqiad1 (T401957)

sudo cookbook wmcs.vps.create_project --user robertsky --user chlod --cluster-name eqiad1 --project eseap --task-id T401957 --description "To host eseap.org website and other related digital assets (for now a phorge task tracker) for ESEAP Hub"
...
raymond-ndibe@cloudcontrol1006:~$ sudo wmcs-openstack quota show eseap

+-----------------------+-------+
| Resource              | Limit |
+-----------------------+-------+
| cores                 |     8 |
| instances             |     8 |
| ram                   | 16384 |
| fixed_ips             |  None |
| networks              |   100 |
| volumes               |     8 |
| snapshots             |     4 |
| gigabytes             |    80 |
| backups               |    10 |
| volumes_high-iops     |    -1 |
| gigabytes_high-iops   |    -1 |
| snapshots_high-iops   |    -1 |
| volumes___DEFAULT__   |    -1 |
| gigabytes___DEFAULT__ |    -1 |
| snapshots___DEFAULT__ |    -1 |
| volumes_standard      |    -1 |
| gigabytes_standard    |    -1 |
| snapshots_standard    |    -1 |
| groups                |     4 |
| ports                 |   500 |
| rbac_policies         |    10 |
| routers               |    10 |
| subnets               |   100 |
| subnet_pools          |    -1 |
| injected-file-size    | 10240 |
| injected-path-size    |   255 |
| injected-files        |     5 |
| key-pairs             |   100 |
| properties            |   128 |
| server-group-members  |    10 |
| server-groups         |    10 |
| floating-ips          |     0 |
| secgroup-rules        |   100 |
| secgroups             |    40 |
| backup-gigabytes      |  1000 |
| per-volume-gigabytes  |    -1 |
+-----------------------+-------+

@Robertsky @Chlod, default quotas were used because there was no quota detail in the request. If you need some of these values changed, you need to create new requests