|
Some of the major changes in 1.3.0 include:
azeti_logging.cfg
is obsolete. All logging-related settings are now integrated into SiteController.cfg
As a result SiteController.cfg
is not compatible between 1.2 and 1.3 - hence a real upgrade is not possible
SiteController.cfg
or the SensorConfigThis guide describes how to remove the currently installed Site Controller in version 1.2 and do a fresh install with the version 1.3 of the Site Controller. After the new version has been installed, the customer will re-apply custom changes from the old installation. An automated approach has not yet been tested to a statisfactory result, therefore the manual approach has to be taken.
This guide will focus on SSH as the means of connecting to system which runs Site Controller. Other means are of course possible and this guide should also apply to them.
Please note, that this guide assumes you have already used the azeti Control Panel in combination with Site Controller. If you are absolutely new to these topics, please refer to this guide instead: Quick Start to the Engine |
Add the steps involved:
/opt/azeti/SiteController/
, but some systems might differ.Copy the installer-Tar.gz for Site Controller in version 1.3 onto the system, which will be upgraded.
scp Installer.tar.gz user@systemIP:. |
Connect to the system, which will be updated.
ssh user@systemIP |
If you are not root yet, become root.
user@ubuntu1404MaxVM1:~$ sudo su [sudo] password for user: root@ubuntu1404MaxVM1:/home/user# |
Change into the directory where the current Site Controller (v1.2) is installed. By default this should be /opt/azeti/SiteController/
root@ubuntu1404MaxVM1:/home/user# cd /opt/azeti/SiteController/ |
Copy the current SiteController.cfg
to a location outside of this directory, because we are going to delete this directory later on.
root@ubuntu1404MaxVM1:/opt/azeti/SiteController# cp config/SiteController.cfg /home/user/old_SC.cfg |
If you made any changes to azeti_logging.cfg
you might also want to backup this file as well.
root@ubuntu1404MaxVM1:/opt/azeti/SiteController# cp config/azeti_logging.cfg /home/user/old_azeti_logging.cfg |
Stop the running Site Controller - doing this with root-rights is important!
root@ubuntu1404MaxVM1:/opt/azeti/SiteController# ./run_SiteController.py stop |
Change to the directory where the installer-Tar.gz resides.
root@ubuntu1404MaxVM1:/opt/azeti/SiteController# cd /home/user/ |
Remove the old directory of the 1.2-installation (keep in mind, that the location might be different for your system)
root@ubuntu1404MaxVM1:/home/user# rm -fr /opt/azeti/SiteController/ |
Extract the archive and change into the resulting new directory
root@ubuntu1404MaxVM1:/home/user# tar xf SiteController-install_1.3.0.tar.gz && cd SiteController-install/ |
Execute the script setup.sh
root@ubuntu1404MaxVM1:/home/user/SiteController-install# sh ./setup.sh |
Minor errors can be ignored. Should the installation completely stop, please inspect the output for errors. Otherwise it appears to be save to ignore them. |
During the Installation, you will be asked to provide a serial for the new installation.
If in doubt, please have a look at the serial defined in |
Navigate to the installation-directory of the new Site Controller.
root@ubuntu1404MaxVM1:/home/user# cd /opt/azeti/SiteController/ |
Use your preferred editor to open the file config/SiteController.cfg
.
root@ubuntu1404MaxVM1:/opt/azeti/SiteController# vim config/SiteController.cfg |
The following values have to be present, for any Site Controller to start and work:
Depending on your Site Controller configuration it can be necessary to add or tweak more aspects of the config (eg. RemoteExecutionJobs
or which Serial-Interfaces to use for ModBus-devices). Please reference your previously backed up SiteController.cfg
After your changes have been done, save and close the file
Restart the Site Controller (issue the command run_SiteController.py restart
with root privileges).
root@ubuntu1404MaxVM1:/home/user# cd /opt/azeti/SiteController/ root@ubuntu1404MaxVM1:/opt/azeti/SiteController# |
From the dropdown-menu select "Deployments"
Please ignore the fact that the cloud shows an already running SensorConfig for your newly installed Site Controller. The Site Controller only communicates his running config-revision to the cloud, when a new SensorConfig is deployed (new; changed or upgrade) only then sends a message to the cloud, that it has a running config. If the Site Controller is installed fresh, such a communication does not occur and hence the cloud assumes, that the old SensorConfig is still running. The cloud only takes into considaration the serial of the System not eg. the running version of SC. |
log/ConfigProvider.log
for the success of the deployment on your Site ControllerRelated articles appear here based on the labels you select. Click to edit the macro and add or change labels.