let me know if you want to talk about #K8s distros or have questions. It is a huge part of our 2021 plan, and this #openshift ticket I have now has shown me I need to spend a lot of time on it. I work better when I have something specific to test or figure out, so you're really doing me a favor.
We use #AWS and #ovirt for our...I'll call them provisioners. I much prefer ovirt, but we don't manage our puny DC and our IT team barely does, so for anything we want to approximate HA, we have to put it in AWS.
I know that you lose some features, but if I thought I might be using multiple clouds, I would look for a layer that sits in front of them, K8s or not.
our ovirt and AWS systems sit in different subnets (I'm not a networking person, maybe the wrong word...they can't talk to each other) which means I don't know how much I would gain by putting a layer between the two. Plus, I don't use the command line for either. I should probably learn that though, as I would be quicker.
I am learning a bit about using #Terraform with ovirt. Perhaps Terraform is the answer here for me.
on the Garmin I do. The daily scores aren't additive. Yesterday I ended up at 35. Because heart rate is so variable person-to-person, I doubt comparing numbers is super useful, but comparing against yourself seems to line up.
That said, I generally don't pay a lot of attention to it unless I feel like I have had a stressful day.
my Garmin stress level today is 37 already. Monday was 31. Tuesday was 32. ...so, yeah.
musicman (musicman@nu.federati.net)'s status on Wednesday, 04-Nov-2020 17:11:14 EST
musicmanPretty burned out. I'm on day 22/30 of 10k steps per day but idk if it is worth it. Of course, it seems I have some backup on my customer case but I have two issues I am stuck on. I tried to not take a lunch but only made it to 15:20. AWS and ovirt both giving issues. I guess I should look at the installer code to see what it is actually doing since there doesn't seem to be good documentation. Hadn't thought about that until just now.
ok, I have been informed that this invite was sent from a group, so deleting it could be tricky.
I don't actually know if this is tricky, but I don't care enough to find out, especially since I re-announced in slack since people don't actually read slack...a separate issue, entirely.
it'd be one thing if you did both, but to announce in slack, but not cancel it in Outlook is just dumb, but hey, I guess that's a lot of people in the world.
>... >"If you are looking to file or dispute a takedown notice by posting to this repository, please STOP because we do not accept Pull Requests or other contributions to this repository," wrote Jesse Geraci, Github's Corporate Counsel. "Please note that re-posting the exact same content that was the subject of a takedown notice without following the proper process is a violation of GitHub's DMCA Policy and Terms of Service. If you commit or post content to this repository that violates our Terms of Service, we will delete that content and may suspend access to your account as well," Geraci wrote. This statement caused an update to Github's earlier DMCA notice advice.
It might be a systemd issue, but I am using the official yum repo on Postgres 12, not postgres 13, and not doing anything fancy with systemd, so I doubt it.