3 ms·

"A sysadmin doesn’t want to automate his job and let the cloud provider manage what they can manage" There may be some people like that, but I never said that

"A sysadmin doesn’t want to automate his job and let the cloud provider manage what they can manage" There may be some people like that, but I never said that I didn't want to automate my job. I'd rather automate as much as possible. I realize that in order to scale infrastructure, you can't be sitting around manually pressing buttons and running apt-get command to install software.

scarface74 7y ago
And that requires programming. When the software architects come to you with a plan about how they plan to implement something, are you going you to understand the technology well enough to know that there is a managed alternative or will you just set up another VM? I was a dev lead at my previous company and they decided to “move to the cloud”. They brought in a whole bunch of consultants. I didn’t know the first thing about AWS back then. I showed the consultants my architectural plans. All of this was greenfield development. If they had known anything about development and understood anything I was talking about, there is no way they wouldn’t have suggested that we used managed services in place of things I was proposing hosting in VMs. Are you also willing to give up hosting things on VMs entirely and using managed services when possible. Will you even know how AWS’s services can be used in place of self hosted applications? This isn’t aimed at you in particular. But there is a lot more to implementing systems on AWS cost efficiently than automating VMs. Too many sysadmins turned “Cloud Architects” can’t get their mind around being “cloud native”. I haven’t even mentioned Kubernetes or Docker - because I haven’t used either yet. The consultants manually set up a VPC with different subnets in different availability zones just like they would have done on prem. No CloudFormation, no separate accounts under an organization, etc. They couldn’t talk about using AWS as developers, or setting up a CI/CD pipeline using AWS’s services.

scarface74 7y ago

And that requires programming. When the software architects come to you with a plan about how they plan to implement something, are you going you to understand the technology well enough to know that there is a managed alternative or will you just set up another VM? I was a dev lead at my previous company and they decided to “move to the cloud”. They brought in a whole bunch of consultants. I didn’t know the first thing about AWS back then. I showed the consultants my architectural plans. All of this was greenfield development. If they had known anything about development and understood anything I was talking about, there is no way they wouldn’t have suggested that we used managed services in place of things I was proposing hosting in VMs. Are you also willing to give up hosting things on VMs entirely and using managed services when possible. Will you even know how AWS’s services can be used in place of self hosted applications? This isn’t aimed at you in particular. But there is a lot more to implementing systems on AWS cost efficiently than automating VMs. Too many sysadmins turned “Cloud Architects” can’t get their mind around being “cloud native”. I haven’t even mentioned Kubernetes or Docker - because I haven’t used either yet. The consultants manually set up a VPC with different subnets in different availability zones just like they would have done on prem. No CloudFormation, no separate accounts under an organization, etc. They couldn’t talk about using AWS as developers, or setting up a CI/CD pipeline using AWS’s services.