Shulou(Shulou.com)06/01 Report--

Editor to share with you what are the misunderstandings of Linux deployment, I believe most people still do not understand, so share this article for your reference, I hope you can learn a lot after reading this article, let's go to know it!

First, deploy too many at one time in a short time.

Whether you use Linux as a desktop system or a server, or both, if you fully deploy to the entire system, it can lead to a quantitative change to a qualitative change. Before any deployment, you should first test the deployment of a small environment.

You need to ensure that your system operates properly under peak load, which requires you to do a lot of load testing and then fully deploy to the server to know if you need to replace more powerful hardware or modify the configuration.

Start with a small environment, and if you find any problems, you still have a chance to modify them quickly.

2. Mutual compatibility between new and old systems

Testing the deployment environment requires testing not only the new system, but also the compatibility and interoperability between the old and new systems. If your old system is also a Linux system, this is relatively easy. If your old system is a Wndows system, you need to check whether Windows users can seamlessly access your new Linux system.

III. Certification

The new Linux system works very well, users like to use it, and administrators are easy to manage, but they have to open an active directory authentication for Windows users. Of course, we can choose to give up this part completely, but if we can get him to run, there is no need to let these troubles continue.

Make sure your system can provide single sign-on (SSO). Whether in the LDAP of the entire system, in the configuration of the Linux system, or in the Active Directory with Microsoft, there is no need to log in repeatedly.

Give up the old system and replace it with the new system

You must know the idiom "don't break, don't stand", but it becomes a mistake when it comes to IT.

In the case of IT, "don't break, don't stand" means replacing the existing infrastructure, and you need to judge your users unless there is a very compelling reason to fully move to the new system.

Of course, this does not mean that you will be stuck on the original platform forever. At certain times, such as the end of the service support period for your old system, this is usually a good time to break through. When a system is working well, it is a mistake to overturn it all over again.

V. documentation

Deployment documentation is a must, even in * * solutions, you need to constantly manage and improve, and you can't expect this solution to be managed by you alone forever. There are always situations that cause the system to be managed by someone else. So any administrator must have a way to know what settings and changes you have made to the system, you need to record what you did, how you did it, and so on.

Ensure that the system files required for each Linux deployment exist, and that the new administrator can redeploy, update the system, add users, configure services, and so on. All these should be put on record. These records must be stored outside the system and accessible, and a document backup is also necessary.

These aspects are summed up by some common sense, and they won't bother you as you increase your deployment experience.

These are all the contents of the article "what are the misunderstandings of Linux deployment?" Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.