...
General Release Tasks and Notes
- Expand hardware support - ARM
EdgeX has been built to be cross platform. Some micro services (such as those written in Go) require compiling to the native platforms (cross compiling). Once the program artifacts for the platform have been created, they also need to be containerized (in Docker) and some of the containerization is platform dependent. Finally, it is also desired that the micro services be tested on their native platform. While virtual machines and simulation environments can allow functional tests to occur, some issues and performance metrics for that platform can only be identified when running on the target platform. This task therefore includes:
- CI process that includes cross compiling for Intel/Arm platform artifacts
- Micro service Docker container images produced for Intel and Arm platforms
- Native platform testing of the micro services on Intel and Arm platforms
- Not MVP, but additional contributions sought for
- Alternate (from Docker/Docker Compose) deployment and orchestration options
Today, while the community and users of EdgeX are free to deploy EdgeX as they see fit based on their use case/needs, the EdgeX community provides Docker container images and a docker-compose.yml file to help get and deploy EdgeX. Going forward, it is anticipated that the community will seek and even need alternate means of deploying, managing, and orchestrating the EdgeX micro services. Options include using Kubernetes, Swarm, Mesos, Nomad, to name a few. Additional support may be offered by system management tools or facilities. At this time, the community welcomes input and contributions in this area from the community and user groups, but has no firm plan to do work in this area by the California release.
- Alternate (from Docker/Docker Compose) deployment and orchestration options
Micro Service Tasks and Notes
...