Setup
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 and kit number is 42:# mkdir -p /opt/charon/utils
# cp /charon/charon_linux_toolkit.kit42.tar /opt/charon/utils
.
Extract the files from the tar file to the CHARON installation directory, subdirectory ‘utils’
# cd /opt/charon/utils
# tar –xf charon_linux_toolkit
.kit42
.tar.
In order to activate the ‘menu’ command, execute the following command:
# ./menusetup
.
- The setup will check first your terminal settings
- if set to
VT100
you will not be able to continue until you set theTERM
value toVT200
, dtterm or xterm (see how to here: Configuration)
- if set to
- Mandatory packages installation will be checked (
telnet
,screen
, etc..): if one package is missing you will not be able to continue. - If telnet is installed, you will be prompted to force the mode to character to avoid some input issues while connected to the guests console
- Recommended packages installation will be checked (
expect
,evince
, etc...): if one package is missing you will be able to continue, installation of these packages can be done later if needed - The '
menu
' alias will be created, this will be the command you'll use to access the menu - Recursive jobs will be added in the
crontab
file:- if the
crontab
file does not exist, it will be automatically filled - if it already exists, you will be prompted to update it via the selected editor: a check will be performed and the missing entries will be added
- if the
- Alerts parameters will now have to be filled
- Select between HTML or pure TEXT emails
- Mail recipients list (used for alerts, not for sending files like log and configuration files for example)
- Customize emails footer: you can add here your disclaimer, information on CHARON server or any information you think useful
- Enable/disable wall alert messages
- Install or update the alert script (can be customized later)
Select the alert level from guests log files: 0 = none, 1 = informational+warning+error entries, 2 = warning+error entries, 3 = error entries only
Example:
For more see: Alerts management
.
When the setup is completed either log out to activate the '
menu
' alias or execute the following command:# . /etc/profile.d/charon_menu*
.
The Interface Configuration Files (ifcfg
) will have to be created/updated manually before starting a guest using the related network cards. See the CHARON products related documentation, Installation part and Network configuration chapter. Please note the NIC name and the corresponding "ifcfg-xxx
" name file will have to be identical to run with the Toolkit, see How to customize network interfaces on Linux
Upgrade
To upgrade the kit, you will need:
- to read the CHARON Linux Toolkit - Release notes for kit 42 document
Copy and extract the files from the tar file to the CHARON installation directory, subdirectory ‘
utils
'# cd /opt/charon/utils
# tar –xf charon_linux_toolkit
.kit
<newkit>
.tar ..
- You can then run the '
menu
' command as usual
In case of upgrade from a kit older than 41 on a Fedora or Red Hat 7 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
# chkconfig --list | grep charon
charon_gstart 0:off 1:off 2:off 3:on 4:on 5:on 6:off
charon_logchk 0:off 1:off 2:off 3:on 4:on 5:on 6:off
Remove installed services
# chkconfig --del charon_gstart
# chkconfig --del charon_logchk
Once these services are removed, you can perform a standard kit upgrade
Services will have to be redefined or updated from the 'menu
', they will then use the 'systemd
' features
© Stromasys, 1999-2024 - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described.