The New Stack Podcast

When the Open Container Initiative was first formed over two years ago now, the event appeared at the time to lend a much-needed sense of importance to the matter of how a software container should be formed and formatted.  Then last year, Mesosphere began work on what it was describing as a Universal Container Runtime (UCR) — a way to leverage Mesos’ format-agnostic methodology for scheduling workloads, to schedule any workload in any respectable format but recognize it as though it were a container.

Last month at MesosCon in Los Angeles, Mesosphere formally announced the stable version of the project. And in a wide-ranging discussion, company co-founder and CTO Tobias Knaup offered some further insight on the concept, defining UCR as a runtime inside Mesos enabling it to abstract away the details of a workload from whatever container management system may be addressing that workload.

Watch on YouTube: https://youtu.be/h-fga2dE4Og

When the Open Container Initiative was first formed over two years ago now, the event appeared at the time to lend a much-needed sense of importance to the matter of how a software container should be formed and formatted.  Then last year, Mesosphere began work on what it was describing as a Universal Container Runtime (UCR) — a way to leverage Mesos’ format-agnostic methodology for scheduling workloads, to schedule any workload in any respectable format but recognize it as though it were a container.

Last month at MesosCon in Los Angeles, Mesosphere formally announced the stable version of the project. And in a wide-ranging discussion, company co-founder and CTO Tobias Knaup offered some further insight on the concept, defining UCR as a runtime inside Mesos enabling it to abstract away the details of a workload from whatever container management system may be addressing that workload.

Watch on YouTube: https://youtu.be/h-fga2dE4Og

During his time as chief technical officer for infrastructure at Cisco, Ken Owens was the point man for explaining software-defined infrastructure to a new and sometimes skeptical crowd.  Eventually, the other folks at Cisco caught on to what Owens was saying to them, and now the company has a more sophisticated strategy for software-defined infrastructure.

But now, he’s taken on a similar role on the other side of the fence, as Vice President for Digital Native Architecture at financial services provider Mastercard.  Now his job is to articulate the requirements for software-defined infrastructure to a new, and perhaps even more skeptical, audience.  At the recent Open Source Summit in Los Angeles, he took note of what he considered to be an attendance imbalance between the introductory sessions and the “lessons learned” discussions, with the latter grabbing the lion’s share of people.

It wasn’t because folks already know the technology and don’t need an introduction to it, Owens believes.  As he told Scott Fulton for this edition of The New Stack Makers, he has observed a continued hesitancy among enterprises to going all-in on any technology, especially in the open source field — at least not until there’s more history behind it.

Watch on YouTube: https://youtu.be/geCyWdVa1j4

During his time as chief technical officer for infrastructure at Cisco, Ken Owens was the point man for explaining software-defined infrastructure to a new and sometimes skeptical crowd.  Eventually, the other folks at Cisco caught on to what Owens was saying to them, and now the company has a more sophisticated strategy for software-defined infrastructure.

But now, he’s taken on a similar role on the other side of the fence, as Vice President for Digital Native Architecture at financial services provider Mastercard.  Now his job is to articulate the requirements for software-defined infrastructure to a new, and perhaps even more skeptical, audience.  At the recent Open Source Summit in Los Angeles, he took note of what he considered to be an attendance imbalance between the introductory sessions and the “lessons learned” discussions, with the latter grabbing the lion’s share of people.

It wasn’t because folks already know the technology and don’t need an introduction to it, Owens believes.  As he told Scott Fulton for this edition of The New Stack Makers, he has observed a continued hesitancy among enterprises to going all-in on any technology, especially in the open source field — at least not until there’s more history behind it.

Watch on YouTube: https://youtu.be/geCyWdVa1j4

During his time as chief technical officer for infrastructure at Cisco, Ken Owens was the point man for explaining software-defined infrastructure to a new and sometimes skeptical crowd.  Eventually, the other folks at Cisco caught on to what Owens was saying to them, and now the company has a more sophisticated strategy for software-defined infrastructure.

But now, he’s taken on a similar role on the other side of the fence, as Vice President for Digital Native Architecture at financial services provider Mastercard.  Now his job is to articulate the requirements for software-defined infrastructure to a new, and perhaps even more skeptical, audience.  At the recent Open Source Summit in Los Angeles, he took note of what he considered to be an attendance imbalance between the introductory sessions and the “lessons learned” discussions, with the latter grabbing the lion’s share of people.

It wasn’t because folks already know the technology and don’t need an introduction to it, Owens believes.  As he told Scott Fulton for this edition of The New Stack Makers, he has observed a continued hesitancy among enterprises to going all-in on any technology, especially in the open source field — at least not until there’s more history behind it.

Watch on YouTube: https://youtu.be/geCyWdVa1j4

During his time as chief technical officer for infrastructure at Cisco, Ken Owens was the point man for explaining software-defined infrastructure to a new and sometimes skeptical crowd.  Eventually, the other folks at Cisco caught on to what Owens was saying to them, and now the company has a more sophisticated strategy for software-defined infrastructure.

But now, he’s taken on a similar role on the other side of the fence, as Vice President for Digital Native Architecture at financial services provider Mastercard.  Now his job is to articulate the requirements for software-defined infrastructure to a new, and perhaps even more skeptical, audience.  At the recent Open Source Summit in Los Angeles, he took note of what he considered to be an attendance imbalance between the introductory sessions and the “lessons learned” discussions, with the latter grabbing the lion’s share of people.

It wasn’t because folks already know the technology and don’t need an introduction to it, Owens believes.  As he told Scott Fulton for this edition of The New Stack Makers, he has observed a continued hesitancy among enterprises to going all-in on any technology, especially in the open source field — at least not until there’s more history behind it.

Watch on YouTube: https://youtu.be/geCyWdVa1j4

Microsoft has taken an approach that essentially meets the developer halfway by providing abstractions so tools like Jenkins and Terraform can seamlessly work in hybrid, multi-cloud  environments using third-party tools. It's a mouthful but speaks to the concept of federation and how abstracting operations has become an important philosophy for Microsoft as it works to help developers bridge the gaps that have long been impassable. The intricate operations requirements to glue disparate components has long eluded customers. To close the gap means meeting developers where they are.

In essence, Microsoft is offering a platform for developers to use the tools they know and love instead of rebuilding from scratch, said Arun Chandrasekhar, Senior Program Manager at Microsoft Azure, who joined us for a conversation at OpenSource Summit in Los Angeles in September.

Watch on YouTube: https://youtu.be/0ZzwPeAnI3g

Microsoft has taken an approach that essentially meets the developer halfway by providing abstractions so tools like Jenkins and Terraform can seamlessly work in hybrid, multi-cloud  environments using third-party tools. It's a mouthful but speaks to the concept of federation and how abstracting operations has become an important philosophy for Microsoft as it works to help developers bridge the gaps that have long been impassable. The intricate operations requirements to glue disparate components has long eluded customers. To close the gap means meeting developers where they are.

In essence, Microsoft is offering a platform for developers to use the tools they know and love instead of rebuilding from scratch, said Arun Chandrasekhar, Senior Program Manager at Microsoft Azure, who joined us for a conversation at OpenSource Summit in Los Angeles in September.

Watch on YouTube: https://youtu.be/0ZzwPeAnI3g

Microsoft has taken an approach that essentially meets the developer halfway by providing abstractions so tools like Jenkins and Terraform can seamlessly work in hybrid, multi-cloud  environments using third-party tools. It's a mouthful but speaks to the concept of federation and how abstracting operations has become an important philosophy for Microsoft as it works to help developers bridge the gaps that have long been impassable. The intricate operations requirements to glue disparate components has long eluded customers. To close the gap means meeting developers where they are.

In essence, Microsoft is offering a platform for developers to use the tools they know and love instead of rebuilding from scratch, said Arun Chandrasekhar, Senior Program Manager at Microsoft Azure, who joined us for a conversation at OpenSource Summit in Los Angeles in September.

Watch on YouTube: https://youtu.be/0ZzwPeAnI3g

Microsoft has taken an approach that essentially meets the developer halfway by providing abstractions so tools like Jenkins and Terraform can seamlessly work in hybrid, multi-cloud  environments using third-party tools. It's a mouthful but speaks to the concept of federation and how abstracting operations has become an important philosophy for Microsoft as it works to help developers bridge the gaps that have long been impassable. The intricate operations requirements to glue disparate components has long eluded customers. To close the gap means meeting developers where they are.

In essence, Microsoft is offering a platform for developers to use the tools they know and love instead of rebuilding from scratch, said Arun Chandrasekhar, Senior Program Manager at Microsoft Azure, who joined us for a conversation at OpenSource Summit in Los Angeles in September.

Watch on YouTube: https://youtu.be/0ZzwPeAnI3g