Sv translation | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Introduction A jtel ACD consists of a minimum 2 of virtual machines and may grow to sizes of 30 or more, in concurrence with for example redundancy or performance requirements. Based on a systems architecture, there are certain dependencies between the services, so a clean startup and shutdown is required and only done in a certain order to prevent problems during and after startup. The following page describes the various possible scenarios for proper shutdown and startup procedures, depending on the systems architecture.
Page Layout This page is split into three rows, each named after a different type of sizing. The sizing variants are Small, Medium and Large General
Dependencies All services of the platform are dependent on two central entities:
To boot the solution, the storage should always be booted first. If this is external to the solution, continue with the next step. Otherwise, the computer (or in case of redundancy - both computers) is started on which the storage is located. This is usually the load balancer, but for larger systems a separate storage machine could have been implemented. Afterwards, the master database is booted. As soon as its is finished, the slave can be started up. Finally, the telephony servers and web servers can be started up in any order, even simultaneously. Small Small V1
Small V2
Small V3
Shutdown Dependencies for Small, Medium and Large systems Small V1 The two computers should be shutdown in the correct orderFirst shutdown acd-tel. You do not have to wait until acd-tel is shutdown fully down before starting the shutdown on at acd-store/lb/dbm/dbs/dbr/jb, but the order should be kept anyhow. Small V2 First shutdown acd-tel. You do not have to wait until acd-tel is down before starting the shutdown at acd-dbm/dbs/dbr. Wait for acd-dbm/dbs/dbr to be shutdown before starting the shutdown on acd-store/lb/jb. Small V3 First shutdown acd-tel and acd-jbN in no particular order. You do not have to wait until acd-tel and acd-jbN are down before starting the shutdown at acd-dbm/dbs/dbr. Wait for acd-dbm/dbs/dbr to be shutdown before starting the shutdown on acd-store/lb. Medium V1 First shutdown acd-tel and acd-jbN in no particular order. You do not have to wait until acd-tel and acd-jbN are down before starting the shutdown at acd-dbs/dbr. Wait until acd-dbs/dbr is shutdown before starting the shutdown on acd-dbm. Wait until acd-dbm is shutdown before starting the shutdown on acd-store/lb. Medium V2 First shutdown acd-tel and acd-jbN in no particular order. You do not have to wait until acd-tel and acd-jbN are down before starting the shutdown at acd-dbs/dbr. Wait until acd-dbs/dbr is shutdown before starting the shutdown on acd-dbm. Wait until acd-dbm is shutdown before starting the shutdown on acd-lb. Wait until acd-lb is down before starting the shutdown on acd-store Large V1 When shutting down a redundant database architecture, the inactive machines are shutdown first. Therefore, before a shutdown procedure can begin, the active machines must be known. The table at Large V1 assumes that acd-XXX dbm2 is currently the active master database and displays the shutdown procedure according to that. Large V2 When shutting down a redundant load balancing architecture, the inactive machines are shutdown first. Therefore, before a shutdown procedure can begin, the active machines must be known. The table at Large V2 assumes that acd-XXX lb2 is currently the active load balancer and displays the shutdown procedure according to that. Large V3 When shutting down a redundant storage architecture, the inactive machine is shutdown first. Therefore, before a shutdown procedure can begin, the active machine must be known. The table at Large V3 assumes that acd-XXX store2 is currently the active load balancer storage and displays the shutdown procedure according to that. Medium Medium V1
Medium V2
Startup Dependencies for Small, Medium and Large systems Small V1 The two computers must be started in the correct order. Wait until acd-store/lb/dbm/dbs/dbr/jb is up before starting acd-tel. Small V2 First start acd-store/lb/jb and wait until it is up. Start acd-dbm/dbs/dbr and wait until it is up. Start acd-tel afterwards. Small V3 First start acd-store/lb and wait until it is up. Start acd-dbm/dbs/dbr and wait until it is up. Start acd-jbN and acd-tel afterwards in no particular order. Medium V1 First start acd-store/lb and wait until it is up. Start acd-dbm and wait until it is up. Start acd-dbs/dbr and check the MySQL replication status after it is up. Start acd-jbN and acd-tel afterwards in no particular order. Medium V2 First start acd-store and wait until it is up. Start acd-lb and wait until it is up. Start acd-dbm and wait until it is up. Start acd-dbs/dbr and check the MySQL replication status after it is up. Start acd-jbN and acd-tel afterwards in no particular order. Large V1 First start acd-store and wait until it is up. Start acd-lb and wait until it is up. Start acd-dbm and wait until it is up. Start acd-dbs/dbr and check the MySQL replication status after it is up. Start acd-jbN and acd-tel afterwards in no particular order. Large V2 Large V3 When starting a Small or Medium system,
Checks
Large Large V1 - Redundant Databases
Large V2 - Redundant Databases + Load Balancing
Large V3 - Redundant Databases + Load Balancing + Storage
Startup Dependencies for Large Systems Shutting down redundant clusters is easier than starting them back up. Some components must be checked directly after starting up, before work can continue. Database:
Load Balancing:
Storage:
Startup and Shutdown - Redundant componentsIf the entire system is shut down, some components may not be immediately available or manual intervention may be necessary. Storage (Redundant) - CentOS
Shut down (only one)Always shut down one after the other. With:
determine which node is Primary. On the Secondary Node:
Then shut down the Primary Node.
Boot up (only one)After booting the Secondary Node, check the status. It should be Secondary and UpToDate
Check Sync status with :
After the sync is done, if necessary, and is ready:
Check status with: It should be Primary/Primary + UpToDate/UpToDate
Shut down (both)With:
determine which node is active (the node on which Samba and the virtual IP is running). This is the Primary Node. Set the secondary Node to secondary with:
On the Secondary Node first, then Primary:
Start up (both)Boot the Primary Node first Check DRBD sync Status and pcs cluster status Check with:
The Primary Node should be primary, and Secondary Node should be secondary. Disc should be UpToDate Then on Secondary Node
Check with:
Both nodes should be set to Primary/Primary + UpToDate/UpToDate Then check if everything works a final time:
|
...