Fairbanks

𝐇𝐨𝐰 𝐝𝐨 𝐲𝐨𝐮 𝐦𝐚𝐧𝐚𝐠𝐞 𝐢𝐧𝐟𝐫𝐚𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞 𝐰𝐢𝐭𝐡𝐨𝐮𝐭 𝐝𝐫𝐨𝐰𝐧𝐢𝐧𝐠 𝐢𝐧 𝐜𝐨𝐦𝐩𝐥𝐞𝐱𝐢𝐭𝐲? As infrastructure evolves, so does the complexity behind it. From physical resources and private cloud to Infrastructure as Code, containers and orchestration: every new layer can make infrastructure more powerful, but also harder to manage. In our upcoming keynote, we take a step back and look at how infrastructure management has evolved, why automation alone is not the end of the journey, and how orchestration with Kubernetes can help manage infrastructure at scale. We’ll explore the different layers of complexity, the choices organizations make about what to manage themselves, and what to delegate. Most importantly: how do you create simplicity for users without losing control over what happens underneath? 📅 October 29 Sign up for the keynote and join the conversation.

🚨 𝐖𝐡𝐚𝐭 𝐢𝐟 𝐎𝐩𝐞𝐧𝐒𝐭𝐚𝐜𝐤 𝐰𝐚𝐬 𝐜𝐥𝐨𝐮𝐝-𝐧𝐚𝐭𝐢𝐯𝐞 𝐭𝐡𝐞 𝐰𝐡𝐨𝐥𝐞 𝐭𝐢𝐦𝐞, 𝐢𝐭 𝐣𝐮𝐬𝐭 𝐧𝐞𝐯𝐞𝐫 𝐡𝐚𝐝 𝐭𝐡𝐞 𝐫𝐢𝐠𝐡𝐭 𝐡𝐨𝐦𝐞? Stateless services. REST APIs. A design built for orchestration, 15 years before the term "cloud-native" existed. ✔️ Running OpenStack the way it was always meant to run ✔️ Kubernetes as the natural conclusion, not an extra layer ✔️ Years of scattered tooling, finally consolidated into one place

🚨 𝐘𝐨𝐮'𝐫𝐞 𝐧𝐨𝐭 𝐦𝐚𝐧𝐚𝐠𝐢𝐧𝐠 𝐎𝐩𝐞𝐧𝐒𝐭𝐚𝐜𝐤. 𝐘𝐨𝐮'𝐫𝐞 𝐦𝐚𝐧𝐚𝐠𝐢𝐧𝐠 𝐭𝐰𝐨 𝐬𝐲𝐬𝐭𝐞𝐦𝐬 𝐭𝐡𝐚𝐭 𝐝𝐨𝐧'𝐭 𝐭𝐚𝐥𝐤 𝐭𝐨 𝐞𝐚𝐜𝐡 𝐨𝐭𝐡𝐞𝐫. The real complexity isn't the initial build. It's keeping OpenStack patched, upgraded, and secure, on an OS never designed to make that easy. ✔️ One orchestration layer instead of two disconnected ones ✔️ Security patching that doesn't put your cluster at risk ✔️ Upgrades that stop draining your team's time

𝗧𝗵𝗲 𝗰𝗵𝗮𝗻𝗴𝗲𝘀 𝗮𝗿𝗼𝘂𝗻𝗱 𝗩𝗠𝘄𝗮𝗿𝗲 𝗰𝗮𝗹𝗹 𝗳𝗼𝗿 𝗮𝗰𝘁𝗶𝗼𝗻. 𝗡𝗼𝘁 𝗳𝗼𝗿 𝗿𝘂𝘀𝗵𝗲𝗱 𝗺𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻. Many organizations are feeling the pressure to rethink their VMware strategy. Cost, dependency and long-term flexibility are now higher on the agenda than ever. But a successful migration does not start with the question of where you want to go. It starts with understanding what you have today. Which workloads are running? How critical are they? And which workloads can or cannot simply be moved? 𝗪𝗮𝘁𝗰𝗵 𝘁𝗵𝗲 𝗿𝗼𝘂𝗻𝗱 𝘁𝗮𝗯𝗹𝗲 𝗱𝗶𝘀𝗰𝘂𝘀𝘀𝗶𝗼𝗻 𝗮𝗻𝗱 𝗱𝗶𝘀𝗰𝗼𝘃𝗲𝗿 𝗵𝗼𝘄 𝘁𝗼 𝗺𝗼𝘃𝗲 𝗳𝗿𝗼𝗺 𝗩𝗠𝘄𝗮𝗿𝗲 𝘂𝗻𝗰𝗲𝗿𝘁𝗮𝗶𝗻𝘁𝘆 𝘁𝗼 𝗮 𝗰𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗲𝗱 𝗺𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝗮𝗽𝗽𝗿𝗼𝗮𝗰𝗵.

𝗩𝗠𝘄𝗮𝗿𝗲 𝗺𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝗶𝘀 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝗮 𝘁𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗽𝗿𝗼𝗷𝗲𝗰𝘁. The decision to migrate affects more than infrastructure alone. It impacts strategy, budget, operations, risk and the people who need to work with the platform every day. That is why VMware migration should not sit solely with the technical team. C-level, tactical management and IT all need to understand the context, the choices and the impact. 𝗪𝗮𝘁𝗰𝗵 𝘁𝗵𝗲 𝗿𝗼𝘂𝗻𝗱 𝘁𝗮𝗯𝗹𝗲 𝗱𝗶𝘀𝗰𝘂𝘀𝘀𝗶𝗼𝗻 𝗮𝗻𝗱 𝗱𝗶𝘀𝗰𝗼𝘃𝗲𝗿 𝗵𝗼𝘄 𝘁𝗼 𝗮𝗽𝗽𝗿𝗼𝗮𝗰𝗵 𝗩𝗠𝘄𝗮𝗿𝗲 𝗺𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝗮𝗰𝗿𝗼𝘀𝘀 𝘁𝗵𝗲 𝗲𝗻𝘁𝗶𝗿𝗲 𝗼𝗿𝗴𝗮𝗻𝗶𝘇𝗮𝘁𝗶𝗼𝗻.

𝗙𝗿𝗼𝗺 𝗩𝗠𝘄𝗮𝗿𝗲 𝗱𝗲𝗽𝗲𝗻𝗱𝗲𝗻𝗰𝘆 𝘁𝗼 𝘁𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗳𝗹𝗲𝘅𝗶𝗯𝗶𝗹𝗶𝘁𝘆. A platform decision is not just about licensing, infrastructure or which hypervisor you use. It is also about the knowledge your organization builds and how broadly that knowledge can be applied. When your team is mainly used to VMware, much of that expertise remains tied to one ecosystem. Open source knowledge is more widely applicable, from smaller hypervisor environments to large-scale infrastructure stacks. This gives your team more technical freedom and makes your organization more flexible. In this round table discussion, we discusses why open source can be a serious alternative in your VMware strategy, and how to avoid becoming dependent on a single vendor or platform again. 𝗪𝗮𝘁𝗰𝗵 𝘁𝗵𝗲 𝗿𝗼𝘂𝗻𝗱 𝘁𝗮𝗯𝗹𝗲 𝗱𝗶𝘀𝗰𝘂𝘀𝘀𝗶𝗼𝗻 𝗮𝗻𝗱 𝗱𝗶𝘀𝗰𝗼𝘃𝗲𝗿 𝘁𝗵𝗲 𝗿𝗼𝗹𝗲 𝗼𝗽𝗲𝗻 𝘀𝗼𝘂𝗿𝗰𝗲 𝗰𝗮𝗻 𝗽𝗹𝗮𝘆 𝗶𝗻 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗮 𝗺𝗼𝗿𝗲 𝗳𝗹𝗲𝘅𝗶𝗯𝗹𝗲, 𝗳𝘂𝘁𝘂𝗿𝗲-𝗿𝗲𝗮𝗱𝘆 𝗶𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲.