Difference between revisions of "Clouds manager"

From LORIX One - Wiki

Jump to: navigation, search
Line 10: Line 10:
  
  
The LORIX One gateway proposes a nice script to manage and choose the application you want to use by default. It allows as well to start automatically the selected application at boot time.
+
Each of these scripts have a init script which can be used to start, stop of get actual status of the application.
  
 +
However, since only one of them can be used at a time, the LORIX One gateway proposes a nice script to manage and choose the application you want to use by default. It allows as well to start automatically the selected application at boot time.
  
  
 
==Configuration and usage==
 
==Configuration and usage==
=== ===
 
 
===Status===
 
===Status===
 +
The clouds-manager script can be used to retrieve the actual status of the selected cloud client. To get this status, you can simply use the script as follow:
 +
 +
$ sudo /etc/init.d/clouds-manager.sh status
 +
The result on a stopped application cloud (with LORIOT selected):
 +
 +
$ sudo /etc/init.d/clouds-manager.sh status<br data-attributes="%20/" />Cloud loriot status:<br data-attributes="%20/" />/opt/lorix/clouds/loriot/loriot-gw is stopped
 +
And on a running instance:
 +
 +
$ sudo /etc/init.d/clouds-manager.sh status
 +
Cloud loriot status:
 +
/opt/lorix/clouds/loriot/loriot-gw (pid 969) is running...
 
===Start/stop===
 
===Start/stop===
 +
The clouds-manager scripts allows to start or stop the selected cloud client. To start, stop or restart, you can simple use the script as follow:
 +
 +
$ sudo /etc/init.d/clouds-manager.sh start
 +
Password: [enter your password here]
 +
Cloud loriot already running, abort.
 +
$ sudo /etc/init.d/clouds-manager.sh restart
 +
Stopping cloud loriot... stopped /opt/lorix/clouds/loriot/loriot-gw (pid 969)
 +
done.
 +
Starting cloud loriot... done.
 +
$ sudo /etc/init.d/clouds-manager.sh stop
 +
Stopping cloud loriot... stopped /opt/lorix/clouds/loriot/loriot-gw (pid 1043)
 +
done.
 
===Configuration===
 
===Configuration===
 +
The main goal of this cloud manager script is really to select which one of the available client you would like to use and to allow the possibility of automatic start at boot time.
 +
 +
By default, the LORIX One is configured to use the LORIOT client application and to start it at boot time.
 +
 +
Before modifying the parameters, you must stop the actual running cloud if any using the stop command:
 +
 +
$ sudo /etc/init.d/clouds-manager.sh stop<br data-attributes="%20/" />Stopping cloud loriot... stopped /opt/lorix/clouds/loriot/loriot-gw (pid 1104)<br data-attributes="%20/" />done.
 +
You can modify these parameters by using the script as follow:

Revision as of 16:13, 22 October 2017

Introduction

The LORIX One gateway is pre-installed with few cloud client applications. 


There is actually the following one:

  • LORIOT which is selected and started by default at boot time
    A great and powerful way of managing your gateways and objects
  • Semtech packet-forwarder 
    The official basic packet-forwarder made by Semtech, owner of the LoRa protocol
  • TTN (The Things Network) packet-forwarder 
    A nice community of LoRa enthusiast people. Based on the Semtech packet-forwarder


Each of these scripts have a init script which can be used to start, stop of get actual status of the application.

However, since only one of them can be used at a time, the LORIX One gateway proposes a nice script to manage and choose the application you want to use by default. It allows as well to start automatically the selected application at boot time.


Configuration and usage

Status

The clouds-manager script can be used to retrieve the actual status of the selected cloud client. To get this status, you can simply use the script as follow:

$ sudo /etc/init.d/clouds-manager.sh status

The result on a stopped application cloud (with LORIOT selected):

$ sudo /etc/init.d/clouds-manager.sh status
Cloud loriot status:
/opt/lorix/clouds/loriot/loriot-gw is stopped

And on a running instance:

$ sudo /etc/init.d/clouds-manager.sh status
Cloud loriot status:
/opt/lorix/clouds/loriot/loriot-gw (pid 969) is running...

Start/stop

The clouds-manager scripts allows to start or stop the selected cloud client. To start, stop or restart, you can simple use the script as follow:

$ sudo /etc/init.d/clouds-manager.sh start 
Password: [enter your password here]
Cloud loriot already running, abort.
$ sudo /etc/init.d/clouds-manager.sh restart
Stopping cloud loriot... stopped /opt/lorix/clouds/loriot/loriot-gw (pid 969)
done.
Starting cloud loriot... done.
$ sudo /etc/init.d/clouds-manager.sh stop 
Stopping cloud loriot... stopped /opt/lorix/clouds/loriot/loriot-gw (pid 1043)
done.

Configuration

The main goal of this cloud manager script is really to select which one of the available client you would like to use and to allow the possibility of automatic start at boot time.

By default, the LORIX One is configured to use the LORIOT client application and to start it at boot time.

Before modifying the parameters, you must stop the actual running cloud if any using the stop command:

$ sudo /etc/init.d/clouds-manager.sh stop
Stopping cloud loriot... stopped /opt/lorix/clouds/loriot/loriot-gw (pid 1104)
done.

You can modify these parameters by using the script as follow: