The migration and sharing of IDC engine room server

Demand:

Need to transfer the original computer room server and re-planning the new IDC Room server business, so the original entire business to be split and migrated. The following is the original computer room architecture diagram, the server between the login for the secret key login, and 192.168.111.30 for the springboard machine, can only be connected to other servers through this machine, other machines can not connect with each other. Gateway is 192.168.111.253, Mask is 255.255.255.0 (24-bit)

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/73/E2/wKiom1YJAZ6Q6HI-AAKBEeO8VRU856.jpg "title=" New.png "alt=" Wkiom1yjaz6q6hi-aakbeeo8vru856.jpg "/>

If you can read it carefully, it will certainly help you personally.

From the above architecture diagram, the main is the Nginx this piece, the second is the master-slave synchronization of MySQL, in fact, the building of friends can be seen, this is a common and easier to implement the architecture, in PV day visits reached more than million, this architecture is definitely rejected by the boss, and this program is not feasible. (This schema PV at the same time on-line up to about 100,000) well, then to share the specific operation.

Here's how:

1. In the firewall this block, we need to set the network card inside and outside the address, and ensure that the external network can be accessed normally. Build OpenVPN (Let the office area Network can access to IDC room), the implementation of NAT is for the engine room internal server can access the external network, open iptables Firewall policy ( This is very important!!!) )
   

This article is from the "Small Sea" blog, please be sure to keep this source http://hason.blog.51cto.com/8271396/1698904

The migration and sharing of IDC engine room server