Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

Document cloud provider instances with KVM support #222

Merged
merged 11 commits into from
Aug 8, 2019
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -75,6 +75,8 @@ Please check out the [Releases Page](https://github.com/weaveworks/ignite/releas

How to install Ignite is covered in [docs/installation.md](https://ignite.readthedocs.io/en/latest/installation.html).

Guidance on Cloud Providers' instances that can run Ignite is covered in [docs/cloudprovider.md](docs/cloudprovider.md).

## Getting Started

**WARNING**: In it's `v0.X` series, Ignite is in **alpha**, which means that it might change in backwards-incompatible ways.
Expand Down
40 changes: 40 additions & 0 deletions docs/cloudprovider.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@


## Cloud Provider KVM supported instances

If you intend to use a cloud provider to test Ignite, you can use the instructions below to provision an instance that satisfies the KVM system requirements described in the [installation guide](./installation.md).

### Amazon Web Services

#### Amazon EC2 Bare Metal Instances

Amazon EC2 [bare metal instances](https://aws.amazon.com/about-aws/whats-new/2018/05/announcing-general-availability-of-amazon-ec2-bare-metal-instances/) provide direct access to the Intel® Xeon® Scalable processor and memory resources of the underlying server. These instances are ideal for workloads that require access to the hardware feature set (such as Intel® VT-x), for applications that need to run in non-virtualized environments for licensing or support requirements, or for customers who wish to use their own hypervisor.

Here's a list of instances with KVM support, with pricing (as of July 2019), to help you test Ignite. All the instances listed below are EBS-optimized, with 25 Gigabit available network performance and IPv6 support.

| Family | Type | Pricing (US-West-2) per On Demand Linux Instance Hr | vCPUs | Memory (GiB) | Instance Storage (GB) |
| ---- | ---- | :----: | :----: | :----: | ---- |
|Compute optimized | c5.metal | $4.08 | 96 |192 |EBS only |
| General purpose | m5.metal | $4.608 | 96 | 384 | EBS only |
| General purpose | m5d.metal | $5.424 | 96 | 384 |4 x 900 (SSD) |
|Memory optimized| r5.metal| $6.048 |96 |768| EBS only|
|Memory optimized| r5d.metal| $6.912 | 96 |768 |4 x 900 (SSD)|
|Memory optimized| z1d.metal| $4.464 | 48 |384 |2 x 900 (SSD)|
|Storage optimized| i3.metal| $4.992 | 72 | 512 | 8 x 1900 (SSD) |

Use the AWS console to [launch one of these instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/LaunchingAndUsingInstances.html) and [connect to your instance using SSH](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html). Then, follow the instructions in the [installation guide](./installation.md).

### Google Cloud (Source: https://blog.kubernauts.io/ignite-on-google-cloud-5d5228a5ffec)

Use Google compute from a custom KVM image so that Ignite can be installed and run easily.
- Login to Google cloud console
- Open Google cloud shell
- run the following command to create custom images with KVM enabled
```
gcloud compute images create nested-virt \
--source-image-project=ubuntu-os-cloud \
--source-image-family=ubuntu-1604-lts \
--licenses="https://www.googleapis.com/compute/v1/projects/vm-options/global/licenses/enable-vmx"
```
- Create a compute Engine with the custom image created

2 changes: 2 additions & 0 deletions docs/installation.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,8 @@ This guide describes the installation and uninstallation process of Ignite.
Ignite runs on any Intel-based `linux/amd64` system with `KVM` support.
AMD support is in alpha (Firecracker limitation).

See [cloudprovider.md](cloudprovider.md) for guidance on running Ignite on various cloud providers and suitable instances that you could use.

**Note**: You do **not** need to install any "traditional" QEMU/KVM packages, as long as
there is virtualization support in the CPU and kernel it works.

Expand Down