Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...


Section


Column
width400px

Introduction

TODO: Deployments

The Config and Provisioning is one of the most critical parts of the Administrators tasks, as it deals with the the configuration of the sensors on all sites. The tasks included here are:

  • Configure and deploy the sensor templates that will be running on all sites
  • Manage software updates
  • Make changes on the sites software basic configuration.


Column
width400px


Panel
borderColorlightgrey
bgColor#f0f0f0
titleOn this page:

Table of Contents



Templates

Definition, Types and Structure

Templates are xml files which contain all the sensor configuration for all the sensors. This includes sensors, actions, rules and everything the azeti SiteController is programmed to do. This file will later be deployed to each site.

...

All the changes done to a template are inherited to the templates below them. So if a sensor inside component instance is edited, all the site templates and locations templates that use it will be edited as well automatically. The exception being those changes that were done directly on the lower template. So if, for example, sensor X state threshold is changed on a site template, and then on a component instance, the change done directly on the site template will take precedence, and the change done on the component instance will not be applied.

Using Components and Components instances

The first step to create a template would be to upload one:

  1. Go to Configuration → Management→ Templates → Component TemplatesComponents
    Image RemovedImage Added
  2. Click the +Add button
  3. Choose the file and click upload


...

After the component template is uploaded, a component instance that uses is it can be created:

  1. Go to Configuration →  Management→ Templates → Component Instances
    Image RemovedImage Added
  2. Click  +Add to create a new instance
  3. Select the component which will be the base for the component instance. Change the name of the instance if needed and click Add to create it, or Add and Edit to create it an go directly to the edit page.

...

To edit or create a site template go to Configuration → Management → Templates Site Templates

Each templates shows:

...

To manage the system configurations go to Configuration → System Config Management→ Configigurations

To create a new one:

  1. click +Add
  2. Select the base component for the config. This are the Site Controller packages that are uploaded to the cloud (see Controller Software section). They have to be upload before creating the system config.
  3. Click + Next
  4. Edit the system config name and click + Create Template

...

This will show all the sections of the configuration file as a tree, with the values on the left side. To change this values click 

Controller Software

For the deployments, jobs, updates and validations to be done correctly, the correct version of the site controller has to be uploaded to the server. To see which ones are already uploaded go to Configuration → Controller Management→ Software → Software Packages.

Image RemovedImage Added

The list shows all the site controller packages that have been uploaded, with the all the details and the possibility to download it. 

...