Release Date
Deliverables
- Made public request for testing and usage of the latest version of iofogctl i.e. `3.0.0-beta8` on Eclipse ioFog Slack channel.
- Finished performing internal performance and integration testing of the latest version of iofogctl i.e. `3.0.0-beta8` and the components involved i.e Agent and Controller.
- Prepare information about all third party library dependencies.
- Prepare release record, IP records, and submit for review.
Compatibility
- Users will no longer be able to use the old YAML version with 3.0 release as there are some breaking changes in the API's.
- Users will have to delete and disconnect ECNs which are on 2.0 version as they are no longer compatible with 3.0 release.
- Users will have to upgrade the iofogctl brew upgrade iofogctl && brew link --overwrite iofogctl.
- Three SDK's for building Microservices are no longer compatible. These are iofog-java-sdk, iofog-c-sdk and iofog-csharp-sdk as they were not maintained with the latest changes of ioFog 3.0. We have a plan to update them but it is on lower priority. Users will be able update it by themselves if needed. We are expecting community members to update them if they find them useful.
- Nodejs 10 is not compatible any more as it has reached EOL.
Internationalization
- Added the support for different timeZones, iofog identifies the local timezone of the edge node and carries it forward to the microservices.
- Added support for systems using European locale.
Target Environments
- Raspberry Pi
- Linux cloud VM
- Vagrant VM
- Ubuntu 16 and above
- Debian 9 and above
- Centos 7 and 8
- Fedora 22, 23 and 24
| Name | Date | Description |
|---|---|---|
| Code Freeze | 2022/04/27 | |
| Eclipse ioFog 3.0 release | 2022/05/04 |
Themes
Edge Resources
By adding kind EdgeResource in the YAML, the user will be able to deploy edge resources on the edge node. EdgeResources are where the virtual meets the physical, such as a sensor, camera, 3D printer, fuel pump, or other edge resource. These edge resources are mapped into the ioFog abstraction model.
Application Template
By adding kind ApplicationTemplate in the YAML, the user will be able to deploy an application template on the edge node. By deploying an application template the user can preconfigure an entire ioFog application and create an “application store“.
Docker pull percentage
Added support for Docker pull percentage for getting granular percentages when container is being downloaded by Agent.
Agent ability to set local timezone as default timezone for microservices
Added support for determining the local TZ and use it as a default global TZ when creating containers when not provided by the user. Added the ability to configure the TZ using CLI. Also user will be able to provide TZ as an environment variable in the application YAML
Added custom installation plugin support for Agent deployment.
iofogctl can install ioFog Agent on a number of Linux distributions out of the box. However, the list of supported distributions is finite; in order to allow the community to add support for any host environment, iofogctl has been updated with the ability to run user-defined installation scripts for Agent and its dependancies.