OpenStack

I think that person is the ideal person that creates an architecture, but then there are other things.

I do think that a one, two, three will develop because you need OpenStack, you need AI developers now.

You need somebody for infrastructure, right? People think that, oh, I can vibe code something alive.

But yes, but then when you scale, it's going to break.

We also need the classical NFS access because our storage, our AI storage most of the time are also mounted on different infrastructure at the same time.

As instance, our data platform for our Cloud infrastructure is at the same time mounted on our classical OpenStack, through classical OpenStack assets mainly based on file access.

But at the same moment is also mounted on Leonardo, which is a classical HPC system that require a more classical HPC high performance file system.

But at the same moment is also mounted on our Liza infrastructure, which is an expansion of Leonardo full fully focused on ai infrastructure and for this specific requirement we need a typical ai after and now also lisa we a part of a portion of the leader will be also used for incidents so we start to look also to um to vector database, to KD caching, all these functionality that the classical storage infrastructure, they don't provide.

MetaCloud, okay.

MetaCloud was an OpenStack.

It was a service-based company.

It was acquired by Cisco.

Before founding OpenCSG, Sam founded, uh, JIHU GitLab China and served as the CEO.

He's held senior lanagement, leadership positions at IBM, HP, and Mesosphere, and has been deeply involved in open source communities including Docker, Mesos, OpenStack, and Cloud Foundry.

So Sam has had a front row seat to some of the biggest infrastructure transitions in technology, and today I wanted to find out whether we're entering another one, where companies, cities, and perhaps entire countries decide that artificial intelligence is simply too important to outsource.

With that, I'd like to bring Sam on the show.

And then through a series of a career at Red Hat, up until earlier this year, I was the vice president of core platforms engineering.

And that involves things like RHEL, OpenStack, Satellite, the in-vehicle operating system that we're working on, and a lot of those related technologies.

And so that would have been like Fedora and CentOS would be there, all that kind of stuff.

And now I'm working on Lightwell, which is a big topic we'll discuss today.

And I think in July or so, we all realized like, this is going to be a major, this is a major product that requires a full dedicated team.

organization around it.

And so I, I set Ralph free, and I set OpenStack free, and you know, they're being managed by other teams now.

And I'm full time on on Lightwell.

Founders may feel pressure to shift focus from nurturing the open source ecosystem to delivering quarterly growth numbers.

In twenty nineteen, OpenStack's corporate steering committee struggled to balance cloud provider contributions against the needs of downstream operators.

Some argued for tighter governance and monetization of private clouds.

The resolution was to create separate open source and enterprise branches allowing community contributors to shape core functionality while the company built a revenue engine around managed hosting, consulting and support.