Versions Compared

Old Version 20

changes.mady.by.user Max Millrose

Saved on

compared with

New Version Current

changes.mady.by.user Sebastian Koch

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column
width400px

Introduction

This guide describes what steps have to be taken when a customer wants to install Site Controller Version 1.3 on a running system, which is already connected to the azeti Engine. There is no automatic upgrade for version 1.2 to 1.3. Instead the customer has to do a fresh installation and migrate the existing configuration, as there have been structural changes in 1.3 that avoid an automatic approach. This guide explains the steps necessary and gives some guidelines on things to keep in mind. 

 

Info

This update guide is intended for standard linux OS like Ubuntu. Other platforms, like Cisco IOX and GOS,  require different steps to do the upgrade.

Column
width400px
Panel
borderColorlightgrey
bgColor#f0f0f0
titleOn this page:

Table of Contents

Related pages:

  • Filter by label (Content by label)
    showLabelsfalse
    showSpacefalse
    sortcreation
    cqllabel = "getting-started" and space = currentSpace()

...

  • The file 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

  • Modules can be defined to autostart in SiteController.cfg or the SensorConfig
  • A new major module is the data_store. This module now takes over the tasks of hd2cloud exporter & cloud connector
  • Status-Command of Site Controller does now include the status of the connection to the external broker and port used / configured
  • Various bugfixes and improved stability 
    • data_store is able to repair a single DB-corruption (Please note: second DB-corruption will break the Site Controller and a manual restart is mandatory)
    • XML-parsing is more robust

Abstract

This 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.

...

Info

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: Get StartedQuick Start to the Engine

Prerequisites

  1. The customer needs access to the corresponding azeti Control Panel and admin-rights for her / his account
  2. The customers needs ssh-access for the system, which is to be updated.
    1. It is also possible to transfer data (e.g. the installer) via other methods, depending on the system, but this guide will focus on SSH-based access
  3. Installer-Tar.gz for SiteController-1.3 (can be requested in the online Service Desk)
  4. The customer needs to know, where the current version of Site Controller is installed. By default this should be /opt/azeti/SiteController/, but some systems might differ.

...