Show Navigation
Conversation
Notices
-
@Moon @lnxw48a1 Ok, if they're different then I suppose it would be better for me to actually just learn the one I think is a better move for my career, AWS, rather than learning Azure just because it would be more useful to my current employer.
- LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} and GeniusMusing like this.
-
Question to other fedi sysadmins; would I regret it if I started learning AWS?
From where I'm looking, it seems to me like not diversifying into cloud is gonna cap my opportunities career-wise.
-
@guizzy I'm doing the same: learning cloudy stuff (AWS, Azure, thinking about Google Cloud) because I don't want to restrict my options.
Too bad I didn't spend more time on AWS when @musicman was starting to learn it and offered me an account in his auth group.
(I suspect it was partly due to one of those "work 12-16 hour days" assignments; added to "log in from hotel Wi-Fi", it usually means the end of anything you're working on.)
-
I was indirectly answering your question, but let me be direct: learn cloudy stuff. Even if you stay where you are now, at some point, management will say "what if we moved some of our stuff to the cloud?" and you want to be the one that says "I've been running cloud instances for years so that I'd be ready when you are."
-
@lnxw48a1 @musicman I'm not learning it yet, but a friend/ex-colleague has been bugging me about it for a while. My main problem is that I don't do well with organized learning; I'm a hands-on, build something for myself kind of learner. Not just practical exercices; to get me interested, I need to have personal interest in what I'm building.
-
@lnxw48a1 We already are moving stuff to the cloud. I'm not seeing it so much as a move for my current employer (we're moving to Azure, while I'm more inclined to learn AWS), but for my future prospects.
-
@guizzy A retro-gaming site! 16-bit Quebecois!
@musicman
-
@Moon @lnxw48a1 How's the crossover in knowledge between AWS and Azure? Are the concepts basically the same, just with different tools?
-
@nik @Moon @lnxw48a1 Coming from a Microsoft admin background? I'm already fairly comfortable with AD from on-prem, how applicable is that knowledge to Azure AD?
-
@lnxw48a1 @musicman And I could probably even pay for the AWS instances by writing articles about online casinos!
-
@guizzy When I first looked at Azure, it seemed like even the simplest site needed multiple moving parts. I think I was just used to having all the pieces in a single VPS server instead of starting from the beginning with a database instance, a web instance, a compute instance, and so on.
That's why I decided to start out with a couple of courses, then move on to building a couple of projects on my own.
-
Perhaps you would be better served learning K8s as all the major cloud providers have that
-
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.