Okay, who would like to help me run #DevOops at @pyconau again this year?
Should I run #DevOops at PyConAU again this year?
The week just started and I already reached that level :thisisfine:
Already have my first #DevOops at #DevOpsDays Chicago. I wasn't paying close attention at the sink and tried to wash my hands with mouthwash. If you shake my hand, it will be minty fresh. 😂
« During this morning's forum maintenance window, a backup of the forum database from one day ago (Monday, February 10th) was mistakenly restored by internal infrastructure DevOps team over the production database, which did not experience any issues and did not require restoration »
The good news is that restoring a backup is actually working 😅
🔗 Backup software vendor Veeam botched restore, lost data https://www.theregister.com/2025/02/17/veeam_forums_data_loss/
Bit of "fun" with O365 email for us this week...
Background: Our main email domain's MX records are on-prem servers that do a bunch of things, and email for our O365 domain relays through them. These on-prem MX servers have been dual-stack (ipv4 and ipv6) for many years now.
Not sure exactly when MS made various changes, but our example-com.mail.protection.outlook.com records have both ipv4 (A) and ipv6 (AAAA) addresses.
And they enforce that email they receive has to be via a "trusted connector" for your domain, pass SPF, or pass DKIM.
> 450 4.7.26 Service does not accept messages sent over IPv6 [dead::beef::1] unless they pass either SPF or DKIM validation (message not signed)
But O365 doesn't yet support adding ipv6 IPs/ranges to the trusted/connector list.
So, suddenly email sent to us without DKIM signatures was getting stuck in the MX server queues.
Our temporary workaround is we added egress firewall rules on the MX servers themselves blocking SMTP to 2a01:111:f400::/48 and 2a01:111:f403::/48 (the published ranges for their MX servers). Not ideal, but at least mail is flowing again.
Oh my, #GitLab. Get your shit together!!
Bug open for 3 years!! 🤯
Currently wasting runner minutes for us at work 👀
#CICD #Pipelines #DevOops
whomst among us has not hosed production due to #k8s
@jemsu our industry has been running in this circle for ages #k8s , #prometheus lots of things that were solved and yes it's infuriating and depressing #devoops
The #DevOops track close from @pyconau has been published: https://www.youtube.com/watch?v=KR7i4pfKhDU
And while I'm having a whinge, I know that the term DevOps is practically meaningless these days, and has never really been a job title, but why would a Lead DevOps Engineer have the hard requirement of “you MUST come from a development background”.
Tell me you don't know what DevOps means without telling me you don't know… ;-)
Simplifying Python Web App Operations: Automating K8s Ops with Open Source, by David Andersson in the #DevOops track at @pyconau 2024.
Why UUIDs are Secretly Incredibly Fascinating, by Tom Eastman @tveastman in the #DevOops track at @pyconau 2024.