Sv translation | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
RequirementThe system must first be updated to a version with MySQL 8.x (Release 3.15 to 3.17). Preparation for the updateWith every update there is a golden rule that must be strictly followed regardless of the customer's wishes:
Determine Authoritative ShareIn some installations, the file share is on a system provided by the customer. In this case, the repositories are checked out locally to the load balancer on the non-authoritative share, but the files are later copied to the "authoritative" file share. After changes should be checked for the Authoritative File-Share. Authoritative File-ShareThis is /home/jtel/shared Non-Authoritative File-ShareThis is /srv/jtel/shared Determine if AuthoritativeIf /home/jtel/shared is mounted on the load balancer from a third-party system, it is usually not authoritative. You can easily determine this by creating a file on /srv/jtel/shared. If this does not appear in /home/jtel/shared, then /srv/jtel/shared is not authoritative. Data backupA data backup should unconditionally be made. The MINIMUM is that the database is backed up and the data directory is backed up, but this should only be a stopgap solution. Better is a snapshot of all virtual machines involved, in cold state (shut down). There is a risk that if a snapshot is taken during operation (especially of the database machines), it may not be consistent. Manual backupDienste Stoppen
Backup database (on DB master)Enter the corresponding password at <password>:
Backup Data DirectoryThis can be done via the Windows Explorer or a corresponding cp command on the Linux. Remember GIT status (Authoritative Share)From the load balancer, check the GIT status:
If necessary, the directories must also be included in the data backup, especially if patches have been applied so that local changes have been made. Securing additional componentsIf other components are affected by the update, such as the 8 server itself, or the JBOSS server (not the web application), these components should also be backed up in advance. Snapshot BackupThis is done via the VMWare console, or Hyper-V console. This is usually done by the customer. Confirmation
RestoreSnapshotsThe snapshots are all reactivated and booted. There should be normal operation with the old software. Manual RestorationWith all services stopped, restore the database. Enter the corresponding password at <password>:
In parallel, the old data directory can be restored. Further steps may be necessary (restore GIT repositories, restore 8 servers, ...) depending on which components were affected by the update.
The updating of the systemIt should be mentioned again: all jtel services of the system must be shut down. After that the update can be started. The steps are performed in the order documented here Updating the software on the STOREThis step must be performed as user "jtel".
Check if changes / patches are availableBefore updating the software, you should check whether files in the respective directory have been changed.
Here is an example based on the software directory JTELCarrierPortal
If this indicates that files have been modified, caution is advised. The project engineer must first check whether the changes are local bug fixes that have been incorporated into the release. If this is the case, the changes can be deleted before updating. If this is not done, the update may fail!
However, a general procedure cannot be described in such a case. In this case, the procedure must be checked on a case-by-case basis. If file mode changes should be ignored, the following command can be used:
Updating the repositories (always on non-authoritative share)The following command sequence updates all software directories to the latest version of the respective chosen release.
If errors occur in GIT, for example: Merge-Conflict in (file name) Oder fatal: Deny the merge of unrelated histories. the local repository must be reset. This can be done as follows (example for stable-3.18 on JTELCarrierPortal)
Checking out the desired releaseAfter the GIT PULL is done, the corresponding release must be checked out if a release other than git status is desired.
Copy files to Authoritative ShareOnly if there is an Authoritative / Non-Authoritative share. This is done with the following script
Run update scriptsThe following update script makes all necessary changes. This is executed as root or jtel with sudo. Here with jtel user:
You may be asked for the sudo password first. The script asks for the corresponding master database, user, password, and name of the customer directory where specific software for the customer may be located. The questions can be answered, usually with the following answers, knowledge of <password> for the database assumed:
If there is no customer directory, this can be left empty. The presence of custom software can be checked with ls /home/jtel/shared - there you can see the names of the directories. Enter only the name of the directory! For example acme The update is then carried out.
Download BinariesThe binaries are downloaded with the following command:
Update of the Platform UDP ListenerMaster DatabasesWith release 3.18 and higher, Java 8 is used. The (existing) Java 7 must be uninstalled and Java 8 will be installed. We use the openjdk so that it remains updateable under Linux.
The update of the Platform UDP Listener must be executed as user "root" and is performed on the master databases by entering the following command:
This command updates the listener and starts it. The success can be checked by viewing the file /home/jtel/PlatformUDPlistener/log/listener.log.
Telephony serversHere you have to check if Java 8 is installed. If necessary, download Java 8 from one of the sources here (these are BCL licensed versions, i.e. license-free):
The start script for the platform listener copies the new version of the listener itself.
Updating the WEB serversThe JBOSS server is completely replaced by a Wildfly server. Backup Hazelcast configurationIf no backup already exists:
Uninstalling JBOSS Server and Java 7As root:
Install Java 8 and Wildfly
Configure WildflyThe hazelcast.xml must be copied and the default settings for the database must be adjusted. In the following replace <password> please accordingly:
Updating the portal softwareThe update of the portal software must be executed as user "root" on the web server and is done by entering the following command:
This command updates the portal software and starts the wildfly server. The success can be checked by viewing the file /home/jtel/wildfly-current/standalone/log/server.log. There you should see the following entries in the log file if the update was successful: Update of the 8ServerThe 8Server is updated in Windows Explorer using GIT. To do this, right-click on the directory C:\8Server\deploy to perform a GIT pull and switch to the desired version after the pull.
If you do not want to update to the last version, but to a specific version, you can do this via "git checkout", by indicating the release. After updating, the version must then be installed. For a daemon server, this is done with the command:
For a telephony server with Aculab Media Service, this is done with the following command:
Afterwards the 8Server can be started. Updating the connectorsBasically: the corresponding files from the software directory in the STORE must be copied into the target directory. These usually come from JTELCarrierPortal/WebServices/Install
Final workOnce the update has been completed and the system restarted without errors, the following tasks must be performed:
|
...