You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+15-10Lines changed: 15 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,18 +7,21 @@
7
7
8
8
## What is flintlock?
9
9
10
-
Flintlock is a service for creating and managing the lifecycle of microVMs on a host machine. Initially we will be supporting [Firecracker](https://firecracker-microvm.github.io/).
10
+
Flintlock is a service for creating and managing the lifecycle of microVMs on a host machine. We support [Firecracker](https://firecracker-microvm.github.io/) and [Cloud Hypervisor](https://www.cloudhypervisor.org/) (experimental).
11
11
12
-
The primary use case for flintlock is to create microVMs on a bare-metal host where the microVMs will be used as nodes in a virtualized Kubernetes cluster. It is an essential part of [Liquid Metal](https://www.weave.works/blog/multi-cluster-kubernetes-on-microvms-for-bare-metal) and will ultimately be driven by Cluster API Provider Microvm (coming soon).
12
+
The original use case for flintlock was to create microVMs on a bare-metal host where the microVMs will be used as nodes in a virtualized Kubernetes cluster. It is an essential part of [Liquid Metal](https://www.weave.works/blog/multi-cluster-kubernetes-on-microvms-for-bare-metal) and can be orchestrated by [Cluster API Provider Microvm](https://github.com/weaveworks-liquidmetal/cluster-api-provider-microvm).
13
+
14
+
However, its useful for many other use cases where lightweight virtualization is required (e.g. isolated workloads, pipelines).
13
15
14
16
## Features
15
17
16
18
Using API requests (via gRPC or HTTP):
17
19
18
-
- Create and delete microVMs using Firecracker
20
+
- Create and delete microVMs
19
21
- Manage the lifecycle of microVMs (i.e. start, stop, pause)
20
22
- Configure microVM metadata via cloud-init, ignition etc
21
23
- Use OCI images for microVM volumes, kernel and initrd
24
+
- Expose microVM metrics for collection by Prometheus
22
25
- (coming soon) Use CNI to configure the network for the microVMs
23
26
24
27
## Documentation
@@ -50,13 +53,15 @@ Your feedback is always welcome!
50
53
51
54
The table below shows you which versions of Firecracker are compatible with Flintlock:
Copy file name to clipboardExpand all lines: api/services/microvm/v1alpha1/microvms.swagger.json
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -341,6 +341,10 @@
341
341
"uid": {
342
342
"type": "string",
343
343
"description": "UID is a globally unique identifier of the microvm."
344
+
},
345
+
"provider": {
346
+
"type": "string",
347
+
"description": "Provider allows you to specify the name of the microvm provider to use. If this isn't supplied\nthen the default provider will be used."
344
348
}
345
349
},
346
350
"description": "MicroVMSpec represents the specification for a microvm."
0 commit comments