Beginner: Get out of five mistakes in Linux deployment

Linux, as a commercial application, is very mature, but it does not mean that every time you deploy Linux, you are very experienced and will still make some mistakes. When deploying Linux, linux Beginners should pay special attention to the following five aspects:

I. Too many deployments at a time

Whether you use Linux as a desktop system or a server, or both, if you fully deploy it in the entire system, it may lead to a qualitative problem. Before any deployment, you should first perform a deployment test in a small environment.

Make sure that your system runs normally during peak loads. This requires you to perform a lot of load tests and then fully deploy them on the server, in this way, you can determine whether to replace or modify the hardware with higher performance.

Starting from a small environment, if you find any problems, you still have the opportunity to quickly modify them.

2. mutual compatibility between old and new systems

The test deployment environment should not only test new systems, but also test the mutual compatibility and connectivity between new and old systems. If you are a Linux system, this is relatively easier. If your old system is Wndows, you need to check whether Windows users can access your new Linux system seamlessly.

Iii. Authentication

The new Linux system runs very well and users like to use it and the administrator management is easy, but they have to enable permission authentication for an Active Directory for Windows users. Of course, we can choose to give up this part completely, but if we can let him run perfectly, there is no need to let these troubles continue.

Ensure that your system can provide Single login SSO ). You do not need to log on repeatedly in LDAP, Linux, or Microsoft Active Directory.

4. Discard all old systems and replace them with new systems

You must know the idiom "don't break down", but IT becomes the biggest mistake when applied to IT.

In terms of IT, "Don't break" means to replace the existing infrastructure, and you need to determine your users unless there is a very convincing reason to fully migrate to the new system.

Of course, this does not mean that you will always be stuck on the original platform. This is usually a good time to break through when the service support period of your old system ends. When a system works well, it is a mistake to overturn it all.

V. Documentation

Deployment documents are required. You need to constantly manage and improve the perfect solution, and you cannot expect that this solution will always be managed by you alone, there will always be situations where the system needs to be managed by others. Therefore, any administrator must have a way to know the settings and changes you have made to the system. You need to record what you have done and how you have done it.

Make sure that all system files required for Linux deployment exist. The new administrator can redeploy, update the system, add users, and configure services. These should be recorded. These record documents must be accessible outside of the system, and a document backup is also required.

These aspects are summed up by some common sense. As deployment experience increases, these aspects will not cause any problems to you.

Let's talk about the experiences that everyone has discussed.

Original article: http://www.linux.com/news/technology-feature/security/383997:top-five-linux-deployment-mistakes