OpenHack – IoT Gateway Operations (IOTGO-OH)


Course Overview

This OpenHack enables attendees to learn the essentials of building, deploying, and operating IoT gateways on the edge. Attendees will learn the fundamental skills, default patterns and practices, and core technologies across the Azure portfolio that will accelerate their deployment of edge gateway solutions.

During the “hacking” attendees will focus on leveraging available tools/tasks in Azure DevOps to enable best-practice oriented scenarios such as:

  • IoT Edge Solution DevOps – CI/CD, Container Management, Marketplace and OSS offerings
  • IoT Edge Solution Production Operations – Watchdogs, Tracing, Logging, Monitoring, Metrics
  • IoT Solution Logging and Monitoring
  • Operations Dashboards
  • Gateway Host Management
  • Finding existing IoT Edge solutions across the Azure Marketplace and OSS ecosystems

This OpenHack simulates a real-world scenario where a leading provider of IoT system integration is launching its next generation of predictive maintenance and process optimization solution.

By the end of the OpenHack, attendees will have built out a technical solution that covers the fundamentals required to drive production readiness and operationalization of solutions built on Azure IoT offerings.

Course Content

Challenge 1: Device Streams for Gateway Host Management (Each Participant) (Buhler & Weir)

In this challenge, you will use Azure IoT Hub’s Device Streams feature to gain a secure remote shell to an IoT device. This is remote shell is a critical tool you can use to perform application updates, patching, security audits or other specific tasks.

Learning objectives:
  • Deploy an IoT “Device” as a service to a Virtual Machine
  • Enable Device Streams
  • Initiate SSH/RDP Session via Device Streams to VM
Challenge 2: Device Provisioning Service with Azure IoT Edge (Each Participant) (Cooler Screens, Buhler, Weir, Volpara)

The intent of this challenge is to continue to demonstrate the power and flexibility of Device Streams, while also familiarizing attendees with the configuration of the Azure IoT Hub Device Provisioning Service (DPS), installation of Azure IoT Edge and the configuration of Azure IoT Edge to leverage DPS.

Learning objectives:
  • Provision IoT Edge Device in DPS
  • Install IoT Edge with DPS configuration using Automatic Device Management via Device Stream
  • Device Tagging for Azure IoT Edge Devices
Challenge 3: Workload Build and Deployment Strategies for IoT Edge (Each Participant) (Weir, PTC, Rockwell)

The intent of this challenge is to get attendees familiar with the DevOps fundamentals for developing and deploying workloads to Azure IoT Edge.

Learning objectives:
  • Build all challenge assets using a continuous build approach
  • Deploy all assets using a continuous deployment approach
  • Use a simulator to push telemetry from Azure IoT Edge to Azure IoT Hub
Challenge 4: Forward Azure IoT Edge Metrics to Azure (Rockwell)

The intent of this challenge is to get participants thinking about performance and observability concerns for edge compute environments.

Learning objectives:
  • Build all challenge assets using a continuous build approach
  • Deploy all assets using a continuous deployment approach
  • Forward all IoT Edge metrics to operations dashboard in Azure
Challenge 5: Pull Azure IoT Edge Logs up to Azure (Marsden, Maersk, SLB)

The intent of this challenge is to get participants familiar with approaches to the management of hardware/firmware, OS and application logs for solutions leveraging Azure IoT Edge.

Learning objectives:
  • Upload IoT Edge container and service logs to Azure using a push or pull model
  • Run a query showing five (5) minutes of logs after the last IoT Edge solution restart
Challenge 6: Keeping a Pulse on Connectivity with a Watchdog (Weir, Buhler, Marsden, BNSF, Rockwell, Volpara)

The intent of this challenge is to get participants thinking about the complexity of running an IoT solution where intermittent network connectivity is of concern.

Learning objectives:
  • Use GitHub to find watchdog solution for IoT Edge
  • Build all challenge assets using a continuous build approach
  • Deploy all assets using a continuous deployment approach
  • Forward watchdog and tracing messages from IoT Hub to a time series database
  • Visualize five (5) minutes of watchdog messages in a dashboard
Challenge 7: Building an Operations Dashboard with Priority Alerts (Preview Feature – Buhler & Weir)

The intent of this challenge is to get participants thinking about how to both appropriately capture and conditionally route telemetry, and to create and present a dashboard that provides application level alerts in a timely manner.

Learning objectives:
  • Implement an IoT Edge module that sends distributed tracing messages (1/minute) through IoT Hub and onto a time series database
  • Use module twin update to enable/disable tracing messages remotely
  • Visualize message latency for tracing messages traveling from edge through cloud services

Technical Scenarios

The technical scenarios covered by this content are wide-ranging and applicable to Intelligent Edge solutions:

  • HMI: Human Machine Interface design and implementation in edge environments to give field solution operators local insights into the health and status of edge applications.
  • Cloud-based Operations: Dashboarding and command and control for globally distributed edge compute.
  • Complementary Code: A unifying pattern for running common business logic in both the cloud and at the edge.
  • IoT & DevOps Fundamentals: the basics of CI/CD for Intelligent Edge application development and deployment.
  • Watchdogs & Tracing: Network partition monitoring and event driven design for partition events. This pattern allows edge and cloud deployed applications and services to be independently responsive to partition events.
  • Log Shipping from Edge to Cloud: Azure IoT Direct Methods are the method by which the cloud can communicate to edge applications running in IoT Edge.
  • Gateway Host Management: the updating and patching of physical gateway devices deployed to the field. This pattern will be replaced as products for this functionality are delivered from product engineering.

Who should attend

  • Target Audience:
    • Microsoft – CSE, CSA, GBB, ATT, SE, TPM, & Product Engineering
    • Customer – Intelligent Edge application developers, IoT solution integrators, ISVs, IT pros
  • Target verticals: Retail, Manufacturing (discrete and continuous), Telco, Healthcare, Government, Travel & Hospitality, Finance, Natural Resource Management, Supply Chain and Logistics, cross-industry


Knowledge Prerequisites

To be successful and get the most out of this OpenHack, it is highly recommended that participants have previous experience with:

  • Understanding the "Things, Insights, Actions" approach to IoT solution development with the Azure IoT Reference Architecture
  • Overview of Azure IoT Hub for high-scale IoT telemetry ingest
  • Deploy and Manage the Intelligent Edge with Azure IoT Edge
  • Leveraging Azure DevOps to plan, collaboratively develop, build and deploy applications for IoT solutions
  • Maximize the availability and performance of Intelligent Edge Applications with Azure Monitor
Language-Specific Prerequisite
  • None
Tooling Prerequisites

To avoid any delays with downloading or installing tooling, have the following ready to go ahead of the OpenHack:

Required Tools
  • A modern laptop running Windows 10 (1703 or higher), Mac OSX (10.12 or higher), or one of these Ubuntu versions
  • Docker CE (18.02.0+) on Windows , macOS or Linux .
  • An IDE or code editor; Visual Studio or Visual Studio Code
  • VS Code
    • Docker Support for VSCode
    • Azure IoT Tools for VSCode
  • Visual Studio
    • Azure IoT Edge Tools for Visual Studio 2019
  • Install the latest .NET Core SDK (3.1) on your personal device
  • Install an OpenSSL Client on your personal device
    • Installation of OpenSSH For Windows Server 2019 and Windows 10
    • Installation of Putty, an SSH and telnet client for Windows
Recommended Tools
  • Download the latest version of Azure CLI.
  • Azure CLI - IoT Extension
  • Docker Compose (1.20.0+) (Only required for Linux. Compose has already been included in Windows/macOS Docker CE installation)
  • Python (2.7/3.5/3.6/3.7/3.8) and Pip
  • Azure IoT EdgeHub Dev Tool

Course Objectives

  • This OpenHack (OH) covers the fundamentals required to drive production readiness and operationalization of solutions built on Azure IoT offerings. Customers will need to implement all the components and patterns covered by this OH to be successful with their solutions in a production environment. By preparing the technical field with production operationalization patterns, customers are more likely to stay and build on Azure after they have de-risked their projects. Furthermore, we see opportunity to share this OH with our stakeholders in product engineering so they can tangibly see the impact of technology gaps and friction points in solutions built using their technology.
  • From a Microsoft business value proposition, this OH covers content that will on-board all IoT solutions to offerings like Azure Monitor, Azure DevOps, and Time Series Insights – driving further revenue opportunity.

Prices & Delivery methods

Online Training

3 days

  • Online Training: CAD 13,500
  • Online Training: US$ 10,000
Classroom Training

3 days

  • Canada: CAD 13,500


Currently there are no training dates scheduled for this course.