Part 01 is all about setting up your development environment and building your initial edge tier applications: the Gateway Device App (GDA), which is written in Java, and the Constrained Device App (CDA), written in Python.
This content summarizes the lab module exercises as a companion to the content in the following book sections and chapters from Programming the Internet of Things. They are intended to be used together:
1) Overall: Learn about the edge tier architecture of a typical IoT solution and build two simple applications - one to handle sensing and actuation (Constrained Device App - CDA) and the other to handle integration between the edge tier and cloud tier (Gateway Device App - GDA).
2) System Design: Learn about the edge tier design and the two applications - GDA and CDA - that will comprise this part of the solution.
3) DevOps: Learn how to clone the sample source code for the GDA and CDA, how each application is structured / modularized, and how to navigate / update the code base.
Review the README
Please see README.md for further information on, and use of, this content.
Review the LICENSE and USAGE guidelines
Please see PIOT-DOC-LIC for license and usage information.
PIOT-STU-01-001: A summary of lab module and assignment submission instructions for students of Connected Devices.
PIOT-CFG-01-001: A summary of configuration instructions for this lab module.
CDA specific instructions
PIOT-CDA-01-001: Clone the CDA repository, then configure and test the baseline CDA code (Python), along with initial Git branching suggestions.
GDA specific instructions
PIOT-GDA-01-001: Clone the GDA repository, then configure and test the baseline GDA code (Python), along with initial Git branching suggestions.
Lab Module 02
Lab Module 02 - Add System Performance Monitoring to CDA and GDA is focused on adding initial data generation features to your CDA and GDA. For both applications, you'll add the logic needed to collect basic system performance data and manage a data 'polling' schedule as part of the state of each the application.
PIOT-CDA-02-001: Review the CDA main application template and test its basic functionality. This will allow the CDA to start and stop the SystemPerformanceManager functionality.
PIOT-CDA-02-002: Create the SystemPerformanceManager module. This will be responsible for scheduling system performance data collection tasks.
PIOT-CDA-02-003: Connect SystemPerformanceManager to the CDA's main application code.
PIOT-CDA-02-004: Create BaseSystemUtilTask. This will be the base class containing core functionality all other system performance tasks will inherit.
PIOT-CDA-02-005: Create SystemCpuUtilTask. This will collect CPU utilization metrics from the local system.
PIOT-CDA-02-006: Create SystemMemUtilTask. This will collect memory utilization metrics from the local system.
PIOT-CDA-02-007: Connect SystemCpuUtilTask and SystemMemUtilTask into SystemPerformanceManager. This will allow SystemPerformanceManager to start and stop the performance monitoring tasks.
PIOT-GDA-02-001: Review the GDA main application template and test its basic functionality.
PIOT-GDA-02-002: Create the SystemPerformanceManager module. This will be responsible for scheduling system performance data collection tasks.
PIOT-GDA-02-003: Connect SystemPerformanceManager to the GDA's main application code. This will allow the GDA to start and stop the SystemPerformanceManager functionality.
PIOT-GDA-02-004: Create BaseSystemUtilTask. This will be the base class containing core functionality all other system performance tasks will inherit.
PIOT-GDA-02-005: Create SystemCpuUtilTask. This will collect CPU utilization metrics from the local system.
PIOT-GDA-02-006: Create SystemMemUtilTask. This will collect memory utilization metrics from the local system.
PIOT-GDA-02-007: Connect SystemCpuUtilTask and SystemMemUtilTask into SystemPerformanceManager. This will allow SystemPerformanceManager to start and stop the performance monitoring tasks.
Part 01: Setup and Edge Device Application Configuration
About Part 01 (O'Reilly Book Link)
Part 01 is all about setting up your development environment and building your initial edge tier applications: the Gateway Device App (GDA), which is written in Java, and the Constrained Device App (CDA), written in Python.
This content summarizes the lab module exercises as a companion to the content in the following book sections and chapters from Programming the Internet of Things. They are intended to be used together:
It's comprised of two Lab Modules:
Part 01 Summary (O'Reilly Book Link)
Key Learning Activities
1) Overall: Learn about the edge tier architecture of a typical IoT solution and build two simple applications - one to handle sensing and actuation (Constrained Device App - CDA) and the other to handle integration between the edge tier and cloud tier (Gateway Device App - GDA).
2) System Design: Learn about the edge tier design and the two applications - GDA and CDA - that will comprise this part of the solution.
3) DevOps: Learn how to clone the sample source code for the GDA and CDA, how each application is structured / modularized, and how to navigate / update the code base.
Review the README
Review the LICENSE and USAGE guidelines
Part 01 Lab Module Overview
Lab Module 01
Lab Module 01 - Setup and Initial Test of CDA and GDA is focused on setting up your development environment, cloning the Git repositories you'll need to implement all the exercises in Programming the Internet of Things, and testing the initial applications: Constrained Device App (CDA) and Gateway Device App (GDA).
CDA specific instructions
GDA specific instructions
Lab Module 02
Lab Module 02 - Add System Performance Monitoring to CDA and GDA is focused on adding initial data generation features to your CDA and GDA. For both applications, you'll add the logic needed to collect basic system performance data and manage a data 'polling' schedule as part of the state of each the application.
CDA specific instructions
SystemPerformanceManagerfunctionality.SystemPerformanceManagermodule. This will be responsible for scheduling system performance data collection tasks.SystemPerformanceManagerto the CDA's main application code.BaseSystemUtilTask. This will be the base class containing core functionality all other system performance tasks will inherit.SystemCpuUtilTask. This will collect CPU utilization metrics from the local system.SystemMemUtilTask. This will collect memory utilization metrics from the local system.SystemCpuUtilTaskandSystemMemUtilTaskintoSystemPerformanceManager. This will allowSystemPerformanceManagerto start and stop the performance monitoring tasks.GDA specific instructions
SystemPerformanceManagermodule. This will be responsible for scheduling system performance data collection tasks.SystemPerformanceManagerto the GDA's main application code. This will allow the GDA to start and stop theSystemPerformanceManagerfunctionality.BaseSystemUtilTask. This will be the base class containing core functionality all other system performance tasks will inherit.SystemCpuUtilTask. This will collect CPU utilization metrics from the local system.SystemMemUtilTask. This will collect memory utilization metrics from the local system.SystemCpuUtilTaskandSystemMemUtilTaskintoSystemPerformanceManager. This will allowSystemPerformanceManagerto start and stop the performance monitoring tasks.