da Agency

Momentum mounts for Kubernetes, cloud native

For any new technology, there are few attributes more valuable then momentum. In the open tech space, few projects have as much momentum as Kubernetes and cloud native application development.
The Cloud Native Computing Foundation (CNCF) kicked off the European leg of its biannual CloudNativeCon/#KubeCon event in Berlin by welcoming five new member organizations and two new projects.
CNCF has pulled in rkt and #containerd as its eighth and ninth open projects, joining Kubernetes, Fluentd, Linkerd, Prometheus, OpenTracing, gRPC and CoreDNS,
IBM senior technical staff member Phil Estes is one of the open source maintainers for containerd. He explained a bit about the project and the role of IBM in the video below:

This week, containerd joined the @CloudNativeFdn. @estesp explains what it means for the community. Details: https://t.co/AQigsrXzqY pic.twitter.com/oC9XAOjO9D
— IBM Cloud (@IBMcloud) March 30, 2017

Meanwhile, CNCF announced that SUSE, HarmonyCloud, QAware, Solinea and TenxCloud have joined as contributing member organizations.
“The cloud native movement is increasingly spreading to all parts of the world,” CNCF executive director Dan Kohn told a sellout crowd of 1,500. That number tripled from CloudNativeCon in London a year prior.
We reported last fall that Kubernetes adoption was on the cusp of catching a giant wave. That wave has evolved into a groundswell among developers. There are now 4,000 projects based on Kubernetes, more than 50 products supporting it and more than 200 meetups around the world.
Even more significant has been the IBM announcement in March that Kubernetes is available on IBM Bluemix Container Service.
Linux Foundation Vice President Chris Aniszczyk and IBM Fellow, VP and Cloud Platform CTO Jason McGee discussed the move by IBM to Kube (and much more) on a podcast recoded from the venue. You can listen to it here:

A few more highlights from Berlin:
• 17-year-old Lucas Käldström, the youngest core Kubernetes maintainer, wowed the crowd with his talk on autoscaling a multi-platform Kubernetes cluster built with kubeadm.

Listening to Lucas talk about multi-architecture cluster support for containers/k8s. Oh, he’s in high school too! pic.twitter.com/V8G3qAylzz
— Phil Estes (@estesp) March 30, 2017

• Docker’s Justin Cormack delivered one of the conference’s most popular sessions with his talk on containerd:

Now @justincormack from @Docker talking containerd in SRO room @CloudNativeFdn Kubecon Berlin. Hey @chanezon open a window, it&8217;s hot! pic.twitter.com/SlVHCyTwH6
— Jeffrey Borek (@jeffborek) March 30, 2017

• An update on the Open Container Initiative from Jeff Borek (IBM), Chris Aniszczyk (Linux Foundation), Vincent Batts (Red Hat) and Brandon Philips (CoreOS)

An update on @OCI_ORG and container standards from @Cra, @JeffBorek, @vbatts, @sauryadas_ & @BrandonPhilips. #KubeC… https://t.co/MqqBKxwjBU
— Kevin J. Allen (@KevJosephAllen) March 29, 2017

More information about Bluemix.
The post Momentum mounts for Kubernetes, cloud native appeared first on #Cloud computing news.
Quelle: Thoughts on Cloud

da Agency

containerd joins the Cloud Native Computing Foundation

Today, we’re excited to announce that #containerd – Docker’s core container runtime – has been accepted by the Technical Oversight Committee (TOC) as an incubating project in the Cloud Native Computing Foundation (CNCF). containerd’s acceptance into the CNCF alongside projects such as Kubernetes, gRPC and Prometheus comes three months after Docker, with support from the five largest cloud providers, announced its intent to contribute the project to a neutral foundation in the first quarter of this year.
In the process of spinning containerd out of Docker and contributing it to CNCF there are a few changes that come along with it.  For starters, containerd now has a logo; see below. In addition, we have a new @containerd twitter handle. In the next few days, we’ll be moving the containerd GitHub repository to a separate GitHub organization. Similarly, the containerd slack channel will be moved to separate slack team which will soon available at containerd.slack.com

containerd has been extracted from Docker’s container platform and includes methods for transferring container images, container execution and supervision and low-level local storage, across both Linux and Windows. containerd is an essential upstream component of the Docker platform used by millions of end users that  also provides the industry with an open, stable and extensible base for building non-Docker products and container solutions.

“Our decision to contribute containerd to the CNCF closely follows months of collaboration and input from thought leaders in the Docker community,” said Solomon Hykes, founder, CTO and Chief Product Officer at Docker. “Since our announcement in December, we have been progressing the design of the project with the goal of making it easily embedded into higher level systems to provide core container capabilities. Our focus has always been on solving users’ problems. By donating containerd to an open foundation, we can accelerate the rate of innovation through cross-project collaboration – making the end user the ultimate benefactor of our joint efforts.”

The donation of containerd aligns with Docker’s history of making key open source plumbing projects available to the community. This effort began in 2014 when the company open sourced libcontainer. Over the past two years, Docker has continued along this path by making libnetwork, notary, runC (contributed to the Open Container Initiative, which like CNCF, is part of The Linux Foundation), HyperKit, VPNKit, DataKit, SwarmKit and InfraKit available as open source projects as well.
containerd is already a key foundation for Kubernetes, as Kubernetes 1.5 runs with Docker 1.10.3 to 1.12.3. There is also strong alignment with other CNCF projects: containerd exposes an API using gRPC and exposes metrics in the Prometheus format. containerd also fully leverages the Open Container Initiative’s (OCI) runtime, image format specifications and OCI reference implementation (runC), and will pursue OCI certification when it is available. A proof of concept for integrating containerd directly into Kubernetes CRI is currently being worked on. Check out the pull request on github for more technical details.

Figure 1: containerd’s role in the Container Ecosystem
Community consensus leads to technical progress
In the past few months, the containerd team has been active implementing Phase 1 and Phase 2 of the containerd roadmap. Details about the project can be charted in the containerd weekly development reports posted in the Github project.
At the end of February, Docker hosted the containerd Summit with more than 50 members of the community from companies including Alibaba, AWS, Google, IBM, Microsoft, Red Hat and VMware. The group gathered to learn more about containerd, get more information on containerd’s progress and discuss its design. To view the presentations, check out the containerd summit recap blog post.
The target date to finish implementing the containerd 1.0 roadmap is June 2017. To contribute to containerd, or embed it into a container system, check out the project on GitHub. If you want to learn more about containerd progress, or discuss its design, join the team in Berlin tomorrow at KubeCon 2017 for the containerd Salon, or Austin for DockerCon Day 4 Thursday April 20th, as the Docker Internals Summit morning session will be a containerd summit.
Additional containerd Resources:

Roadmap
Scope table
Architecture document
Draft APIs

Docker’s core container runtime: containerd joins the @CloudNativeFdnClick To Tweet

The post containerd joins the Cloud Native Computing Foundation appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

da Agency

Docker to donate containerd to the Cloud Native Computing Foundation

Today, Docker announced its intention to donate the #containerd project to the Cloud Native Computing Foundation (CNCF). Back in December 2016, Docker spun out its core container runtime functionality into a standalone component, incorporating it into a separate project called containerd, and announced we would be donating it to a neutral foundation early this year. Today we took a major step forward towards delivering on our commitment to the community by following the Cloud Native Computing Foundation process and presenting a proposal to the CNCF Technical Oversight Committee (TOC) for containerd to become a CNCF project: [overview][link], [proposal][link]. Given the consensus we have been building with the community, we are hopeful to get a positive affirmation from the TOC before CloudNativeCon/KubeCon later this month.  
Over the past 4 years, the adoption of containers with Docker has triggered an unprecedented wave of innovation in our industry: we believe that donating containerd to the CNCF will unlock a whole new phase of innovation and growth across the entire container ecosystem. containerd is designed as an independent component that can be embedded in a higher level system, to provide core container capabilities. Since our December announcement, we have focused efforts on identifying the right home for containerd, and making progress in implementing it and building consensus in the community.

Why is the CNCF the right place for containerd?

Given that containerd has been the heart of the Docker platform since April 2016 when it was included in Docker 1.11, it is already deployed on millions of machines; we wanted it to continue its development under the governance of an organization where a focus on containerization is  front and center.
Docker with containerd is already a key foundation for Kubernetes, which was the original project donated to the CNCF; Kubernetes 1.5 runs with Docker 1.10.3 to 1.12.3. Moving forward, we and key stakeholders from the Kubernetes project believe that containerd 1.0 can be a great core container runtime for Kubernetes.
Strong alignment with other CNCF projects (in addition to Kubernetes): containerd exposes an API using gRPC and exposes metrics in the Prometheus format. Both projects are part of CNCF already.

Technical progress and building consensus
In the past few months, the containerd team has been active implementing Phase 1 and Phase 2 of the containerd roadmap. You can find details about progress in containerd weekly development reports posted in the Github project.
At the end of February, Docker hosted the containerd summit with more than 50 members of the community from companies including Alibaba, AWS, Google, IBM, Microsoft, Rancher, Red Hat and VMware. The group gathered to learn more about containerd, get more information on containerd’s progress and discuss its design. You can watch some of the presentations in the containerd summit recap blog post: Deep Dive Into Containerd By Michael Crosby, Stephen Day, Derek McGowan And Mickael Laventure (Docker), Driving Containerd Operations With GRPC By Phil Estes (IBM) and Containerd And CRI By Tim Hockin (Google).
Tim Hockin from Google gave the best summary of the containerd summit.

containerd @thockin containerd is all we wanted from @docker in @kubernetesio and none of what we didn’t need: kudos to the team! pic.twitter.com/t26kRo2etJ
— chanezon (@chanezon) February 23, 2017

There is still a lot of work to finish implementing the containerd 1.0 roadmap, our target being June 2017. If you want to contribute to containerd, or embed it in your container system, you can find the project on GitHub. If you want to learn more about containerd progress, or discuss its design, join us in Berlin in March at CloudNativeCon/KubeCon 2017 (more details to follow) or Austin for DockerCon Day 4 Thursday April 20th, the Docker Internals Summit morning session will be the next containerd summit.
The Summit is a small collaborative event for container runtime and system experts who are actively maintaining, contributing or generally involved in the design and development of containerd and/or related projects. Simply submit a PR to add discussion topics to the agenda. If you have not signed up to attend the summit you can do so in this form.
Today we followed the CNCF process and presented a proposal to the CNCF Technical Oversight Committee (TOC) for containerd to become a CNCF project: [overview][link], [proposal][link]. If the CNCF TOC votes to accept our donation, we are excited for containerd to become part of the CNCF community!

@Docker to donate containerd to the @CloudNativeFdnClick To Tweet

Learn More about containerd:

Watch the containerd GitHub Repository
Follow @containerd on twitter
Sign up for the containerd summit on 4/21

The post Docker to donate containerd to the Cloud Native Computing Foundation appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

da Agency

containerd livestream recap

In case you missed it last month, we announced that #Docker is extracting a key component of its #container platform, a part of the engine plumbing called #containerd – a core container runtime – and committed to donating it to an open foundation.
You can find up-to-date roadmap, architecture and API definitions in the Github repository, and more details about the project in our engineering team’s blog post.

You can also watch the following video recording of the containerd online meetup, for a summary and Q&A with Arnaud Porterie, Michael Crosby, Stephen Day, Patrick Chanezon and Solomon Hykes from the Docker team:

Here is the list of top questions we got following this announcement:
Q. Are you planning to run docker without runC ?
A. Although runC is the default runtime, as of  Docker 1.12, it can be replaced by any other OCI-compliant implementation. Docker will be compliant with the OCI Runtime Specification
Q. What major changes are on the roadmap for swarmkit to run on containerd if any? 
A. SwarmKit is using Docker Engine to orchestrate tasks, and Docker Engine is already using containerd for container execution. So technically, you are already using containerd when using SwarmKit. There is no plan currently to have SwarmKit directly orchestrate containerd containers though.
Q. Mind sharing why you went with GRPC for the API?
A. containerd is a component designed to be embedded in a higher level system, and serve a host local API over a socket. GRPC enables us to focus on designing RPC calls and data structures instead of having to deal with JSON serialization and HTTP error codes. This improves iteration speed when designing the API and data structures. For higher level systems that embed containerd, such as Docker or Kubernetes, a JSON/HTTP API makes more sense, allowing easier integration. The Docker API will not change, and will continue to be based on JSON/HTTP.
Q. How do you expect to see others leverage containerd outside of Docker?
A. Cloud managed container services such as Amazon ECS, Microsoft ACS, Google Container Engine, or orchestration tools such as Kubernetes or Mesos can leverage containerd as their core container runtime. containerd has been designed to be embedded for that purpose.
Q. How did you decided which feature should get into containerd?  How did you came up with the scope of the future containers?
A. We’re trying to capture in containerd the features that any container-centric platform would need, and for which there’s reasonable consensus on the way it should be implemented. Aspects which are either not widely agreed on or that can trivially be built one layer up were left out.
Q. How integrate with CNI and CNM?
A. Phase 3 of the containerd roadmap involves porting the network drivers from libnetwork and finding a good middle ground between the CNM abstraction of libnetwork and the CNI spec.
Additional Resources:

Contribute to containerd
Join the containerd slack channel
Read the engineering team’s blog post.

Docker Extracts & Donates containerd, it’s Core Container Runtime for the container IndustryClick To Tweet

The post containerd livestream recap appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

da Agency

containerd – a core container runtime project for the industry

Today Docker is spinning out its core #container runtime functionality into a standalone component, incorporating it into a separate project called #containerd, and will be donating it to a neutral foundation early next year. This is the latest chapter in a multi-year effort to break up the Docker platform into a more modular architecture of loosely coupled components.
Over the past 3 years, as Docker adoption skyrocketed, it grew into a complete platform to build, ship and run distributed applications, covering many functional areas from infrastructure to orchestration, the core container runtime being just a piece of it. For millions of developers and IT pros, a complete platform is exactly what they need. But many platform builders and operators are looking for “boring infrastructure”: a basic component that provides the robust primitives for running containers on their system, bundled in a stable interface, and nothing else. A component that they can customize, extend and swap out as needed, without unnecessary abstraction getting in their way. containerd is built to provide exactly that.

What Docker does best is provide developers and operators with great tools which make them more productive. Those tools come from integrating many different components into a cohesive whole. Most of those components are invented by others – but along the way we find ourselves developing some of those components from scratch. Over time we spin out these components as independent projects which anyone can reuse and contribute back to. containerd is the latest of those components.

containerd is already deployed on millions of machines since April 2016 when it was included in Docker 1.11. Today we are announcing a roadmap to extend containerd, with input from the largest cloud providers, Alibaba Cloud, AWS, Google, IBM, Microsoft, and other active members of the container ecosystem. We will add more Docker Engine functionality to containerd so that containerd 1.0 will provide all the core primitives you need to manage containers with parity on Linux and Windows hosts:

Container execution and supervision
Image distribution
Network Interfaces Management
Local storage
Native plumbing level API
Full OCI support, including the extended OCI image specification

When containerd 1.0 implements that scope, in Q2 2017, Docker and other leading container systems, from AWS ECS to Microsoft ACS, Kubernetes, Mesos or Cloud Foundry will be able to use it as their core container runtime. containerd will use the OCI standard and be fully OCI compliant.

Over the past 3 years, the adoption of containers with Docker has triggered an unprecedented wave of innovation in our industry. We think containerd will unlock a whole new phase of innovation and growth across the entire container ecosystem, which in turn will benefit every Docker developer and customer.
You can find up-to-date roadmap, architecture and API definitions in the Github repository, and more details about the project in our engineering team’s blog post. We plan to have a summit at the end of February to bring in more contributors, stay tuned for more details about that in the next few weeks.
Thank you to Arnaud Porterie, Michael Crosby, Mickaël Laventure, Stephen Day, Patrick Chanezon and Mike Goelzer from the Docker team, and all the maintainers and contributors of the Docker project for making this project a reality.

Introducing containerd &8211; a core container runtime project for the industryClick To Tweet

The post containerd &8211; a core container runtime project for the industry appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

da Agency

More details about containerd, Docker’s core container runtime component

Today we announced that Docker is extracting a key component of its #container platform, a part of the engine plumbing–#containerd a core container runtime&8211;and commits to donating it to an open foundation. containerd is designed to be less coupled, and easier to integrate with other tools sets. And it is being written and designed to address the requirements of the major cloud providers and container orchestration systems.
Because we know a lot of Docker fans want to know how the internals work, we thought we would share the current state of containerd and what we plan for version 1.0. Before that, it’s a good idea to look at what Docker has become over the last three and a half years.
The Docker platform isn’t a container runtime. It is in fact a set of integrated tools that allow you to build ship and run distributed applications. That means Docker handles networking, infrastructure, build, orchestration, authorization, security, and a variety of other services that cover the complete distributed application lifecycle.

The core container runtime, which is containerd, is a small but vital part of the platform. We started breaking out containerd from the rest of the engine in Docker 1.11, planning for this eventual release.
This is a look at Docker Engine 1.12 as it currently is, and how containerd fits in.

You can see that containerd has just the APIs currently necessary to run a container. A GRPC API is called by the Docker Engine, which triggers an execution process. That spins up a supervisor and an executor which is charged with monitoring and running containers. The container is run (i.e. executed) by runC, which is another plumbing project that we open sourced as a reference implementation of the Open Container Initiative runtime standard.
When containerd reaches 1.0, we plan to have a number of other features from Docker Engine as well.

That feature set and scope of containerd is:

A distribution component that will handle pushing to a registry, without a preferencetoward a particular vendor.
Networking primitives for the creation of system interfaces and APIs to manage a container’s network namespace
Host level storage for image and container filesystems
A GRPC API
A new metrics API in the Prometheus format for internal and container level metrics
Full support of the OCI image spec and runC reference implementation

A more detailed architecture overview is available in the project’s GitHub repository.
This is a look at a future version of Docker Engine leveraging containerd 1.0.

containerd is designed to be embedded into a larger system, rather than being used directly by developers or end-users; and in fact this evolution of Docker plumbing will go unnoticed by end-users. It has a CLI, ctr, designed for debugging and experimentation, and a GRPC API designed for embedding. It’s designed as a plumbing component, designed to be integrated into other projects that can benefit from the lessons we’ve learned running containers.
We are at containerd version 0.2.4, so a lot of work needs to be done. We’ve invited the container ecosystem to participate in this project and are please to have support from Alibaba, AWS, Google, IBM and Microsoft who are providing contributors to help developing containerd. You can find up-to-date roadmap, architecture and API definitions in the github repo, and learn more at the containerd livestream meetup Friday, December 16th at 10am PST. We also plan to organize a summit at the end of February to bring contributors together.

More details about containerd, @Docker’s core container runtime componentClick To Tweet

The post More details about containerd, Docker’s core container runtime component appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/