release(prod): 2021.11.11.0-1, ECC concurrency, initFile robustness, …

…and pktfwd rewrite (#215)

* test diag with new base image

test diag with new base image

* bump upnp for testing

bump upnp for testing

* fix: add depends on for packet forwarder

The packet forwarder actually requires the miner container to be able to accept connections on the hostname helium-miner before it will be able to start the concentrator.

This adds a depends_on to not attempt to start the packet forwarder container until the miner container is up

* Create docker-compose.yml

Bumps UPnP, config, diag and packet forwarder containers so they are now all using the same base image.

We need to now test that it's actually smaller so will leave #182 open for now.

* Bump to 2021.10.27.0_GA

Bump to 2021.10.27.0_GA

* Added documentation to the readme for quick start (#189)

Added documentation to the readme for quick start (#189)

* Bump to 2021.10.29.0_GA

Bump to 2021.10.29.0_GA

* Bump to 2021.11.02.0_GA

Bump to 2021.11.02.0_GA

* rearrange readme

rearrange readme

* Update README.md

* Bump diag and config

Bump diag and config

* feat: bump GA to 2021.11.04.2

* release: bump GA to 2021.11.10.0

* release: bump GA to 2021.11.11.0

* Add tech support to CODEOWNERS

Partially fixes #208

* fix: ECC locking and initFile (#209)

Lock ECC usage and ensure initFile always returns.

* build: bump firmware version

* bump(pktfwd): current master branch

Including likely unnecessary patch to regions.

Co-authored-by: Aaron Shaw <[email protected]>
Co-authored-by: Sebastian Maj <[email protected]>

.github/CODEOWNERS

@@ -3,5 +3,6 @@
 # @global-owner1 and @global-owner2 will be requested for
 # review when someone opens a pull request.
 *       @NebraLtd/developers
+*       @NebraLtd/tech-support
 
 # See example for more details: https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-code-owners#example-of-a-codeowners-file

README.md

@@ -44,6 +44,33 @@ Repo: [github.com/balenablocks/dbus](https://github.com/balenablocks/dbus)
 
 This container configures a DBus session bus instance that is used by the gateway config container to communicate with the miner code (note that there is also a separate system bus running on the host OS which is used by gateway config to communicate with bluez for configuring Bluetooth services). This removes the need to have a custom `com.helium.Miner.conf` dbus config file on the host OS as was done previously (and meant we had to run a custom balena device type).
 
+#  Quick Start
+
+This is a guide to help you get started with the repository and get it running on your local device. This guide is focused on pushing the repository onto a Raspberry Pi using Balena.
+
+**Prerequisites:**
+- Local Test Device (Ex: Raspberry Pi)
+- Computer for development and pushing to the device
+- Git installed - [download here](https://git-scm.com/downloads)
+- [Balena CLI](https://github.com/balena-io/balena-cli) (Install located on Balena step in quick start steps below)
+
+### Quick Start Steps
+
+**Step 1:** Clone the repository to your local machine using one of the following commands:
+- HTTP: `git clone https://github.com/NebraLtd/helium-miner-software.git`
+- SSH: `git clone [email protected]:NebraLtd/helium-miner-software.git`
+
+**Step 2:** Follow the [getting started guide](https://www.balena.io/docs/learn/getting-started/raspberrypi3/nodejs/) for Balena to help you install Balena on your local test device and get a fleet setup so you can start pushing code to it.
+
+**Step 3:** Once you've gone through the steps and have Balena setup with your device in your fleet, open your cli terminal and navigate to the root directory of the cloned repository (Ex: /usr/name/documents/helium-miner-software).
+
+**Step 4:** Once you're at the root directory. You want to push the code by running the following command:
+```bash
+$ balena push <fleet-name>
+```
+
+**Step 5:** Once complete check your fleet on the Balena dashboard and all modules should be running on the local test device.
+
 # Device Configuration / Fleet Configuration Notes
 
 For some Nebra Hotspots that use spidev1.2 you may need to add a DT overlay in the device or fleet configuration section on balenaCloud to enable spi1.

docker-compose.yml

@@ -3,12 +3,12 @@ version: '2'
 services:
 
   gateway-config:
-    image: nebraltd/hm-config:951749c
+    image: nebraltd/hm-config:8070d87
     depends_on:
       - dbus-session
       - diagnostics
     environment:
-      - FIRMWARE_VERSION=2021.11.11.0
+      - FIRMWARE_VERSION=2021.11.11.0-1
       - DBUS_SYSTEM_BUS_ADDRESS=unix:path=/host/run/dbus/system_bus_socket
       - DBUS_SESSION_BUS_ADDRESS=unix:path=/session/dbus/session_bus_socket
     privileged: true
@@ -25,7 +25,9 @@ services:
     stop_signal: SIGINT
 
   packet-forwarder:
-    image: nebraltd/hm-pktfwd:1213210
+    image: nebraltd/hm-pktfwd:3f7c41e
+    depends_on:
+      - helium-miner
     restart: always
     privileged: true
     volumes:
@@ -56,9 +58,9 @@ services:
       - RELEASE_BUMPER=foobar
 
   diagnostics:
-    image: nebraltd/hm-diag:d9ab173
+    image: nebraltd/hm-diag:12420cf
     environment:
-      - FIRMWARE_VERSION=2021.11.11.0
+      - FIRMWARE_VERSION=2021.11.11.0-1
     volumes:
       - pktfwdr:/var/pktfwd
       - miner-storage:/var/data
@@ -72,7 +74,7 @@ services:
       io.balena.features.sysfs: 1
 
   upnp:
-    image: nebraltd/hm-upnp:5672229
+    image: nebraltd/hm-upnp:9c18f02
     network_mode: host
     restart: on-failure
     volumes: