By Ian Jolliffe
StarlingX is a relatively new open source project - it was announced in May of 2018 and things have changed, grown and evolved very quickly. It is a very different project now than when we started for sure. Let's review the journey we've taken to get to the recent StarlingX 2.0 release.
In the past year we have made a tremendous amount of progress as a community. We have fully operationalized community governance, attracted new contributors from around the world, and elected a diverse set of members to the Technical Steering Committee from four different companies. There are a wide range of opportunities for people to contribute to the project; please reach out to us if you are looking to learn more. We have a group of people in our First Contact SIG working to improve the on boarding experience.
At the same time the community has made huge strides in evolving the architecture of the project. In the first release, the platform services ran on bare metal. In this release, the platform has evolved to a cloud native platform integrating OpenStack and Kubernetes with the StarlingX services. The containers are deployed via a local docker registry. We now have an ecosystem of components with the StarlingX services ready to drive the convergence of the 5G world. This is a great example of the power of open infrastructure components coming together to solve real problems.
As new technologies emerge it is important to adapt and change to take advantage of the possibilities they bring to the table. At the edge, the solutions are power and space constrained, latency and timing are critical. StarlingX now gives users the choice to deploy containers or VM’s or both. OpenStack services are deployed in containers that gives more flexibility to shape the platform for the requirements of a particular environment. We can now provide an edge optimized solution that brings together Kubernetes and OpenStack.
StarlingX is a project that develops and integrates technologies that brings together a curated solution for Edge use cases.
Among other features the project provides:
1. Growing documentation suite
3. Ease of deployment
4. High performance networking
5. Support for highly accurate synchronous timing
Below are some of the StarlingX 2.0 updates in these areas:
· Support for TPM devices to store secrets, and UEFI secure boot are some examples of the easy ways to leverage security capabilities that are critical at the edge.
· Deployment is realized by a fully declarative model that leverages Ansible to configure and deploy the initial host environment and software services. We have contributed to and are leveraging Armada and OpenStack Helm to deploy and configure the OpenStack services.
· From a networking perspective the solution is brought together with either IPv4 or IPv6 full stack support. Calico is the primary CNI, along with Multus and SRIOV to provide high performance (low latency and high throughput) networking capabilities needed at the edge.
· In this release we have added support for Precision Time Protocol (PTP). This is a great way to source, and distribute a highly accurate clock source to all servers in the cloud. This provides a way to distribute and align a highly accurate clock around a factory or a telecom network, areas where NTP is not accurate enough.
· At the same time as the above architectural changes, we have refreshed many components of the stack such as aligning 100% with OpenStack Stein, and updating to Ceph Mimic. In the OpenStack Train release we have contributed to Nova and Neutron and eliminated all out of tree patches.
The StarlingX community has worked tirelessly over the past several months on this exciting transformation. See the release notes for more information or check the code to start you journey with StarlingX.
In future blogs, we will go deeper into each of these areas. I hope you find the work we are doing in the community interesting. Your feedback is appreciated, so please join us in this exciting journey transforming computing at the edge and enabling exciting new use cases, in transportation, automation, medical and telecommunications.
*Post originally published at StarlingX.io.