DevOps server Deployment and Configuration Management in 2018


DevOps server Deployment and Configuration Management

In recent years, as the number of servers leading to a little bit more and services rendered required greater flexibility in terms of adding and deleting than configured for server-specific purposes, it does not try a different Implementation and Configuration Tool.

The improvements are also the way the systems management has progressed in the same way as we are beginning to build everything on hand, without the registration process, then the document editing of text files and finally preparing the Man Manifest Manifest But one of these techniques allows for quick payment, controlling the regular pattern or the flexibility required to modify the daily requirements.
I
n recent years, "Devops" (a good integration of activities and activities) has become a book and application for companies that use development tools.

Very short (and unfortunately) philosophy DevOps

Server, such roles need to be managed through the release control configuration and should be discarded (screaming in common. The Server server burns its code if it exploded the server, or if some of the organizations' organizations should have the ability to pay or cancel minutes, but not hours (several days or weeks), and should be able to afford and withdraw directly, without prejudice.

Using the cloud platform with the API management server (such as Amazon Web, VMWare vCloud, Rackspace, or Ocean Digital), the management and configuration device (one of the ones listed below) may be affected Adding, updating and deleting services In addition, individual developers should be able to run their own server and server management (at least for an optimal environment).

The aim of the programs is also to reduce disagreement between development teams and operational teams. Normally, if an application fails or fails, the next days are spent on a misdemeanor, trying to find out who is unhappy. If both developers and colleagues, together with infrastructure management and management, share responsibility for SLA and feedback. DevOps interview question and answers

Management Tools and Performance Equipment

The three elements below are the three that I see about which are often reported. I would like to summarize some of the characteristics of each and every factor that can influence one another's use. Three, much or less, and similar, I used in every one, but I do not have international choices from each other. Each is appropriate in some situations.

chef(Opscode)

  • For Ruby Ruby, use natural ruby ​​ruby.
  • Adjust the softness.
  • It can be switched over by a central server or a single host.
  • Computer control components
  • Requires additional software for everyone who is managed.

Summary Description: Implementation of the server and framework management tools based on Ruby. Define the style you want (for example, "cookbook") and then use the server. Code nodes (private servers) will receive the latest customization and update them to get new services  Implementing a new server is as simple as building a basic server, installing a boss, and determining the server to the central server of the cook.

Puppet (with Labeento doll)

  • Use Ruby + DSL to determine the configuration.
  • Adjust the softness.
  • You need a puppet doll that you must wear (usually).
  • Focus on controlling visual files.
  • Requires additional software for everyone who is managed.

Brief explanation: another tool to run the server and manage the ruby-based framework. The doll is very similar to the carrier, but I have a little different because it uses the Ruby doll + a customized custom domain (DSL), but some words are different. ("Master doll" instead of "central server center", "show" ring "cookbook", etc.). It seems that the doll is smaller than the company, but I did not use it enough to judge them.

ansible (AnsibleWorks)

  • Use YAML files to define the configuration.
  • Build Python.
  • Implementation directly from the workplace ("press" implementation).
  • Sports books define the shape.
  • You do not need additional software to install personal servers.

A brief description of the YAML structure and changes and implementation using Ssh, but you can set them up on one server more than once. The text differs from other options ("book" of brochures, not "brochures", etc.). In other words, instead of being a group of individuals looking for a new / renewal, change the central location (workplace). As a rule, it is much faster than Anita (especially a small server / computers), but requires a little more responsibility for personal development, which needs to be well aware of network security and SSH in general.

There are some other interesting devices (for example, SaltStack, which is similar to Anishi, but uses ZeroMQ instead of Ssh traffic, which means that the broad implementation can be quick, but it takes a little longer to be set up), but these are not most often mentioned and I'm trying control your own infrastructure (which now includes seven servers, often a lamp server or a node.js style).

Another issue is often happening, especially for people using a hard disk drive on a special staircase: What do you use for screws / dolls? - Click on the link for a good reason.

Local settings - Vagrant and VirtualBox

The above three devices were created to manage over a hundred or thousand servers (virtual or physical), but they can also be used as local hybrids, such as those created by VirtualBox VM or another application. Vagrant can easily create and destroy hardware boxes (or special services) on your computer.

I built the Vagrant profile for local government development and the configuration of one of my live production servers that allows me to install and restore server conditions on a local development and testing computer. Basically, I built a profile with a CentOS / RHEL shell, but I'm working with a warehouse profile using any of the above tools, just to see which one, the best complainant in an anesthetist. I still like Anishi so far, because I do not have many servers that I succeeded, and I do not have a large group of developers.

Vagrant has excellent documentation (complete and illustrated with introductory examples) for using various tools for setting up a new server.

Concluding notes

As the number of organizations managed by organizations increased, and web applications that depend on different servers to meet increasingly demanding needs, it became even more important to develop server management and infrastructure. Hours or days waiting for the speed limit of the forwarding server and not a good behavior that can rely on the server administrator's memory or a written instruction for the new server.

Use control management tools, such as those mentioned above, and ensure that customers are the same as everyone application.


Comments

Popular posts from this blog

Introduction to Ansible - DevOps in 2018

Important Topic of Terminology in DevOps

6 Compelling Business Benefits of DevOps In 2018