To address these challenges and accelerate reliable distribution of software updates, ONF invested in development of an automated system to build, test and deliver most Aether components, from the infrastructure to applications. It quickly became clear that this manual approach to software testing and updating was not scalable or efficient.
#Aether scope parts update
The results were that both operation and development teams had to spend a significant amount of time and effort to manually resolve software update issues, taking time away from other tasks.
In addition, the pilot network often had failures after software upgrades were installed due to software bugs, configuration errors or broken version dependencies between Aether software components. For example, when deploying applications, errors such as passing incorrect cluster configuration files or executing commands on unintended clusters became common. Each ACE took anywhere from two days to a full week to build, test and deploy. With this growth, the process of applying new software updates to the Aether pilot network became more complex, error prone and hence much slower.
In 2020 the scope of Aether expanded in size and scope with the addition of multiple Aether Connected Edges (ACEs), new components such as ROC, SD-Fabric and SD-RAN, and an expanded development team. Building the entire software platform was a manual effort but it was manageable given the network size. This initial network was a simple platform consisting of just two clusters, one in the cloud and the other at the ONF office in Menlo Park, and a single application, OMEC. Hyunsun Moon About the author IntroductionĪether has been rapidly evolving since launch of the pilot network in late 2019.
0 kommentar(er)
