Skip to content

2.1.0
Compare
Choose a tag to compare
@x85446 x85446 released this 01 Oct 14:37
· 468 commits to master since this release
2.1.0
5c8a9c1
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Added

The primary feature in this release is the addition of container orchestration:

  • [compiler] Switches to golang 1.14.4 compiler from 1.11.1. This includes poky meta upstream go.bbclass files.
  • [edge-proxy] Adds edge-proxy tunneling daemon to the buildand subsequent systemD unit and supporting files.
  • [devicejs] Moves devicejs default port from 8080 to 8081 in support of edge-proxy using 8080 for kubelet.
  • [os] Modifies /etc/hosts creation file to support kubelet communication with edge-proxy using the address gateways.local.
  • [os] Adds poky's meta-virtualization layer bblayersto bring in Docker and containered programs, as well as kernel optimizations specified in meta-virtualization to local.conf).
  • [os] Adds boot flags to enable cgroups control over memory and CPU use.
  • [kubelet] Adds edge-kubelet, modified to enable container orchestration with Pelion cloud to the main console-image.
  • [docker] Adds Docker via rdepends in edge-kubelet. Docker's default storage location is moved to /userdata/Docker to take advantage of /userdata's single (non-overlay) ext4 partition, enabling Docker to use the more performant overfs2.
  • [cni] Adds container networking interfaces cni to enable container network communication.

Bug fixes

  • General syntax and whitespace changes in bitbake recipes.
  • Fixed the situation where the root password changes after an upgrade by changing the default WIPETHEUSER_PARTITION to 0.

Known issues

  • When conducting back-to-back production factory flow with the Pelion Edge Provisioner, the mcc_config directory sometimes is not written correctly and upon reboot, Edge-Core does not connect properly. Workaround: Run the provisioner again.
  • After production factory flow, if you run the info command before Edge core pairs with the cloud, the info command shows N/A for the deviceID while displaying connected. Workaround: Delete the file /wigwag/system/lib/bash/relaystatics.sh, and rerun the info command.
  • Portal is not correctly updated after a firmware campaign in some instances.

Limitations

  • The maximum translated devices behind the edge gateway is 100.
  • Devices behind Pelion Edge do not support auto-observation.
  • Pelion Device Management Client enabled devices must first boostrap to the Pelion Device Management Cloud before connecting to Pelion Edge.
  • No moving devices are supported. (Device would be moving from Edge to another Edge device.)

Important note

While provisioning your gateway, please use vendor-id=42fa7b48-1a65-43aa-890f-8c704daade54 to unlock the rich node features, such as gateway logs and gateway terminal in the Pelion web portal.

Assets 2
Loading