Senior DevOps Contractor – Speed & Function
User Details
- User Since
- Oct 6 2021, 4:41 PM (129 w, 1 d)
- Availability
- Available
- LDAP User
- Unknown
- MediaWiki User
- Alex.lep.sp [ Global Accounts ]
Tue, Mar 5
WME Gitlab instance was upgraded to version 16.8.3, we didn't face any issues during the upgrade.
The ticket can be closed.
Jan 18 2024
Nov 16 2023
@JArguello-WMF
Yes, let's close this ticket. In case some fixes in the documentation will be needed - i can fix those in ad-hoc mode, not expecting much queries from the team.
Nov 2 2023
Oct 25 2023
- Dev Access to kafka UI and Airflow UI are not available anymore.
- Production Access will be blocked within 1-2 days.
- Now the management tools are accessible only using the AWS Sessions manager, so only for a dedicated subset of AWS users. Documentation for activating the access is available.
- Access to Sonarqube should be blocked in frames of a separate ticket, since Sonarqube also requires an upgrade.
Sep 19 2023
After a short discussion we have activated a mandatory MFA for Irene's account, and now Irene is able to query the logs through the AWS Console.
Also we have found a way fetch the scripts from the repository, since local environment is not yet configured to access the git repos.
The next steps are:
- Irene will prepare local environment (export env vars, prepare python virtual env, etc) to run the data analyses scripts - most likely some Nat's help will be needed here.
- In case of any permission issues - @Iflorez will inform us here in the ticket, and we will try to debug it offline or arrange another debug session.
Sep 18 2023
Related to CSP, fixing.
Sep 11 2023
@Iflorez
All the requested permissions were granted earlier.
I've added additional permissions in AccessDeniedException from your comment + some of the permissions on-top, and I hope this should allow you to run the script.
Ping me in case of issues please.
Thx
Sep 7 2023
hey, all the permissions should be in place.
Irene, can you please validate?
Aug 16 2023
Aug 14 2023
Jul 25 2023
The tags were added and now we see the data by the tags.
Thou it looks like we need to add tags for more resources to make the information more useful.
We can close this ticket and open a new one on improving the existing setup.
The POC was prepared, and the results were shared during the tech session.
The documentation was prepared.
Jul 24 2023
The changes were deployed to the environments, and the corresponding tags were activated for tracking:
https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/activating-tags.html
We will check the situation in 1-2 days once some statistics will be aggregated.
Jun 1 2023
May 18 2023
May 11 2023
May 4 2023
Apr 28 2023
Apr 27 2023
Apr 26 2023
Apr 20 2023
Apr 10 2023
Apr 6 2023
Mar 31 2023
Mar 23 2023
Mar 16 2023
Jan 30 2023
Jan 17 2023
Nov 14 2022
Oct 27 2022
CA setup is working fine now, both in local environment and in AWS.
Keycloak setup is still being worked on - majority of subtasks is completed, but still some polishing is needed - we are catching some errors after AWS deployment.
Oct 8 2022
Oct 3 2022
Ideally, we should have all plugins installed manually - or all plugins installed "automagically".
Since we are using containerized approach and installing the plugins manually right now - all the plugins are found on a shared volume, mounted to all the containers. This way all the updates are reflected immediately on all the running instances of Wordpress. If we want our custom plugins to be installed in automated manner - we need an extra step in startup script, which will copy plugins to the plugins directory, which was mounted on startup.
Alternatively WP config could be modified to get the plugins from different directories, so all the public and premium plugins could be in mounted volume ("Directory A"), while all the custom plugins could bundled in docker image, in "Directory B". I'm just not sure Wordpress supports such a config (doubt it, but need to double-check).
Aug 15 2022
Permissions were modified, moved the ticket to QA.
Shared the dashboard with the stakeholders and waiting for the initial feedback, so the ticket is moved to QA.
Aug 12 2022
Aug 4 2022
Jul 4 2022
https://enterprise.wikimedia.com/robots.txt
It's available now.
May 25 2022
May 4 2022
IAC is deployed, and CI\CD pipeline is in place. Webpage is available already.
May 2 2022
Should be resolved now. please double-check. Re-initiated the runner from the latest official image.
Apr 27 2022
wikimediaenterprise.org now redirects to https://enterprise.wikimedia.com, was configured via S3 bucket and R53 record.
Apr 25 2022
@SDelbecque-WMF
We will also need you public PGP key for this operation.
Do you need any help with generating it? Or maybe you have the one already?
Record was added.