+1 from me

Project has been created, with 200 gigabytes of storage quota. Best wishes! If you need more storage, just let us know. I would also +1 bd808's comment about trying out trove. If you do, be sure to let us know how it goes!

In T286695#7231514, @White-Master wrote:

In our particular case, we stated the use of SASL because is required to access to Libera from DigitalOcean and I can set the mandatory access via sasl.

However, if are no exceptions the bnc service will stay on wikisp servers.

So: Zammad + Elasticsearch (1) , Moodle (2) + Limesurvey, Test enviroment (3). and two Floating IP for the two first VM

I think it makes maintaining the project easier to be more focused. But if you're comfortable with this setup, a project can be created.

I'm going to go ahead and close this as resolved as further quota changes would need to happen in a new request anyway. It seems like the initial creation of the project is complete.

@Ladsgroup thank you for clarifying and your patience. With Legal's approval on the private data being served, I've created a new project for you.

Is it possible to scope this request to a single specific project ? The amount of ideas makes it hard to evaluate this request. Projects which have specific purposes and use cases applicable to all end are a better fit for WMCS, as well as being easier to invite other volunteers to join.

Tested from toolforge.

@Ladsgroup I'm sorry you haven't heard back. Help me understand, are the changes you are making going to unblock creating this project?

I have granted the revised request quota mentioned here (https://phabricator.wikimedia.org/T284687#7198040). The project quota has been set to 600 GB, 20 cores, 48G of RAM.

Quota updated. Thanks!

+1 from me. Is this a temporary or permanent quota change?

Confirmed I can query from toolforge

Confirmed I can query from toolforge

@wiki_willy If a server replacement is likely, we can wait until Dell resolves the issue completely. We would prefer not to put a potentially failing server back into service. In other words, we can wait for a full resolution if it's easier for you and team.

+1 from me, thanks for figuring out the name.

Impacted clouddb's will be clouddb1013, clouddb1014, clouddb1021.

@Usmanmuhd as mentioned, the ability to rename or tweak accounts is quite limited unfortunately. We can remove accounts however. Are there accounts you would like to be deleted? For reference, as above, please specify exactly which accounts to delete. I see iamusman98, usmanmuhd, meusman.

You should have a password reset mail in your inbox . However, you can do this yourself anytime :-). Use https://wikitech.wikimedia.org/wiki/Special:PasswordReset.

Thank you for completing this audit! I appreciate the work and concerns you've raised, and I'm happy to discuss them.

@Cmjohnson Are we still looking at returning this machine? Has an RMA been started?

After looking at available resources, unfortunately given the size of the request, that much extra disk space is not something we can grant. Is it possible for you to instead stream the data you are looking to process rather than download and retain copies? As I understand it, streaming datasets is possible and done by others within the movement. However, I'm unsure of the details or if it's applicable to your use case.

Any updates on this? Confirmation from Legal?

+1 from me. This is now complete.

+1 from me as well. We appreciate you volunteering to help with this work!

You should now be able to reset the password for Mfchris84 using this link: https://wikitech.wikimedia.org/wiki/Special:PasswordReset

For reference, the current project quota is:
8 instances
8 vCPU
16G RAM

Instances have been changed from 8 -> 16.

+1 from me as well.

Thanks for the request! Can you describe how big the datasets you intend to process are? 2.1TB is a lot of space. How many instance are you looking to run / and what will they be used for?

The project has the increased quota to 16 vCPU, 34G RAM.

Current quota for wikisource is:
11 vCPU and 24G RAM

I'm +1 as well. I've added 16 vCPU. Total vCPU is 178 now.

@Samwilson is this increase temporary in anticipation of a move to VPS or ?

Brooke also kindly pointed out we should include the range from our test setup

185.15.56.0/25 should cover the correct range.

@Jclark-ctr @wiki_willy were we able to upgrade this firmware and see if that helped?

I'll be around to help facilitate this. Let me know if there's something specific I can help with!

I'll be around to help facilitate this. Let me know if there's something specific I can help with!

Following. This could be an interesting reference implementation for other uses / problems. I would be mindful of the networking requirements here and loop in I/F as well.

@Reedy @JBennett Let's get an ask into the Hardware requests for next fiscal and target Q1 for a system that can store this data securely and meet your current and future needs. I would ask you to prioritize doing this migration in Q1 as we are unable to continue to store the data. Ping me if you'd like help on requesting.

This is still under review. Unfortunately I don't have an ETA to share.

+1, let us know once it's transitioned and what your final quota needs will be

@Marostegui Thanks for jumping on this quickly. Hopefully this means this collection of hosts will be in a healthy state for the migration. To answer your earlier question, I would say yes. If there is another non-trivial breakage let's wait until after switching sanitarium hosts and consider depooling or any other option as well depending on the outcome of the switchover.

Thanks @Urbanecm ! Turnilo looks like a useful way to present data in an easy to use and understand manner. I hope your project enables similar insights for the WMCZ community. +1 from me.

I'm +1 for removing. Thanks for helping clean up resources!

Do you have an idea what software / tool you will use to collect and analyze stats?

+1 from me!

@Gopavasanth your quota should now let you deploy per the suggested chart above. Let us know if you need assistance/quota with cinder as well. Thanks!

Thanks for making these! I like 4 or 5 the most.

I'm +1 in support.

@Gopavasanth yes, so if you can migrate to the new flavors and use cinder volumes, we should be able to meet your disk needs. For the compute, does something like this work?

Majavah, are you open to migrating to using cinder and the new g3 flavors? Or are you locked into shared storage?

While it was noticed within a WMCS ip range first, I believe this affects everything utilizing the exemption ranges (https://commons.wikimedia.org/wiki/MediaWiki:Block-autoblock-exemptionlist).