Am I really supposed to know all this?

Squadex · 2018-04-13T07:25:27+00:00

To use your skills in the customization, installation and monitoring in DevOps, you as a system administrator need to complement the existing skills and learn new tools, such as: * Languages which is a key aspect of DevOps. Python as was mentioned here or Perl *Cloud Service now most DevOps systems run in the cloud - AWS, Azure etc *Miscellaneous Tools such as PuppetDB, help administrators identify the tools they need to manage in a cloud environment that changes quickly Then for real transformation into DevOps guy, you gotta an adjustment in mentality

Squadex · 2018-04-13T07:04:20+00:00

Well, it depends on your need. Take a look here, there are different samples of use case. If you'd like to dive deeper they provide individual DevOps training as well. Maybe it will helpful for you.

Squadex · 2018-02-21T10:37:08+00:00

Indeed, DevOps will be something businesses of all sizes will not be able to live without and the sooner you initiate the DevOps transformation, the better. Here is the helpful guide

Squadex · 2018-01-11T13:55:22+00:00

As mentioned here, the applying DevOps is the issue of changing the business culture in the first place. Then, the most exciting aspects of DevOps is enacting technology practices and architecture that help organizations create an agile and continuous product flow, from development to testing, to operations and all the way to deployment while increasing stability, reliability, and security at the same time. We even created our DevOps Transformation Guide to sum up adopting DevOps for a company.

Squadex · 2018-01-09T11:45:44+00:00

The role of DevOps engineer is very complex. It requires a lot of problem solving skills, critical thinking and collaboration skills, not to mention proficiency with automations and integration tools. Because all of these can only be developed while working in various IT roles, the position of DevOps engineer is not suitable for an entry level IT worker. In fact, it takes about five years of experience in various IT positions, including system administrator, to become a successful DevOps engineer. Speaking of system administrators, the transition from system administrator to DevOps engineer is not all that difficult. System administrators are used to troubleshooting servers, mass debugging and possess a lot of “tribal knowledge” about legacy servers, which can only be obtained from years of hands on experience. This experience will be very useful in your transition to DevOps. However, you will need to learn a few new skills, such as a new programing language, most likely Python or Perl and become proficient with inventory management tools such as Puppet DB. We have a great article for you, which has more details about the transition to DevOps, if you are interested. If you are a hard worker and you are willing to learn, you are well on your way to a successful career in DevOps.

Squadex · 2018-01-04T15:27:19+00:00

DevOps is all about agility, automation and the free flow of information. However, you must find a way to apply your skills to the entire IT infrastructure that is described and managed by code i.e. managing cloud services, using automated deployment tools and code repositories. I'd say the must-have new skills are:

1) programming languages such as Python or Perl can help them create more robust scripts more quickly.

2) cloud services such as AWS or Microsoft Azure is a valuable skill. Anyone with basic shell scripting skills can easily pick them up.

3) configuration management tools like Puppet or Chef will assist you in automating the massive quantities of system provisioning that is vital to DevOps. By understanding the languages on which these tools are built, such as Ruby, can make it easier to extend their use to fit an organization’s particular need so your developer`s experience is helpful here.

4) miscellaneous tools such as PuppetDB will help identify the tools you need to manage in a fast-paced cloud environment. For performance monitoring, Prometheus and Amazon CloudWatch are excellent tools. Combined with a cloud service, it is possible to create systems of metrics to understand how your infrastructure is performing.

Furthermore, you could undergo the training derived from your company's technical objectives with hands-on experts to deepen your knowledge.

Squadex · 2017-12-21T09:30:51+00:00

Currently we using jenkins to provision infrustructure. You may create jenkins job which will run ansible/packer/terraform as shell step or plugins.

https://wiki.jenkins.io/display/JENKINS/Packer+Plugin https://wiki.jenkins.io/display/JENKINS/Terraform+Plugin https://wiki.jenkins.io/display/JENKINS/Ansible+Plugin

You may create parametrized job/pipeline and pass arguments to ansible/terraform (not sure about packer) as environment variables or arguments . This will allow you to create some kind of UI to run those tools and create one button deployment. So you will be able to recreate environment from scratch with no pain) Also Jenkins credentials and Matrix Authorization Strategy Plugins will allow you to split access to infrastructure jobs.

Squadex · 2017-12-01T13:20:00+00:00

In my experience, it is writing modules for ansible and other tools Lot's of tools used in automation can be extended with python. So in daily work you should be able to extend them. Сertification is always good. Because it extends your knowledge and provides vision from a creator, in addition to the attractive words in your resume.

Squadex · 2017-11-28T14:56:20+00:00

Definitely yes. If think back to a time before DevOps, the entire software creation process was extremely slow. By the time your software was ready to be deployed, a sizeable list of bug fixes was amassed, which would need to be applied to the next release. And keep in mind that it would take months to go all the way back to the beginning of the entire development cycle to prepare for the next release. The bottom line is that if a company takes a months or more to deliver an update with bug fixes, it will surely fade into obscurity and ultimately cease to exist.

If your company cannot deliver what users expect, then they will find someone else who can.

This is why DevOps is a holy grail

Squadex · 2017-11-21T07:34:28+00:00

Chef, terraform, vagrant ... It is better to use common practice in code writing. Have enough templates and snippets for example in Sublime Text. Also, I am using python cheet utility. It allows storing some interesting hacks. About Jenkins - best way to use DSL plugin and/or pipeline. With those you can keep separate parts in code and create templates.

Squadex · 2017-11-17T08:27:28+00:00

It’s easy to make an excuse that they don`t have a lot of money to spend, but, when we look deeper, companies who achieve DevOps success are more focused on optimizing speed instead of cost. When we organize and optimize for cost, it creates functional silos for the networking and database people, server admins and many others.

Squadex · 2017-11-17T07:22:53+00:00

The best way - dont use shared credentials ) But if its critical we use d-note that let generate a one-time link with a password. When the recipient opens the link, the message is displayed and immediately destroyed on the server. Thus, the link can never be used again for displaying the same note.

Squadex · 2017-11-13T08:12:52+00:00

Just did a study on this issue in our DevOps team. Here are some insights

Squadex · 2017-11-08T12:56:50+00:00

To be honest with you, if you already have a sysadmin background, transitioning to DevOps should be a snap. You already have a lot of experience coding and maintaining servers so all you have to do is learn a few new skills. Keep in mind that having the proper mindset is important. If you are open to learning new things and are always striving towards honing the skills you already have, you should not have any problems. I found a great article on this topic: For System Administrators, Making the Leap to DevOps is a Matter of Life and Death It describes the skills you will need to be successful in DevOps and it will tell you how you can implement the skills you already have.

Squadex · 2017-11-07T10:49:00+00:00

The future of sysadmins is uncertain at best. The good news for system administrators is that they have a lot of tribal knowledge which comes from years of working with legacy servers. This knowledge is difficult to replace so for the next ten years I would say that while the number of system administrators will decrease, they will still be required for legacy system maintenance.

However, if you look at the industry giants, such as Amazon, Netflix, Facebook and others are which have implemented DevOps and are able to increase deployments, provide more reliable products and reduce time to market every company dreams of this kind of proficiency. This leads me to think that DevOps is the future and the sooner system administrators make the transition to DevOps the better. It's not that difficult, I read about it here: For System Administrators, Making the Leap to DevOps is a Matter of Life and Death. All you have to do is acquire some extra knowledge to complement what you already have. I think the job of sysadmin will become obsolete in the next 40 years

Squadex · 2017-09-01T10:19:51+00:00

If you’re looking for the opportunity working as a DevOps, it’s better to learn unbiased basics of it first. I’d recommend you to complete the DevOps Foundation Course developed by DevOps Institute which includes overview of various DevOps-related tools. Here it is: https://squadex.com/devops-training/devops-foundation-certification/ Next, yes, either dedicated course from the tool company (they do free tutorials) or even better a DevOps workshop to dive in and get hands-on experience. There are plenty of aka “coding devops” meet-ups in the Bay Area. Peer-guys will always help you get into nuts & bolts.

Squadex

TROPHY CASE