Cloud Native Computing Foundation KubeCon + CloudNativeCon North America 2016 (Seattle), 16 Nov 2016

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Lightning Talk - OCI: Container Standards and Certification

Description

Lightning Talk - OCI: Container Standards and Certification - Rob Dolin, Microsoft & Jeffrey Borek, IBM

The Open Container Initiative (OCI) was formed mid-2015 with the goal of creating open, industry standards around container formats and runtimes. Who's behind this effort, how has the scope evolved, and what is the latest progress along the path towards open governance and multi-vendor support with respect to open source container standardization? Join this update to hear from the front lines of this important effort, and learn how you can get involved/benefit.

About Jeffrey Borek
Jeff Borek is a senior technology and communications executive with over twenty years of leadership and technical experience in the Software, Telecommunications, and Information Technology/Consulting industries. He is currently the business development lead for the Open Technologies and Partnerships team - working with clients, business partners, leading industry analysts, and various open source community initiatives including; the OpenStack cloud software project, the Cloud Foundry Foundation, and the Linux Foundation to ensure rapid response to changes in the market environment. He also represents IBM on the Open Container Initiative, the Cloud Native Computing Foundation, and as the current Chairman on the Docker Governance Advisory Board.

About Rob Dolin
Rob Dolin is the Co-Chair of the Open Container Initiative (OCI) Certification Program WG. He works as a Senior Engineering Program Manager on Microsoft’s Open Interoperability team. His past community work includes service on the OpenDaylight Technical Steering Committee, as a committer on the Open Live Writer project, and as a co-author with representatives from Facebook, Google, IBM, and SixApart on the Activity Streams standard. Rob has volunteered teaching intro to computer science in the Seattle Public Schools.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.

A

My name is Rob Dolan I'm, a part of Microsoft's, a former team, formerly known as Microsoft, open tech working on cross-platform interoperability and Jeff and I are co-chairs of the open container initiative. Certification program, work crew. So.

B

We've got about a half hour worth of interesting information to pack into five minutes, so we're going to keep moving quickly and I'm going to talk a little bit about container technology just to make a couple of key points and you can check out the slide. But container technology is not anything tremendously new, which is good.

B

It means the foundation of it is rock solid and you can see from the presentation that it really got off in the eunuch space around the year 2000 and plenty of different companies from Solaris to google, the Linux Foundation IBM Red Hat up until most recently, our friends at docker really kind of rocked the world by taking a couple of key components and adding some additional value add and making it a lot easier for your average developer or sysadmin to wrap their head around. How do you take advantage of containers?

B

Because, let's face it, you know, Google was leveraging the heck out of container technology ever since, like the 06 07 time frame, you know the board was just massively crunching through containers docker to their credit again put together this innovative technology and its really been a game changer and we're going to talk a little bit more about how that's evolved.

B

So I first started working with docker back in 2014 at the OpenStack conference down at Atlanta, and that was all the buzz on the show floor. Is that gee? You know this startups done this quick pivot and they've.

B

You know created this compelling new technology and we got interested right away because we really saw the potential that we also saw the fact that you know it was an open source project and the company behind it had co-branded around docker and so they've made a commitment back then too be radically open and we've been working with them along with a bunch of other companies and ultimately that led to Solomon at docker con mid-2015 making this announcement about the open container initiative.

B

It's a working group of the Linux Foundation and the key tenants of this effort have been that it's not going to be tightly controlled by any single vendors. So one of the things that we always look at is this idea of how do you balance the concept of open source with open governance and that's really what the oci is all about, as it relates to the base container technology?

B

So a lot of people have been involved with this, but, in addition to docker, really want to give a shout out to the guys at core OS, they were instrumental in working with docker early on, and then they also saw this desire to really ensure that this dialog got started about how to make this technology truly open. So they put out this alternative approach with their rocket initiative and that really helped spur this dialogue about the fact that this really needed to be a shared based technology that many companies could come together and collaborate on.

B

So you can see by the logos up on the screen. Many many companies are involved with this and Rob's going to go into a bit more detail as to you know exactly who's participating in this, because it's still very much a multi-vendor environment. Thanks.

A

Very much Jeff, as Jeff mentioned, there's a lot of companies that are participating in this and, as you can see, this is not a. This is not a open source project, that's dominated by one company or even one or two companies just to list a few here: Red Hat, docker, huawei, core OS, fujitsu parallels, suisei, IBM, Linux, Foundation, Google, Microsoft cloud, fair stripe, Intel, wizardry, canonical, EMC info stir and pivotal are all up on that pie. Chart.

A

Oci is a really interesting project because it's actually its primary output is specs, the runtime spec and the image format spec and, as you can see, from the diagram that I the diagram up here, the runtime spec is influenced both by an open source reference implementation. That's part of run c, as well as by industry industry products. You can see the cartoon docker hamster wheel running as well as core OS rocket, as well as a whole ecosystem of vendors products and users.

A

So the open, oci certification program is a project that a number of members of oci are working on to try to provide an oci, certified runtime and an oci certified image, and the groups have defined those as meeting all of the muster required provisions from the specs. So it's not about you have to use this open source project, but you can use opens you can use the open source reference implementation or you can use other code to meet those requirements, and then oci has worked on trademarking a number of marks or terms related to that.

A

Last but not least, this is what the certification program draft is going to look like. This is how you can get involved, open containers, org, and thank you very much.