Category

Blog

OCI Member Spotlight: OpenStack (Kata Containers)

By Blog

The OCI community is comprised of a diverse set of member organizations that are committed to creating open industry standards around a container image format and runtime. This blog series highlights OCI members and their contributions to building an open, portable and vendor neutral specification.

Name: Xu Wang
Title: CTO + Kata Architecture Committee member
Company: Hyper.sh + Kata Containers

What is Kata Containers?

Kata Containers is an open source project hosted by the OpenStack Foundation that provides lightweight virtual machines that feel and perform like containers, while providing the workload isolation and security advantages of traditional VMs.

Why did OpenStack (Kata Containers) join OCI?

The Kata Containers project runs containers specified by OCI runtime spec in virtual machines. We joined OCI to guarantee the compatibility between Kata Containers and OCI runtime specs, and to help to improve the OCI specifications – enabling more efficient Kata Containers. We look forward to collaborating around tooling, compatibility and interoperability testing.

How can OCI community members contribute to Kata Containers? 

Many of the Kata community members come from the OCI community, so we look forward to more collaboration on use case sharing, specification discussion, testing and toolchains. See Github for more information: https://github.com/kata-containers/community

How do you anticipate OCI changing the container technology landscape? 

The OCI specs guarantee that container technology can be open, vendor neutral and a cornerstone of future computing infrastructure.

What is the benefit of open standards like OCI for users of Kata Containers?

The open and unified container spec gives users more options and helps Kata to be adopted in more cases.

More and more applications are shipped and run under OCI specs. With OCI, Kata could enable users to launch unified container applications no matter if the runtime isolation technology is namespace or VM.

For cloud providers, if a user application has been developed for OCI specs, they could run the application with Kata Containers directly which introduces fewer layers than running a container orchestration system on a VM pool.

On the other hand, for those users who have already invested in VM technology, they could apply their existing tools to Kata Containers and move their application to microservice with OCI containers.

Teaming up with Docker to Support a Diverse Container Ecosystem

By Blog

With a commitment to driving inclusivity in the community, OCI is proud to be an official Diversity Scholarship sponsor for DockerCon 2018.

By actively seeking ways to increase the ecosystem’s diversity, OCI + Docker’s collective goal is to make DockerCon a safe place for everyone to learn and collaborate.

The scholarship program will provide under represented members across the global container community with a scholarship to attend the annual event.

To learn more, make sure to check out the selection process, scholarship details and requirements below + don’t forget to submit an application by Wednesday, April 25, 2018 at 5:00PM PST!

Apply Now!

Selection Process:

A committee of Docker community members will review and select the scholarship recipients. Recipients will be notified by the week of May 7, 2018

What’s included:

Full Access DockerCon Conference Pass

Requirements:

Must be able to attend DockerCon US 2018

Must be 18 years old or older to apply

OCI Announces 2018 TOB Election Results

By Blog

By Chris Aniszczyk (@cra)

It’s 2018 and after shipping the v1.0 specifications last year, we’re nearing contributions from 300+ contributors across 70+ organizations. Today the community is hard at work on future versions of OCI, including discussions around a distribution API specification. For more details about releases and specifications in development, please visit  https://github.com/opencontainers.

Also, the OCI Technical Oversight Board (TOB) – comprised of independently elected individuals who provide oversight of the technical leadership and serve as a point of appeal – just elected the following five board members to each serve a two-year term, effective immediately:

  • Taylor Brown (Microsoft)
  • Stephen Day (Docker)
  • Phil Estes (IBM)
  • Jon Johnson (Google)
  • Mrunal Patel (Red Hat)

These newest TOB members join the following existing members, who are each in the middle of a two-year term:

  • Vincent Batts (Red Hat)
  • Michael Crosby (Docker)
  • Vishnu Kannan (Google)
  • Greg Kroah-Hartman (Linux Foundation)

The TOB also voted to elect Michael Crosby (Docker) as the new Chair. This new TOB lineup is responsible for adding, removing or reorganizing OCI Projects – to learn more, you can follow the TOB on GitHub here.

I’d also like to extend a big thank you to all of our outgoing TOB members – Chris Wright, Diogo Mónica, Jason Bouzane, John Gossman and former Chair, Brandon Philips – for their service and commitment. We look forward to your continued collaboration with and participation in OCI!

Next month, new TOB member Phil Estes of IBM will represent OCI on a panel at Container World on 2/28. Visit http://bit.ly/2Bsr5Gl to learn more about his involvement in this session!

As always, we welcome any/all contributions from the container community – as our success banks on the support and collaboration of many. If you’re interested in contributing to OCI, please join the OCI developer community. For those who are building products on OCI technology, we recommend joining as a member and participating in the future certification program.

Between our exciting new TOB, upcoming releases and a number of exciting community programs we have in the works, we’re on track to make 2018 our biggest year yet 👍🏼

OCI Member Spotlight: Kontena

By Blog

The OCI community is comprised of a diverse set of member organizations that are committed to creating open industry standards around a container image format and runtime. This blog series highlights OCI members and their contributions to building an open, portable and vendor neutral specification.

Name: Miska Kaipiainen
Title: Founder & CEO
Company: Kontena, Inc.

Why did you join OCI?
We see OCI as the most important organization in the container ecosystem driving vendor neutrality, standardization and making this amazing technology accessible globally. Just like many other companies working with containers, we are strong believers in open source, open APIs and open ecosystems in general. We joined OCI to contribute to its mission which helps us and everyone else in this industry to be successful.

How is your organization involved in OCI?
We plan to take an active role in collaboratively on improving OCI specifications, tooling and look forward to being more engaged with other members.

What are the aspects of the runtime spec and/or image format spec that you are looking forward to most for your company?
We enjoy vendor neutrality and collaboration for developing container runtimes that are based on open standards.

How do you plan to use the runtime spec and/or image format spec?
We want to incorporate and support the runtime spec in our Kontena Platform open source project, via runC. Soon, we also plan to support the image spec in our own hosted image registry service.

How will these specifications help your business?
These specifications will provide our users with the confidence to get started with containers while having the promise of no vendor lock-in. In addition, these specifications have stabilized some of the core technology components we use.

How do you anticipate OCI changing the container technology landscape?
OCI has already shown its ability to create solid standards and specifications for an industry that’s moving at the speed of light. This community’s work has already produced amazing results through increased interoperability, recognition and adoption. However, there are still so many things we can accomplish with collaboration to help ensure open standards, interoperability and vendor neutrality.

What do you believe the benefits of using a runtime and image spec based on the OCI standard are for hosting providers? For small ISVs, application developers? For end users?
The benefit of using a runtime and image spec based on OCI is the ability to develop and package once, distribute, deploy and run anywhere. We predict that more vendors will be bringing out runtimes that do their own magic to benefit their specific end users. We’ve always been believers in this market not being a “one solution for all” type of situation, as there are a multitude of users, use cases and needs that no one solution can single handedly meet. Open APIs and standards will enable more vendors to build meaningful solutions that will then benefit the end user with more choice and less lock-in through easier interchangeability of components.

What advice would you give to someone considering joining OCI?
Get on-board and help shape the industry from the inside rather than staying out!

OCI Update: v1.0.1 Release and New Maintainer

By Blog

The OCI community continues to be hard at work, having just issued the first update to OCI v.1.0, after five months of focusing on stability. OCI 1.0.1 contains updates to both the image format and runtime specifications.

We’re still growing and expanding, with even more collaboration since the launch of v 1.0. For example, we are now up to over 5,000 commits from 184 authors across 42 different organizations. Organizations like AWS, Docker, Cloud Foundry, CoreOS, Intel, Mesosphere, Oracle, Red Hat and Kubernetes have already taken advantage of the OCI v1.0 specifications, and with v1.0.1 now available, the industry is on the precipice of true portability and standardization. We had a strong showing on site at recent industry events, at both DockerCon Europe in Copenhagen and Open Source Summit Europe in Prague.

We are also happy to welcome Ma Shimiao as a new maintainer on the image-tools project. Ma joins Aleksa Sarai and Keyang Xie of the image format spec as the newest OCI maintainers, all of whom has been hard at work.  

Concurrently, we are gearing up for the next phase in ensuring broad adoption of common container image format and runtime specs as we prepare to launch an OCI certification/conformance program. This program will allow folks to be confident that their OCI solutions meet a high set of criteria that deliver interoperable solutions. We’ll be presenting a session on Container Runtime & Image Format Standards: What it Means to be ‘OCI-certified during CloudNatvieCon + KubeCon in Austin, Texas on Wednesday, December 6 at 11:10 am. If you’ll be on site, please stop by our booth and check the schedule for additional OCI-related sessions

OCI is always welcoming contributions from across the industry, so please join us! Follow us via @OCI_ORG, and if you’re interested in contributing to the technology, please join the OCI developer community which is open to everyone. If you’re building products on OCI technology, we recommend joining as a member and participating in the upcoming certification program.

 

OCI Member Spotlight: InfoSiftr

By Blog

The OCI community is comprised of a diverse set of member companies that are committed to creating open industry standards around a container image format and runtime. This blog series highlights OCI members and their contributions to building an open, portable and vendor neutral specification.  

Name: Tianon Gravi
Title: SVP of Operations
Company: InfoSiftr

Why did you join OCI and how is your organization involved?
The Open Container Initiative (OCI) is a critical open source organization helping ensure compatibility and interoperability for the basic components of containers. We believe in the mission of the OCI and, as contributors and maintainers in the container ecosystem, will continue to lend expertise and effort to further the group’s goals. On an individual level, I have been involved since the foundation of OCI and am a member of the OCI’s Technical Developer Community (TDC), having worked on the container runtime specifications since the foundation of the OCI.

What are the aspects of the the runtime spec and/or image format spec that you are looking forward to most for your company?
By encouraging standardization and interoperability, the specs help enable differentiation further up the stack, where it benefits all users.  Additionally, companies can feel safer in adopting containers knowing that at a foundational level, they aren’t locked into any one vendor’s solution (which is all thanks to these low-level standards).

How do you plan to use the runtime spec and/or image format spec?
Any development work we do in the container space will adhere to OCI specifications, and encourage their use and furtherance within the ecosystem.

How will these specifications help your business?
The specifications will help all businesses with an interest in containers, whether they are contributing to the container ecosystem or just consuming container-based technology.  This flexibility helps us in our own day-to-day operations, but also helps our clients as they evaluate and commit to container-based solutions and deployments.

How do you anticipate OCI changing the container technology landscape?  
The OCI’s standards create a “baseline for competition.”  Now that we have an agreed upon foundation, companies can proceed to innovate and compete in more interesting ways.

What do you believe the benefits of using a runtime and image spec based on the OCI standard are for hosting providers?  For small ISVs, application developers? For end users?
If you’re doing anything in technology, it’s useful to adhere to standards. Much of the container ecosystem is still new and evolving, and we’re bound to see changes to technology stacks going forward. Adhering to the specifications set forth by the OCI means we all agree the underlying details of our tooling and products will be compatible and interoperable, whatever higher-level changes may come.

What advice would you give to someone considering joining OCI?
Contributing to the underlying specifications of the container ecosystem is sometimes difficult and involved work, but it can be very rewarding. Joining the OCI is a great way to start doing exactly that: https://www.opencontainers.org/join

 

 

OCI Welcomes New Project Maintainers

By Blog

Following the recent release of OCI v1.0 (runtime-spec / image-spec) and a summer break, the work continues and the community is busy.

We had a great panel and strong showing on site at Open Source Summit North America last week in Los Angeles, entitled, “Open Container Initiative: What’s Next For Standards and Container Portability?”.

Furthermore, we’re partnering with Docker to support diversity and inclusivity at DockerCon Europe as one of the official DockerCon Europe Diversity Scholarship sponsors. We continue to work towards our certification program, due out in the near future.

Additionally, the community has just elected two new maintainers for the OCI image specification:

Both Aleksa and Keyang have been fantastic contributors to the OCI community. According to fellow maintainers, Aleksa has been invaluable with feedback, brainstorming and fixes/features all the way through the stack while Keyang has heavily contributed to improved overall quality and testing of the image specification.

As always, contributions from across the industry are welcome; our success depends on the support and collaboration of many. If you’re interested in contributing, please join the OCI developer community which is open to anyone. If you’re building products based on OCI technology, we recommend joining as a member and participating in the upcoming certification program.

OCI Member Spotlight: EasyStack

By Blog

The OCI community is comprised of a diverse set of member companies that are committed to creating open industry standards around a container image format and runtime. This blog series highlights OCI members and their contributions to building an open, portable and vendor neutral specification.  

Name: Guohui Liu
Title: Co-founder and CTO
Company: EasyStack

Why did you join OCI?
Trends in cloud native computing are still on the rise. Businesses are evolving faster than ever before as applications require more agile and scalable infrastructure, and container technology is right at the center of it all. Unified standards are imperative for container technology to evolve and develop, with input and participation from the entire ecosystem. We believe the Open Container Initiative (OCI), with its runtime and image format specifications, plays a leading role in actualizing the ability to “package once, run anywhere” for applications.

Openness is a part of EasyStack’s DNA. We believe container technology will fill the gap between traditional IT and cloud native IT. We are among the first to release a converged infrastructure cloud platform featuring both containers and OpenStack cloud, and are looking forward to sharing our rich experiences with enterprise cloud native infrastructure offerings with the global OCI community.

How is your organization involved in OCI?
EasyStack is an active participant in the broader open source community, and we believe it is equally important to contribute to upstream open source projects to help address enterprise customer needs. Today — based on OpenStack, Kubernetes, Docker, Ceph and other open source technologies– EasyStack provides an open, secure, stable, reliable, and high-performance cloud computing capability for 200+ enterprise customers for their cloud infrastructure. As part of OCI, we are sharing our enterprise cloud and application model experience with the upstream community.  

What are the aspects of the runtime spec and/or image format spec that you are looking forward to most for your company?
The runtime spec and image format spec provide container standards, which is very important to both vendors and users. Trends in cloud native are encouraging more and more enterprise users to deploy containers, and many of them are already in production. This means reliability and consistent upgrades are extremely important. Additionally, API compatibility and scalability is imperative, especially in customized enterprise scenarios.

How do you plan to use the runtime spec and/or image format spec?
We leverage OCI v1.0 the runtime spec in our ESContainer Linux already, providing a reliable and stable container runtime. This allows us to focus on the development of true application-oriented orchestration, leveraging additional technologies such as Kubernetes.

How will these specifications help your business?
These specifications provide standardized and reliable image format and runtime specifications, allowing us to better and more efficiently develop ESContainer, shortening the development cycle. With these standards, the infrastructure provided by different vendors is of the same API so this avoids vendor lock-in, which helps our business to reduce risk (as well as costs, which in turn yields higher profits).  

What do you believe the benefits of using a runtime and image spec based on the OCI standard are for hosting providers?  For small ISVs, application developers? For end users?
OCI’s runtime and image format specs help all types of customers. The use of one standardized spec enables container applications to be deployed, run, and updated in a multi-cloud environment (e.g. public cloud, private cloud or community cloud) more quickly and efficiently. This is extremely helpful in today’s hybrid cloud environment and both the hosting providers and the end users will benefit from it.

ISVs and application developers now have standards to follow, which can help reduce the risk of going in the wrong direction while avoiding vendor lock-in as they build container applications.

What advice would you give to someone considering joining OCI?
If you and/or your organization’s vision align with current cloud native trends, just join OCI. Today, it is almost impossible for one company to really dominate one hot technology and at the same time keep it active and advanced. Open technologies have proven successful for rapid development, and OCI is a great example of this. New members to the OCI community can get started quickly with shared resources and support from across the community, in addition to having fun by contributing back.

Fostering Diversity and Inclusivity at DockerCon Europe

By Blog

It’s incredibly important to the Open Container Initiative (OCI) community, as well as the larger container ecosystem, to build a community of inclusiveness that helps provide opportunities to underrepresented and disadvantaged groups around the world. We strongly believe the power of collaboration is heightened when many different perspectives are included, with massive benefits to the broader tech ecosystem.

To that end, we are pleased to help underrepresented members of the container community the opportunity to attend DockerCon Europe (October 16-19) in Copenhagen this year as one of the official DockerCon Europe Diversity Scholarship sponsors! Together with Docker, we’re helping to foster inclusivity by providing a financial scholarship – including conference pass, airfare, hotel accommodations, and a mentorship – to those who may not have the resources or support to attend on their own. Winners of the scholarship will also receive hands-on access to the resources, tools, and community support needed to further accelerate educational and career growth.  

Applications are due Tuesday, 5 September, 2017 at 5:00PM PST. More details on the program and how to apply are available here: https://blog.docker.com/2017/08/dockercon-europe-diversity-scholarship/

DockerCon is one of the container industry’s premiere events where practitioners come to learn from enthusiasts and experts. It’s all about learning, sharing, connecting, and innovating on the next generation distributed systems.

We plan on sharing a booth with our sister Linux Foundation collaborative project, the Cloud Native Computing Foundation (CNCF). Please stop by the booth to learn more about OCI, CNCF, the wider Linux Foundation container ecosystem, and how OCI integrates with the CNCF community and projects (Kubernetes, Prometheus, OpenTracing, Fluentd, Linkerd, gRPC, CoreDNS, containerd, rkt and CNI).

As always, we  encourage you to look for ways to get involved in OCI, either as an official member or as part of our open developer community.