Ethereum multi machine deployment
DEVICE=eth1
BOOTPROTO=static
IPADDR=192.168.1.1
NETMASK=255.255.255.0
GATEWAY=你的网关
ONBOOT=yes
vim vi /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static
IPADDR=10.1.1.1
NETMASK=255.0.0.0
GATEWAY=你的网关
ONBOOT=yes
define the deployment workflow in the deployment script, which is generally:
prepare the environment, installation depends on
update code
build & compile
restart the service
for the event that the monitoring application hangs up and restarts automatically, you can give it to the supervisor: a process control system
2. Install a kickstart server, DHCP server, TFTP server (the above can be installed on the same server), configure kickstart configuration,
3. Other servers are configured for PXE network card startup, after startup, IP can be automatically assigned, and system installation can be started by getting kickstart configuration.
ha (high availability) cluster
is a cluster that normally works as a running server and transfers business to standby server when the running server fails. It's a cluster for high availability. Including shared disk and mirror disk< br /> Load balancing cluster
is a cluster that distributes client requests to each node according to the proper load balancing principle. It is a cluster with the purpose of high scalability, and generally can not carry out data handover. It includes load balance cluster and parallel database cluster< br /> HPC (High Performance Computing) cluster
refers to the cluster with large amount of computation. It's a cluster that uses supercomputers to perform a single business. In recent years, the grid computing technology that uses all nodes
CPU to perform a single service has become a hot spot
note: this paragraph is extracted from the NEC expresscluster proct start guide
according to your needs, it seems that high availability cluster can not achieve multi server parallel at present. The main procts are (NEC expresscluster, Veritas of Symantec, autostart of EMC and some domestic procts), and load balancing can realize load sharing, However, although the current load balancing realizes the business sharing to each server, it can't realize the data synchronization. (representative procts include F5, NEC's iplb and Barracuda)
as for high-performance computing, I haven't had much contact with it, so I may need to have in-depth communication according to the needs of the owner!
一台机器上部署多个jboss时,经常会报端口被占用,解决方法如下:
1.修改端口比较繁琐
(1). default/conf/jboss-service.xml中的1098,1099,4444,4445,4446,8083,
(2) serverdefaultdeployjboss-web.deployer server.xml中8080 8009
(3) 以及default/deploy/jms/uil2-service.xml中的8093端口
(4) run.bat中的9999端口
(5) serverdefaultdeployejb3.deployerMETA-INFjboss-service.xml 的3873端口
这样启动两个JBOSS的话就不会报任何端口占用异常
2.修改配置文件
(1) 直接修改jboss-BPO-XXXXXserverdefaultconfjboss-service.xml 193行 ports-01
如果是第几个应用就用第几个端口,现在可以部署4个一台机
(2) 如果超过4台机子修改bpo-bindings.xml文件里面的端口号,不要让服务器的重复,每个端口号码加100
主端口号则为180 280 380这样子加上去
<mbean code="org.jboss.services.binding.ServiceBindingManager"
name="jboss.system:service=ServiceBindingManager">
<attribute name="ServerName">ports-01</attribute>
<attribute name="StoreURL">${jboss.home.url}/bpo-bindings.xml</attribute>
<attribute name="StoreFactoryClassName">
org.jboss.services.binding.XMLServicesStoreFactory
</attribute>
</mbean>