Getting Started on Deevnet IoTaaS

Before You Start

Mon, 01 Jan 0001 00:00:00 +0000

Before You Start #

What to bring #

A Mac or a Linux laptop, and your own SD card if you’ll take your backend home. Everything below can be installed before the meetup. At the meetup, the provider, Terraform, Pi Imager, MicroPython and the take-home image come from the site’s tenant downloads rather than the venue’s internet.

From the operator, at admission:


An enrollment token	one-time, bound to your tenant name, valid 72 hours
The API endpoint	`https://api.mobile.deevnet.net:8080`
The `DVNTM-TD` Wi-Fi key	the network you work from ( below)
The site CA	`site-ca.pem`, the certificate authority for everything Deevnet serves over TLS. Check its SHA-256 fingerprint: `ED:ED:43:04:B8:40:8A:CE:14:FE:B8:AB:6C:B6:43:BC:A5:56:84:E8:26:A3:C2:75:CD:BD:EB:70:DF:E5:2D:5C`

Tools #

Required to apply your Terraform:

Admission

Mon, 01 Jan 0001 00:00:00 +0000

Admission #

A tenant starts with a name, and the operator admitting it. That is the only thing the operator does for you; everything after it you do yourself.

Pick a name #

1 to 8 characters, lowercase letters and digits, starting with a letter — ^[a-z][a-z0-9]{0,7}$
It becomes your DNS zone (<name>.mobile.deevnet.net), your MQTT topic prefix (<name>/…) and the name of your network. Pick something you will not mind seeing everywhere
sensors, bench1, ptv are fine; Pico-Demo and meetupproject are not

Ask the operator #

Tell the operator the name. They run one API call ( Tenant Admission) and hand you three things:

First Apply

Mon, 01 Jan 0001 00:00:00 +0000

First Apply #

Lay out a repository #

A tenant is code in its own repository ( ADR-0006). Two layouts work:

A tenant repository of its own, like the reference tenant deevnet-tenant-tdemo — copy it and change the name
Inside your application’s repository, at infra/deevnet-tenant-<name>/, beside the firmware. EdS and Ma Bell do this, so the device and the infrastructure it depends on change together

Either way:

deevnet-tenant-<name>/
├── main.tf
├── site-ca.pem # from the operator; gitignored is fine, it is not secret
├── .gitignore # *.tfstate*, .terraform/
└── Makefile # optional; tdemo's sets the endpoint and CA for you

The minimum: one resource #

terraform {
 required_version = ">= 1.5"
 required_providers {
 deevnet = { source = "deevnet/deevnet", version = "~> 0.4" }
 }
}

# Reads DEEVNET_API_ENDPOINT, DEEVNET_API_TOKEN, DEEVNET_API_CACERT
provider "deevnet" {}

resource "deevnet_tenant" "this" {
 name = "bench1" # exactly the name you were admitted with
}

output "api_token" {
 value = deevnet_tenant.this.api_token
 sensitive = true
}

Everything else — workloads, names, Wi-Fi keys, devices, broker accounts — hangs off deevnet_tenant.this.name and is added to this same configuration later.