The Eclipse Foundation in collaboration with the OpenAtom Foundation today launched the Oniro project and a working group to create an independent implementation of OpenHarmony, an open source operating system.
Created by the OpenAtom Foundation, the OpenHarmony operating system is based on a HarmonyOS originally created by Huawei. It is designed to support multiple kernels but uses the Linux kernel if a device has a large amount of memory.
It also includes a DSoftBus capability to integrate physically separate devices into a single logical super device which allows one device to control the others in addition to facilitating data sharing between distributed devices.
Huawei, together with Linaro, Seco, Array, NOITechPark and Synesthesia, has also contributed to a continuous integration / continuous delivery (CI / CD) platform that is part of the larger Oniro project.
Mike Milinkovich, executive director of the Eclipse Foundation, said the goal is to provide a common layer of abstraction platform that can be used on a wide variety of embedded systems that are typically deployed at the edge of the network. This level of fragmentation surrounding platforms that don’t offer a lot of significant differentiated value only slows down application deployment, Milinkovich noted.
As part of this effort, a dedicated working group has been established to provide a vendor-independent structure through which contributions to the project can be made with greater transparency. The OpenAtom Foundation was established in Beijing last year with support from Alibaba, Baidu, Huawei, Inspur, Qihoo, Tencent and China Merchants Bank. The alliance with the Eclipse Foundation brings more traditional governance rules for the creation of open source software to the OpenHarmony project.
In general, DevOps teams should closely monitor the development of proposed de facto standards for advanced computing platforms. More and more applications are now being deployed on cutting-edge computing platforms that enable data to be processed and analyzed as it is created and consumed. The DevOps challenges associated with building and deploying applications in a highly distributed computing environment are significant.
In many cases, organizations that have never really attempted or mastered continuous delivery of applications and their associated updates will be seriously challenged when it comes to supporting hundreds, if not thousands, of applications. ‘applications, running on embedded systems based on a wide range of processors.
Additionally, many of those same DevOps teams will begin to see traditional batch-oriented applications being replaced by applications based on event-driven architectures that process data in near real time. In most cases, these applications will be built on top of microservice-based applications which are generally more difficult to build and deploy than a traditional monolithic application.
Arguably IT organizations are on the cusp of a new IT age which assumes that most organizations not only master DevOps best practices, but now also adopt DevSecOps best practices to secure these application environments.
It may be some time before the open source software that will be developed by the Orino project finds its way into production environments, but it should be obvious that reducing complexity at the edge of the network should be a key factor. high priority for all DevOps teams by 2022.