Page MenuHomePhabricator

[Spike] Investigate deployment strategy for v0 [high priority]
Closed, ResolvedPublic2 Estimated Story Points

Description

We need to make a decision on where to host v0. Currently, we are considering the following options:

Let's timebox this investigation to 1 week with 1 developer: please update with any findings/prototype in 1 week so we can determine next steps together.

Event Timeline

ifried renamed this task from [Spike] Investigate deployment strategy for v0 to [Spike] Investigate deployment strategy for v0 [high priority].Mar 28 2022, 3:53 PM

I will have a meeting with Stephane next week to try pathcdemo.

I am also checking how could we deploy it to beta

Seems that the VPC could also be a good option (I am checking with some people around this).

Talking to Bryan he shared with me some useful information on how we can request for a "New VPC project" I am taking a look at it.

There is a link under "Requesting a new project" here, that will open a template task for us to fill out to get the project created. (I will be checking on this)

vyuen set the point value for this task to 2.Mar 31 2022, 5:21 PM

One thing I'd like to point out. While it's not a hard dependency, our extension uses CentralAuth quite a bit for global user data. Hence, if we want to build an environment that resembles what we'll have in production, we don't just need a single wiki, we need a wiki farm with CentralAuth. This is already the case for the beta cluster, and while it should be entirely possible to do that in a custom VPS instance, it could take some time to get everything working. Patchdemo, OTOH, does not support wiki farms at all, AFAICS.

One thing I'd like to point out. While it's not a hard dependency, our extension uses CentralAuth quite a bit for global user data. Hence, if we want to build an environment that resembles what we'll have in production, we don't just need a single wiki, we need a wiki farm with CentralAuth. This is already the case for the beta cluster, and while it should be entirely possible to do that in a custom VPS instance, it could take some time to get everything working. Patchdemo, OTOH, does not support wiki farms at all, AFAICS.

Thanks Emanuele, I agree, I am checking VPC and toolforge options, and it seems that they are not a good option for what we need.

One thing I'd like to point out. While it's not a hard dependency, our extension uses CentralAuth quite a bit for global user data. Hence, if we want to build an environment that resembles what we'll have in production, we don't just need a single wiki, we need a wiki farm with CentralAuth. This is already the case for the beta cluster, and while it should be entirely possible to do that in a custom VPS instance, it could take some time to get everything working. Patchdemo, OTOH, does not support wiki farms at all, AFAICS.

Thanks Emanuele, I agree, I am checking VPC and toolforge options, and it seems that they are not a good option for what we need.

We decide to deploy it to Patchdemo and to beta cluster.

Patchdemo will be used by the campaign teams to test.

For the V0 tests, we will use beta cluster

@cmelo has successfully deployed to patchdemo (thank you!) at https://patchdemo.wmflabs.org/wikis/275c2eb463/wiki/. Considering this resolved.