Join the OpenInfra Edge Computing Group to talk about edge conundrums and how to turn them into solutions
After a brief introduction to the Day 0, 1, 2/N concepts, the scheduled two hours will be dedicated to the exploration of the preparation phase of your edge buildout. The topics include a deep dive into how automation is critical, the creation of vanilla templates with variables that can be inserted during Day 2 deployment, site prep work and all the challenges with laying the groundwork for a successful and repeatable edge deployment. If time allows we will also explore new use cases, which is always timely as a growing number of industry segments are getting ready for production deployments.
This day is dedicated for ‘Day-1’ activities, which is where things get really exciting! We will be discussing deployment and configuration challenges. How can you automate the insertion of site-specific variables, such as IP addresses as you deploy edge out to hundreds or thousands of highly distributed locations? Another session will explore how to validate that the deployment was successful and verify your infrastructure during the stages of the overall deployment process. And finally, a discussion of deploying infrastructure over a Zero Trust environment, as security needs to be taken into consideration, would not be out of place.
So you have finally deployed all your sites and you are ready to support them in operations. Now what? The sessions on our last day will focus on on ‘Day- 2, or as some call it ‘Day-n’, operations. Just because your infrastructure and workloads are all operational, does not mean that you can afford to sit back and relax! In production, you need to figure out how to best operate and maintain your infrastructure to keep your workloads running smoothly. We will discuss the challenges and potential solutions with a focus on automation, Infrastructure as Code and more. Some specific topics include:
- Infrastructure as Code
- How configuration changes trigger automated processes (validation and other sequences)
- Patching and library/repository management
- log4j, CentOS changes, and more
- How do you trigger updates and changes?
- Trouble ticket creation based on monitoring of network/nodes
- Testing/root cause analysis triggered by trouble ticket creation
As you can see from this brief overview, we have much work to cover in a short amount of time, as there are many components that need to be taken into consideration as your edge infrastructure moves from an idea into deployment and production. We hope that by organizing the topics by deployment stage, this will spark fruitful discussions. We encourage anyone who has an interest in how to turn edge computing, and that includes — individuals and organizations from open source communities, standards bodies, vendors, architects, and developers — into a thriving reality to join the sessions!
The Edge Computing Group is a working group comprised of architects and engineers across large enterprises, telecoms and technology vendors working to define and advance edge cloud computing. The focus is open infrastructure technologies, not exclusive to OpenStack.