@aborrero Thank you very much for setting expectations. Thanks to your warning we have been able to start prototyping in some VPS somewhere else, and we are ready to start working on the WMCS VPSs as soon as they are created.

Would T207400: Puppetize Discourse get fixed by this and hence be a dependency?

No, Puppetize Discourse is a dependency for the deployment of Discourse in production (as currently stated in T207400).

Ah. In that case, our understanding of "documenting every step, every configuration, every plugin, following quality standards as close to production" heavily differs.

That sentence continues with "as we are capable of. " :)

Learning to puppetize Discourse or anything is out of my reasonable possibilities with all the work I'm supposed to do. Chris and I being the sysadmins in charge of these instances is already a stretch for us.

@Qgil: Ah, thanks! For clarity, have you tried somewhere (where?) to get external expertise involved to help with puppetizing, and this help is not available due to resources or no volunteers or such? (Maybe there has been some call for help to find folks familiar with Puppet which I have missed?)

I like the idea of creating a new instance and migrating the data of discourse1002.discourse.eqiad.wmflabs :-) (And thanks for sorting out the upgrade there the other day, by the way.)

I was just wondering: why create a whole new project, instead of just a new instance within the existing discourse project?

why create a whole new project, instead of just a new instance within the existing discourse project?

I am not sure, honestly. Whatever works. Having the fresh instance is what matters.

I think adding a new large instance to that project would be sufficient. It's still got space:

2 / 8 instances. 6 / 8 VCPUs. 12.0 GB / 16.0 GB RAM. 0 / 0 floating IPs. 1 / 10 security groups.

Thank you, I didn't know this. Works for me, especially if then we can deprecate one of the two other existing instances. I don't want to give extra work to anyone!

this fresh install will deprecate one of the two existing Discourse instances

@Qgil: What's the task ID for that deprecation? I'm curious how that deprecation is performed and communicated. Or where to file bugs about that Discourse instance.