Table of contents

Installation

The tools are provided in a tar file that must be extracted into the /opt/charon/utils folder.

• If the folder does not exist, by default created at Charon installation, create it and copy the tar file in this directory. In the example below, we assume the tar file was downloaded in the /charon folder:

  # mkdir -p /opt/charon/utils # cp /charon/charonCharon-PAR_linuxLinux_toolkitToolkit.V1.544.tar /opt/charon/utils

  .

• Extract the files from the tar file to the Charon installation directory, subdirectory ‘utils’

  # cd /opt/charon/utils # tar –xf charonCharon-PAR_linuxLinux_toolkitToolkit.V1.544.tar

  .

• Execute the installation script:

  # ./menusetup

  .

• The setup will check first your terminal settings, if set to VT100 you will not be able to continue until you set the TERM value to VT200, dtterm or xterm (see how to here: Configuration)

...

• Mandatory and recommended packages installation will be checked.
  • If some mandatory packages are missing you will not be able to continue.
  • If some recommended packages are missing, installation will continue. Installation of these packages can be done later if needed

...

• The 'menu', 'logtail', 'logview', 'vmlist', 'vmstart', 'vmstop', 'vmconsole' and 'vmlistvmcfg' aliases will be created. They will be the commands you'll use to access the menu or to view and manage virtual machines states and log filesusing command lines.

• Preferences can be defined during the setup or later, they are related to the default editors used with text and graphical user interfaces, Out Of Memory (OOM) Killer settings and continuous log view when starting a guest (virtual machine)

...

• Alerts parameters will now have to be filled (see Alerts management chapter for more if needed)
  
  • Select between HTML or pure TEXT emails
  • Mail recipients list (used for alerts, not for sending files like log and configuration files for example)
  • Mail sender (can be used to change the displayed name of the sender)
  • Customize emails footer: if needed, add here your disclaimer, information on the CHARON Charon server or any information you think useful
  • Enable/disable wall alert messages
  • Install or update the alert script. It can be customized later, in this case it is recommended to do this once the virtual machines are installed

  • Select the alert level from guests log files: 0 = none, 1 = informational+warning+error entries, 2 = warning+error entries (default), 3 = error entries only

  • View alerts if any

  • Enable or disable license expiration alerts from guests logs: 1 alert per hour if enabled, 1 (default) or more alerts per day as defined per the recursive jobs settings

  • Send immediate alert on dongle removal or not (with counter alert)

  • The alerts simulator can be used to send all the know alerts via email (for checks)

  • Reduce the number of warning messages sent on dongle removal or not
    

    Example:

    

     

• When the setup is completed, either log out and login again to define the command aliases or execute the following command:

  # . /etc/profile.d/charon_menu.sh

  
  

...

...

Upgrade

...

Except if mentioned in the release notes, an upgrade does not require the Charon virtual machines to be stopped.

To upgrade the kit, you will need to:

• read the release notes available here:

...

• Charon-PAR Linux Toolkit - Current version
  .

• copy and extract the files from the tar file to the CHARON installation directory, subdirectory ‘utils'.

  
  

  # cd /opt/charon/utils # tar –xf

...

• Charon-PAR_

...

• Linux_

...

• Toolkit.V1.

...

• 4.tar

  
  

  .

• To install newly defined aliases (logtail, logview, vmlist, ...), please run the following command:

  
  

  # cd /opt/charon/utils (if not already done) # ./menusetup -a

  
  

  then either logout or execute the following command for the changes to take effect:
  

  
  

  # . /etc/profile.d/charon_menu.sh

  
  

  .

You can then run the 'menu' command as usual

...

In case of upgrade from a kit older than 41 on a CentOS 7 or Red Hat Enterprise Linux 7.x system, you must first stop all services, including the virtual machines running, and remove the services that were defined using the previous method as described below:

List installed services

Remove installed services

Once these services are removed, you can perform a standard kit upgrade

...

.

Please refer to release notes for post upgrade operations. The operations to perform are detailed in the release notes. Usually upgrades can require the log monitoring services to be restarted and/or the alert script to be re-installed.