Unit Tests
Integration Tests
vHive CRI tests
Go Report Card
License: MIT

vHive Header

Mission

vHive aims to enable serverless systems researchers to innovate across the deep and distributed software stacks
of a modern serverless platform. Hence, we built vHive to be representative of the leading
Function-as-a-Service (FaaS) providers, integrating the same production-grade components used by the providers, including
AWS Firecracker hypervisor,
Cloud Native Computing Foundation’s Containerd,
and Kubernetes.

vHive adopts the Knative flexible programming model, allowing the researchers to quickly deploy
and experiment with any serverless applications that may comprise many functions,
running in secure Firecracker microVMs, as well as serverfull services.
Both the functions and the stateful services can be deployed using OCI/Docker images.

vHive empowers systems researchers to innovate on key serverless features,
including functions autoscaling and cold-start delay optimization with several snapshotting mechanisms.

vHive architecture

vHive Architecture

The details of the vHive architecture can be found in our ASPLOS’21 paper
(extended abstract,
full paper).

Technical talks

Referencing our work

If you decide to use vHive for your research and experiments, we are thrilled to support you by offering
advice for potential extensions of vHive and always open for collaboration.

Please cite our paper that has been recently accepted to ASPLOS 2021:

@inproceedings{ustiugov:benchmarking,
  author    = {Dmitrii Ustiugov and
               Plamen Petrov and
               Marios Kogias and
               Edouard Bugnion and
               Boris Grot},
  title     = {Benchmarking, Analysis, and Optimization of Serverless Function Snapshots},
  booktitle = {Proceedings of the 26th ACM International Conference on
               Architectural Support for Programming Languages and Operating Systems (ASPLOS'21)},
  publisher = {{ACM}},
  year      = {2021},
  doi       = {10.1145/3445814.3446714},
}

Getting started with vHive

vHive can be readily deployed on premises or in cloud, with support for nested virtualization.
We provide a quick-start guide
that describes how to set up an experiment with vHive.

Developing vHive

Developer’s guide and performance analysis with vHive

We provide a basic developer’s guide that we plan to extend in future.
We encourage the community to contribute their analysis scenarios and tools.

vHive roadmap

vHive is a community-led project, maintained by the EASE lab.
The current roadmap is available
and is going to be updated to accommodate the community’s goals and evolution.
To guarantee high code quality and reliability, we deploy fully automated CI
on cloud and self-hosted runners with GitHub Actions.

The statistics of this repository’s views, clones, forks is available by the following
link.

Getting help and contributing

We would be happy to answer any questions in GitHub Issues and encourage the open-source community
to submit new Issues, assist in addressing existing issues and limitations, and contribute their code with Pull Requests.
You can also talk to us on the official Firecracker Slack in the #firecracker-vHive-research channel.

License and copyright

vHive is free. We publish the code under the terms of the MIT License that allows distribution, modification, and commercial use.
This software, however, comes without any warranty or liability.

The software is maintained at the EASE lab in the University of Edinburgh.

Maintainers



Source link