DevOps an ideological and cultural change, combined with the automation concept, we are redefining cooperation and development operation and maintenance personnel.
DevOps is not just the development and integration of operation and maintenance literally, over the years, these two groups have been separated by cultural and intellectual boundaries, particularly within large enterprise IT organizations.
This separation is very direct, developers only care about coding, the operation and maintenance personnel to ensure their normal operation. Complete disconnect between them, resulting in the need for longer QA cycle. And often can not deploy a new program on the environment, as this may result in downtime or disrupt other programs.
This organizational division, risk aversion, and a combination of sequential "waterfall" model of software delivery, software updates will make time to reach a year or even longer. This combination, still exist in many large organizations.
However, over the past decade, some major changes are reshaping the IT field. Developers had enough problems arise when deploying code to start writing software automation deployment. Meanwhile, operation and maintenance staff also contribute their deep expertise to help developers better to write such software.
Between the development and operation and maintenance have clear boundaries are slowly becoming blurred, resulting in on-line application speed faster and faster, QA cycles are getting shorter, the deployment of more and more. Even when we combine the new process, such as the use of continuous integration and continuous deployment of ways. DevOps use many methods to build large applications, several times a day to deploy a production environment, instead of several times a year.
This is not a fad, this automation trend is gradually developing over the past decade, and have been very mature in terms of software and processes. Its implications for internal IT developers is that every manager needs to seriously consider.
If you do not understand why DevOps is so important, and not ready to deal with change brought about DevOps, then this company you will be very detrimental.
How DevOps affect developers?
DevOps origins can be traced back as when tools such as Puppet had just been born, these tools as early as around 2005 had already seen. At that time, as Ruby developers Luke Kanies tired of manually configure Linux and manually modify configuration files. He dreamed of in a more programmed and repeatable manner, to configure the Unix-like systems. So, he wrote a Ruby script, to help him achieve the above process, he will be named as Puppet.
Later, there have been many similar tools, including Chef, Ansible, SaltStack and so on. In addition, the community will be a combination of these tools. Developers and experts in the operation and maintenance of their deployment code package upload, it allows you to configure the software in a similar manner, without regard to the underlying Unix release.
Using these tools, developers can create a program of self-contained environment on how to run the application. It will contain all the dependencies required by the application, and simply run a script, you can configure and start them on a variety of Unix distributions. It used to take highly skilled professionals to set and adjust a few weeks to a good environment, now with the help of a script, perhaps hours to complete.
Although developers can now faster than ever, easier to deploy code. Developers no longer dependent on the operation and maintenance co-workers to start their own responsible for maintaining their own applications running.
It also promoted the development of another tool, platform as a service, or simply PaaS. PaaS was originally conceived by Salesforce and Google, it requires developers to write an application can put a special code on their platform. However, before this method HeroKu show running code to developers, PaaS and not universal.
DevOps PaaS system is based on the principle of automation. In fact, so far, many of PaaS systems are to set up and run them through DevOps tools. The difference between PaaS and applications that use PaaS, you can fully manage applications running on them. You can API startup, shutdown, and expand the monitoring application PaaS. In DevOps, you can create a set of tools to manage your application, but in PaaS, these tools are already ready for you.
Finally, the discussion would have to mention docker DevOps and containers, the biggest drawback is that it is strictly PaaS predefined application architecture. If developers want better environmental control program, the container can provide good speed and flexibility to the user. Use Chef or Puppet to spend a few hours of deployment environment, and ultimately may not be exactly the same to obtain a copy. The use of containers, developers can in a very short period of time, to reproduce the deployment of Linux or Windows environment, and ensure that it is a totally consistent copy.
Over the years, developers through the use and improvement of these DevOps tools, has created a huge productivity. As the operator to run the application becoming fully automated computer code. Eliminating the need for developers to deploy the day is coming.
How DevOps affect the operation and maintenance personnel?
Although developers have begun DevOps revolution, however, the system administrator and is the key to its operation and maintenance experts finally adopted. After all, these tools can help them work more efficiently. In fact, DevOps tools have significantly changed the working range of modern agile operation and maintenance team responsible.
Before DevOps, system administrators and operations teams responsible for ensuring the normal operation of each application. Including setting database and web server, set up load balancing, security, and management into the system and so on.
DevOps to achieve a high standardization, only a few tools, you can replace human intervention, using effective way to deploy, configure and run many services.
Increasingly, the operation and maintenance personnel responsible for deploying and maintaining such DevOps automation services. For example: PaaS, Linux and Windows cluster container. Developers only need to be deployed to various applications such services, and operation and maintenance team responsible for the operation and expansion of such services. DevOps platforms and tools to create an environment that allows developers and operations teams work independently of each other.
With the birth of DevOps, developers can have a quota, within a certain range, they can follow the demand, real-time deployment environment. Operation and maintenance team no longer need to worry about deploying a single application. They still purchase hardware, and configure and manage the servers, but the scale is much larger than a single application. Their responsibilities: DevOps automation management easier for developers to use the service.
This technology environment will separate the life cycle of the application, the developer and operation and maintenance personnel can work together more closely. It allows developers to deploy code to clear the system and let the system operation and maintenance management team will ensure that developers have separate responsibilities.
But the contact person between developers and operations teams, DevOps tools have become blurred responsibility of a collaborative ecosystem. Operation and maintenance team needs for operation and maintenance of complex software systems, in-depth knowledge. Developers will need the help of no operation and maintenance personnel, to deploy the system.
More and more companies start hiring programmers have experience in operation and maintenance, and system administrators have programming experience. Overall, DevOps greatest impact on the operation and maintenance team, they are increasingly responsible for running the application from the system, which will provide developers with more automated on-demand deployment options.
DevOps, a virtuous cycle
As Mark Anderson's famous "software is changing the world", to build and run applications, like phone calls and checked into the same hotel. The task of running the application has been trained system administrators responsible for, but now devops has gradually become the mainstream.
Most say that knowledge is undocumented, and the like folklore as oral tradition from generation to generation. Configuration file has its own unique format, some formats very strange that there will be compiled into a configuration file other configuration files. Exactly how and why the provisioning of these documents, only a few people know.
All DevOps has become a profound knowledge of the operation and maintenance records to the method of open standards, these standards can be recorded and tracked at any time. As developers have more knowledge of operation and maintenance, system administrators have more programming knowledge, their responsibilities will eventually fused.
Docker is the leading container management platform, is another example of this development. Github provides developers with an open environment to share codes with each other and collaborate more easily than ever before. Docker Hub is creating the same type of environment as a system administrator, to lead the new revival of infrastructure deployment and management.
DevOps will always continue to develop, and there is always a new tool, a different framework as well as a cool into a strong trend for its fresh vitality. As it brings continuous integration and software development for the continuous delivery, it also brings a programmable infrastructure for operation and maintenance personnel.
Original link:
https://www.infoworld.com/article/3230285/devops/how-devops-changes-dev-and-ops.html