| 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 V1 Machine
First | Last
Last | First
Small V2 Machine |
First | Last
Second | Second
Last | First
Small V3 Machine
First | Last
First |
Last | First | Start UpOrderA non-redundant solution is assumed in the following. The operation of a redundant solution requires extra schooling. This results in the following starting order:
Checks
ShutdownOrderShutting down is done in the reverse order:
It is not absolutely necessary to wait between the individual steps, just step 1 should be completed before continuing. Medium V1 Machine | Shutdown | Startup | acd-tel | First | Last | acd-jbN | First | Last | acd-dbs/dbr | Second | Second | acd-dbm | Third | Third | acd-store/lb/ | Last | First | Medium V2 Machine | Shutdown | Startup | acd-tel | First | Last | acd-jbN | First | Last | acd-dbs/dbr | Second | Second | acd-dbm | Third | Third | acd-lb | Fourth | Fourth | acd-store | Last | First |
Shutdown Dependencies for Small, Medium and Large systems Small V1 The two computers should be shutdown in the correct order. You do not have to wait until acd-tel is shutdown fully before starting the shutdown on 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 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 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 is currently the active load balancer and displays the shutdown procedure according to that. 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 Large V2 Large V3 When starting a Small or Medium system,
Checks
Large V1 - Redundant Databases
Large V2 - Redundant Databases + Load Balancing
Shutdown/Startup 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:
Large V1 - Redundant Databases 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 following table assumes that acd-dbm2 is currently the active master database. Machine | Shutdown | Startup | acd-telN | First | Last | acd-jbN | First | Last | acd-dbs1/dbr1 | Second | Second | acd-dbs2/dbr2 | Second | Second | acd-dbm1 | Third | Third | acd-dbm2 | Third | Third | acd-lb | Fourth | Fourth | acd-store | Last | First | Large V2 - Redundant Databases + Load Balancing Please view above for database shutdown. 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 following table assumes that acd-lb2 is the active load balancer. Machine | Shutdown | Startup | acd-telN | First | Last | acd-jbN | First | Last | acd-dbs1/dbr1 | Second | Seventh | acd-dbs2/dbr2 | Third | Sixth | acd-dbm1 | Fourth | Fifth | acd-dbm2 | Fifth | Fourth | acd-lb1 | Sixth | Third | acd-lb2 | Seventh | Second | acd-store | Last | FirstLarge V3 - Redundant Databases + Load Balancing + Storage Please view above for database and load balancer shutdown. 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 following table assumes that acd-store2 is the active 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:
|
...
| Sv translation | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Démarrage et fermetureTous les systèmes sont conçus pour démarrer et faire démarrer tous les services indépendamment. Toutefois, il existe certaines dépendances entre les services, de sorte qu'un démarrage et un arrêt propres sont mieux réalisés lorsqu'une certaine commande est envisagée. DémarrageDépendancesTous les services de la plate-forme dépendent de deux entités centrales :
Pour démarrer la solution, le stockage doit toujours être démarré en premier. Si cela est externe à la solution, passez à l'étape suivante. Sinon, l'ordinateur (ou en cas de redondance - les deux ordinateurs) est démarré sur lequel se trouve le stockage. Il s'agit généralement de l'équilibreur de charge, mais pour les systèmes plus importants, une machine de stockage distincte aurait pu être implémentée. Ensuite, la base de données principale est lancée. Dès qu'elle est terminée, l'esclave peut être démarré. Enfin, les serveurs de téléphonie et les serveurs web peuvent être démarrés dans n'importe quel ordre, même simultanément. OrdreUne solution non redondante est supposée dans ce qui suit. Le fonctionnement d'une solution redondante nécessite une formation supplémentaire. Il en résulte l'ordre de départ suivant :
Vérifications
ShutdownOrdreLa fermeture se fait dans l'ordre inverse :
Il n'est pas absolument nécessaire d'attendre entre les différentes étapes, il suffit de terminer l'étape 1 avant de continuer. Démarrage et arrêt - Composants redondantsSi l'ensemble du système est arrêté, certains composants peuvent ne pas être immédiatement disponibles ou une intervention manuelle peut être nécessaire. Storage (Redundant) - CentOS
Arrêt (un seul)Toujours fermer l'un après l'autre. Avec:
déterminer quel nœud est Primaire. Sur le Nœud Secondaire :
Ensuite, arrêtez le Noeud Primaire.
Démarrer (un seul)Après avoir démarré le Noeud Secondaire ,vérifiez son état. Il doit être secondaire et actualisé.
Vérifiez le statut de sync avec :
Après la synchronisation est fait, si nécessaire, et est prêt :
Vérifiez le statut avec : Il devrait être Primaire/Primaire + UpToDate/UpToDate
Arrêter (les deux)Avec:
déterminer quel nœud est actif (le nœud sur lequel Samba et l'IP virtuel fonctionnent). C'est le Nœud primaire. Définissez le nœud secondaire comme secondaire avec :
Sur le nœud secondaire d'abord, puis le Primaire :
Démarrage (les deux)Démarrer le Noeud Primaire d'abord Vérifier l'état de la synchronisation DRBD et l'état du cluster pcs. Vérifier Avec
Le Noeud primaire devrait être primaire, et le Noeud Secondaire devrait être secondaire. Le disque doit être UpToDate Puis, sur le Nœud Secondaire
Vérifier Avec
Les deux noeuds doivent être réglés sur Primaire/Primaire + UpToDate/UpToDate Vérifiez ensuite si tout fonctionne : pour la dernière fois :
|