s
This commit is contained in:
@@ -1,5 +0,0 @@
|
||||
|
||||
## Zero-Images: A New Way Of Dealing With OS Images
|
||||
|
||||
!!wiki.include page:flist_innovation_short
|
||||
|
4
collections/tech/innovations/compute/zero_deploy_inno.md
Normal file
4
collections/tech/innovations/compute/zero_deploy_inno.md
Normal file
@@ -0,0 +1,4 @@
|
||||

|
||||
|
||||
|
||||
!!wiki.include page:'zero_deploy.md'
|
@@ -1,11 +1,20 @@
|
||||
|
||||
|
||||

|
||||
|
||||
|
||||
### The Problem
|
||||
|
||||
The current method of deploying workloads in the cloud using Docker containers and virtual machine images has inherent issues. These images consume significant storage space, result in slow and bandwidth-intensive transfers to the internet's edge, drive up costs, introduce complexity, and pose security risks due to difficulties in tracking their contents over time.
|
||||
|
||||
For instance, a complete Ubuntu image can easily be 2 GB in size, comprising millions of files. In contrast, the Flist for a full Ubuntu image is less than 2 MB (1000 times smaller), containing only the necessary files required to launch an application.
|
||||
For instance, a complete Ubuntu image can easily be 2 GB in size, comprising millions of files. In contrast, the Flist (metadata for Zero-Image) for a full Ubuntu image is less than 2 MB (1000 times smaller). Based on this flist only the required files will be dowbloaded which can easily be 10x less compared to the original image size. These downloaded files (or subparts of files) are identified by a fingerprint (hash) and will only boot once authenticity can be verified.
|
||||
|
||||
|
||||
### Process
|
||||
|
||||
- Zero-OS or the Zero-Image Command Line (works on linux) gets informed to provision a virtual filesystem based on a Zero-Image URL.
|
||||
- The Zero-Image Metadata is stored on e.g. an S3 Server or our [Zero-Hub](zero_hub.md)
|
||||
|
||||
|
||||
### Introducing Flist
|
||||
|
@@ -0,0 +1 @@
|
||||
!!wiki.include page:zero_install.md
|
@@ -4,4 +4,4 @@ Zero-OS is our innovative operating system built from the Linux kernel.
|
||||
|
||||

|
||||
|
||||
!!wiki.include page:zos_innovation_short
|
||||
!!wiki.include page:zos_inno0
|
@@ -1,7 +1,11 @@
|
||||
|
||||
### The Problem
|
||||
|
||||
It is challenging to use current Linux-based operating systems safely and efficiently on the edges of the Internet. They require central management, involve excessive complexity, and prove difficult to update and maintain, resulting in numerous security vulnerabilities. To revolutionize the internet, we must rethink how we host our applications, essentially reinventing the concept of a cloud-based operating system.
|
||||
It is challenging to use current Linux-based operating systems safely and efficiently on the edges of the Internet.
|
||||
|
||||
They require central management, involve excessive complexity, and prove difficult to update and maintain, resulting in numerous security vulnerabilities.
|
||||
|
||||
To revolutionize cloud and the internet, we must rethink how we host our applications, essentially reinventing the concept of a cloud-based operating system.
|
||||
|
||||
### Introducing Zero-OS
|
||||
|
Reference in New Issue
Block a user