The New Stack Podcast

Technology processes have not been designed with the human element in mind. Devices may be made easier, but only through the accomplishments of an ever more complex and typically unseen mesh of technological infrastructures. This surprising pronouncement from Chef CTO Adam Jacob, the co-creator of Habitat, a system that purports to add more of the human element to configuration management. Secure systems, said Jacob, are not engineered to accept change. As a result, they tend to reject new processes on their face, even though they may be innovative, useful and, on the whole, improvements over the systems we already have.

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

Technology processes have not been designed with the human element in mind. Devices may be made easier, but only through the accomplishments of an ever more complex and typically unseen mesh of technological infrastructures. This surprising pronouncement from Chef CTO Adam Jacob, the co-creator of Habitat, a system that purports to add more of the human element to configuration management. Secure systems, said Jacob, are not engineered to accept change. As a result, they tend to reject new processes on their face, even though they may be innovative, useful and, on the whole, improvements over the systems we already have.

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

Technology processes have not been designed with the human element in mind. Devices may be made easier, but only through the accomplishments of an ever more complex and typically unseen mesh of technological infrastructures. This surprising pronouncement from Chef CTO Adam Jacob, the co-creator of Habitat, a system that purports to add more of the human element to configuration management. Secure systems, said Jacob, are not engineered to accept change. As a result, they tend to reject new processes on their face, even though they may be innovative, useful and, on the whole, improvements over the systems we already have.

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

Technology processes have not been designed with the human element in mind. Devices may be made easier, but only through the accomplishments of an ever more complex and typically unseen mesh of technological infrastructures. This surprising pronouncement from Chef CTO Adam Jacob, the co-creator of Habitat, a system that purports to add more of the human element to configuration management. Secure systems, said Jacob, are not engineered to accept change. As a result, they tend to reject new processes on their face, even though they may be innovative, useful and, on the whole, improvements over the systems we already have.

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

OpenStack is folding the big tent for a more modular approach. How will that affect development for this massive open source project that OpenStack has become?

At Open Source Summit in September, TNS Founder Alex Williams spoke with Linux Academy instructor Amy Marrich to learn more about what's next for OpenStack, and how Marrich's Linux Academy courses are helping developers to do more with OpenStack. One such focus in Marrich's classes is a scenario-based story, with developers focused on creating groups in Keystone in a cloud assessment for a fictional government client.

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

OpenStack is folding the big tent for a more modular approach. How will that affect development for this massive open source project that OpenStack has become?

At Open Source Summit in September, TNS Founder Alex Williams spoke with Linux Academy instructor Amy Marrich to learn more about what's next for OpenStack, and how Marrich's Linux Academy courses are helping developers to do more with OpenStack. One such focus in Marrich's classes is a scenario-based story, with developers focused on creating groups in Keystone in a cloud assessment for a fictional government client.

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

OpenStack is folding the big tent for a more modular approach. How will that affect development for this massive open source project that OpenStack has become?

At Open Source Summit in September, TNS Founder Alex Williams spoke with Linux Academy instructor Amy Marrich to learn more about what's next for OpenStack, and how Marrich's Linux Academy courses are helping developers to do more with OpenStack. One such focus in Marrich's classes is a scenario-based story, with developers focused on creating groups in Keystone in a cloud assessment for a fictional government client.

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

OpenStack is folding the big tent for a more modular approach. How will that affect development for this massive open source project that OpenStack has become?

At Open Source Summit in September, TNS Founder Alex Williams spoke with Linux Academy instructor Amy Marrich to learn more about what's next for OpenStack, and how Marrich's Linux Academy courses are helping developers to do more with OpenStack. One such focus in Marrich's classes is a scenario-based story, with developers focused on creating groups in Keystone in a cloud assessment for a fictional government client.

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

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