NightShade03 wrote: » Here are some quick initial thoughts: The "cloud" is a huge space. You can approach it from the software engineer / developer side where you are most provisioning tools/vm for your own use as you build an application. There is the perspective of the engineer who will ensure uptime, scalability, etc. There is the architect who designs cloud solutions from the ground up including security. There are a ton of different skills that go into this; from sciprting/programming, to virtualization, to understanding how to re-architect applications for the cloud. It certainly will require a different set of skills and way of thinking. Things like Puppet and Chef will offer you skills with automation and orchestration, which are certainly helpful in the cloud (because it's all about scalability). I would drop the Splunk cert as it isn't unique for the cloud. Also the Puppet cert can be helpful, but working with the cloud requires a diverse skill set and you'll probably want to know Puppet and Chef (or SaltStack or Ansible). Being able to use multiple tools and architect full solutions is the ultimate goal (in my opinion). So regardless of your course, just make sure you can achieve the same solution multiple ways. BTW - My day job is cloud architect so if you have any specific questions just fire away....always happy to help
UnixGuy wrote: » Interesting topic and this is something I'm interested in as well. I think it's a smart idea to skill up because traditional system administration/engineering is kind of disappearing or to be more accurate it's changing rapidly. Learning new tools is the first step that I personally took. I started with Puppet. I'm not sure what's next for me, but I don't want to stagnate anyway. For OP, to get experience as fast as possible, join a service provider. Your existing skills will be an asset and you will learn as you go. As far as certifications go, RHCSA is highly recommend and you will be contacted for jobs based on having this certification for sure. I would say Puppet/AWS are nice to have, but instead of going through those exams/certs, you can just setup a small VMs/lab and have some initial experience. Mention your lab experience/interest in your CV and this will get your foot in the door for a job where you can have an actual production experience. IMHO, certification aren't really necessary.
UnixGuy wrote: » but instead of going through those exams/certs, you can just setup a small VMs/lab and have some initial experience. Mention your lab experience/interest in your CV and this will get your foot in the door for a job where you can have an actual production experience. IMHO, certification aren't really necessary.
chanakyajupudi wrote: » I have moved from India to New Zealand and have done a Graduate Diploma. The problem with me getting hired as an experienced hire is that I have no IT experience in New Zealand and because I worked in India which is not an equal job market I will be considered as an entry level. The certifications and experience ensure my selection over a local here. I am definitely enraged. But I need to make a career here ! My growth is fast tracked due to my experience and pay as well.
gkca wrote: » What about the "dev" part of DevOps? I assume that a cloud engineer needs to have a good background in scripting and programming such as bash / perl /python / ruby and database technologies as well? And versioning systems such as SVN and Git?
chanakyajupudi wrote: » Essendon - I put my resume in another thread so that this thread does not get hijacked for me !http://www.techexams.net/forums/jobs-degrees/101511-resume-critique-kiwiland.html#post859355
bridgestone wrote: » Very interesting thread. I know that in London, DevOps jobs are all over the place and paying very, very well (have a look on the likes of jobserve or cwjobs) but still I see DevOps has not penetrated into all other major cities yet, at least in the job listings. I think it could well be that newer companies are going straight into it but more established companies have pencilled it in for the future - a bit like delaying the move from XP to Windows 7 - they know they have to do it at some point but they don't need to do it right now. On that note, I have also heard of DevOps being a "mindset" but it begs the question: if the traditional company does not yet have a DevOps department or function, when will it need to create one? Right now I'm your traditional Windows sysadmin (3rd line/infrastructure) but I think DevOps is the ideal position to transition into. I see a lot of jobs still wanting the traditional background. On that note I'm going to look into RHCSA next. Then learn Python. Then AWS. I wonder though, having just started my MCPs, is it worth getting the MCSE? Is it even worth me getting my MCSA? Bear in mind I already have a few years solid experience with 2003 R2/2008 R2/2012. I suppose it can't hurt but the opportunity cost is delaying my start with RHCSA and Python because I figure that if I do go for my MCSA then I should finish what I've already started......?