@MusikAnimal, I clarified the timeline on the wiki to address your question. In short, barring unforeseen implementation issues, the new cluster will transition to be the default in March. You should expect more communication and announcements as this happens. I encourage you to keep planning your migration and utilizing the new cluster for testing.

This has been approved in our 2021-02-17 meeting.

I put you on the schedule and sent you an invite.

Project create, with Thelondonsimon as project admin. You should be able to add other users as needed.

@Aklapper you are most welcome to attend. Current cadence is every fortnight. Any of these dates work for you?

Survey is clear to use https://foundation.wikimedia.org/wiki/Wikimedia_Cloud_Services_Annual_Survey_Privacy_Statement

The project share should be ready for use. Utilize

Instance has been updated.

This was discussed and approved in the 2020-12-23 meeting.

I explicitly asked for confirmation to use the same privacy statement as last year.

views created

Views created.

This should be ready for use.

No matter the solution chosen, I wanted to advocate for ensuring we abstract implementation details away from the end users. I'd like to keep it very simple for end users (including us!) to utilize the service, while ensuring flexibility to make architectural changes in the future without user impact or concern. Ideally architecture changes would not have as much impact as the current scenario. While I wouldn't hide technical details about port, host, or section a wiki is in, I would discourage users from depending on those details.

I was able to discuss this with @faidon briefly. I'll summarize the discussion below.

Thanks for the explanations @ayounsi .

Project has now been created and all users have been added as admins.

+1 from me

This is something to discuss and potentially collaborate on. I'll follow-up with you.

In T265784#6575849, @ST47 wrote:

The block was lifted, mentioned a few comments above. However the rate limit is still in place, so we may be blocked again if we exceed 1000 queries to RIPE in 1 day.

On the section split, WMCS agrees with your logic of the most hit wikis being enwiki, commons and wikidata. We won't be perfect in distributing load, but separating those makes sense.

Thank you for contacting RIPE ST47. I've also reached out to RIPE and asked them to consider our use as a proxy and up the limits to 20k per 24 hours per their terms. I will update the ticket once I have a response.

For historical info for now.

This seems to be fixed now. Please feel free to reopen if needed.

After discussing this as a group, we came to the conclusion that more redundancy would serve everyone better. However, do you have any statistics on what the performance differences would be between the options? Especially in contrast to our existing setup, presumably both would be more performant, yes?

Hey Chris, can you help clarify the reason for the request? Most needs can be met by utilizing a proxy. Please see https://wikitech.wikimedia.org/wiki/Help:Using_a_web_proxy_to_reach_Cloud_VPS_servers_from_the_internet. If you have a specific need, please feel free to detail.

Ahh got it. No arguments are allowed for secure-cookbook. I confirmed I was able to run the cookbook. I have some questions on usability which we can address in a separate ticket if needed.

Ahh, thanks jbond. Trying with sudo, I don't have passwordless sudo on that machine.

I'm trying as a non-global root wmcs admin; here's what I get:

Project deleted and resources cleaned up. For the wiki pages, I believe only https://wikitech.wikimedia.org/wiki/Nova_Resource:Phlogiston/SAL is still around / needs cleaning if desired. I assume log is still valid even post closure. Marking resolved.

I'm guessing thought there should be a dumps dashboard and I should probably revert my edits :-)

The dashboard links are out of date for this. Can you link a current dashboard for labstore1006? I added it to https://grafana.wikimedia.org/d/000000568/labstore1004-1005-1006 quickly; but I don't know what you referenced.

Project cleaned up and removed. Thanks for letting us know!

Views created.

It seems some of the views were already created, but I double checked things. I believe this should be ready now.

Approved in meeting on 9 Sept 2020. You should now be able to attach a floating ip.