Ampere Computing's platforms are uniquely designed to meet the needs of the modern cloud native workload. Ampere's CIDR regression infrastructure uses images taken from a variety of sources. In this case, Gvisor tracks the open source project found [here] (https://github.com/google/gvisor). The regression runs on bare metal rather than in a container. Results are found below in the Test Results section of this page.
gVisor is a container sandbox developed by Google that focuses on security, efficiency and ease of use released on May 2018. gVisor implements around 200 of the Linux system calls in userspace, for additional security compared to Docker containers that run directly on top of the Linux kernel and are isolated with namespaces. Contrary to the Linux kernel the project is written in the memory-safe programming language Go to prevent common pitfalls which frequently occur with software written in C. gVisor is being used in Google's production environment like App Engine standard environment, Cloud Functions, Cloud ML Engine and Google Cloud Run according to Google and Brad Fitzpatrick. Most recently gVisor has been integrated with Google Kubernetes Engine and it allows users to sandbox their Kubernetes pods for use cases like SaaS and multitenancy.
This article uses material from the Wikipedia article [gvisor] (https://en.wikipedia.org/wiki/GVisor) , which is released under the Creative Commons Attribution-Share-Alike License 3.0.
Here at Ampere we've built an extensive infrastructure focused on Continuous Integration, Delivery, and Regression (called CIDR).
Results are categorized as either 'Verified' or 'Unverified'.
Verified: Everything ran according to plan and results came back positive
Unverified: We couldn't collect a result due to an issue within the test infrastructure. When we root-cause an Unverified result the write-up will appear in the Test Notes section of this page. An unverified test result does not imply an issue with the software under test - it means only that Ampere was unable to confirm one or more steps in our verification process.
Test and build infrastructure can encounter complexities or unexpected speed bumps. Known incidents and their resolutions will be documented where applicable.
0% Verified / 100% Unverified
|Test||Result||Most Recent Hash|
|Basic Functional Test|