惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

S
SegmentFault 最新的问题
爱范儿
爱范儿
博客园 - 三生石上(FineUI控件)
Microsoft Security Blog
Microsoft Security Blog
Google DeepMind News
Google DeepMind News
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
GbyAI
GbyAI
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
V
V2EX
酷 壳 – CoolShell
酷 壳 – CoolShell
量子位
博客园_首页
T
Tailwind CSS Blog
aimingoo的专栏
aimingoo的专栏
A
About on SuperTechFans
T
The Blog of Author Tim Ferriss
Stack Overflow Blog
Stack Overflow Blog
Recent Announcements
Recent Announcements
P
Proofpoint News Feed
博客园 - 司徒正美
有赞技术团队
有赞技术团队
Engineering at Meta
Engineering at Meta
Last Week in AI
Last Week in AI
MongoDB | Blog
MongoDB | Blog

Open Container Initiative

OCI Runtime Spec v1.3 - Open Container Initiative OCI Image and Distribution Specs v1.1 Releases OCI Runtime Spec v1.2 - Open Container Initiative OCI in 2024 and TOB Election Results Summary of Upcoming Changes in OCI Image and Distribution Specs v1.1 OCI at The Container Plumbing Conference OCI in 2023 and TOB Election Results OCI in 2022 and TOB Election Results OCI Member Spotlight – Chainguard Calling All Registries to Submit OCI Conformance! OCI Summit 2021 - Open Container Initiative Introducing fuzzing for runC and Umoci OCI in 2021 and TOB Election Results Consuming Public Content - Open Container Initiative OCI accepts new project, umoci Introducing and open sourcing the OCI Icon Set Open Sourcing runc Security Audit Container Journal – “OCI Launches Artifacts Project to Reduce Registries Required” New OCI Artifacts Project - Open Container Initiative Open Container Initiative Explained…with Dolls! OCI 2019 Elections and New TOB Lineup 2018’s Biggest Moments + What’s Coming for OCI in 2019 Bringing OCI images to the desktop with Flatpak OCI Image Support Comes to Open Source Docker Registry Open Container Initiative Welcomes Alibaba Cloud as Newest Member PouchContainer – How OCI Specifications Power Alibaba CRI-O – How Standards Power a Container Runtime OCI Member Spotlight – OpenStack (Kata Containers) Teaming up with Docker to Support a Diverse Container Ecosystem The New Stack – “Open Container Initiative Creates a Distribution Specification for Registries”
OCI Member Spotlight – EasyStack
map[name:Open Container Initiative tag:oci] · 2017-09-11 · via Open Container Initiative

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.