Difference between revisions of "M2MBridge updates"

From AMTech WikiDocs
Jump to: navigation, search
Line 1: Line 1:
 
* M2MBridge updates are managed from the amtechM2mBridge template thing and the cloned amtechM2mBridge instance used in the configuration of the M2MBridge.  
 
* M2MBridge updates are managed from the amtechM2mBridge template thing and the cloned amtechM2mBridge instance used in the configuration of the M2MBridge.  
* Once a new M2MBridge image is flashed into a Raspberry Pi and the M2MBridge is configured following [Edge Configuration#Bridge Configuration|this form], a pre-execution script will run to download the M2MBridge version specified in the configured template.
+
* Once a new M2MBridge image is flashed into a Raspberry Pi and the M2MBridge is configured following [[Edge Configuration#Bridge Configuration|this form]], a pre-execution script will run to download the M2MBridge version specified in the configured template.
 
: ''Important remark'': Note that this first time you run the bridge, you need to be sure that the bridge has a configured Internet connection and the configured template has a valid version set. Otherwise the download will fail and the M2MBridge will not start.  
 
: ''Important remark'': Note that this first time you run the bridge, you need to be sure that the bridge has a configured Internet connection and the configured template has a valid version set. Otherwise the download will fail and the M2MBridge will not start.  
 
* After this initial setup, the service is started and a clone of that template is generated with the same version specified in the template.
 
* After this initial setup, the service is started and a clone of that template is generated with the same version specified in the template.
 
* Any further change to that instance version will be honored by the bridge and an over-the-air update will be applied with a consequent restart of the M2MBridge service.
 
* Any further change to that instance version will be honored by the bridge and an over-the-air update will be applied with a consequent restart of the M2MBridge service.

Revision as of 13:44, 19 April 2018

  • M2MBridge updates are managed from the amtechM2mBridge template thing and the cloned amtechM2mBridge instance used in the configuration of the M2MBridge.
  • Once a new M2MBridge image is flashed into a Raspberry Pi and the M2MBridge is configured following this form, a pre-execution script will run to download the M2MBridge version specified in the configured template.
Important remark: Note that this first time you run the bridge, you need to be sure that the bridge has a configured Internet connection and the configured template has a valid version set. Otherwise the download will fail and the M2MBridge will not start.
  • After this initial setup, the service is started and a clone of that template is generated with the same version specified in the template.
  • Any further change to that instance version will be honored by the bridge and an over-the-air update will be applied with a consequent restart of the M2MBridge service.