Skip to content

Commit

Permalink
Update deployment guide to support KVM
Browse files Browse the repository at this point in the history
The existing bare metal deployment guide is also sufficient for
deployment on KVM machines. This change adds KVM to the list of
supported platforms, makes minor modifications to the deployment
documentation to make that support explicit, adds a note about how to
manage virtual machines, and fixes the load balancer instructions to be
clear that the guide on setting up a load balancer is applicable to both
bare metal and KVM hosts.
  • Loading branch information
cmurphy committed Feb 26, 2020
1 parent f352f20 commit e09ca20
Show file tree
Hide file tree
Showing 5 changed files with 14 additions and 9 deletions.
Binary file added adoc/.deployment-sysreqs.adoc.swp
Binary file not shown.
2 changes: 1 addition & 1 deletion adoc/book_deployment.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ include::deployment-ecp.adoc[SUSE OpenStack Cloud Instructions, leveloffset=+1]

include::deployment-vmware.adoc[VMware Deployment Instructions, leveloffset=+1]

include::deployment-bare-metal.adoc[Bare Metal Install, leveloffset=+1]
include::deployment-bare-metal-or-kvm.adoc[Bare Metal or KVM Install, leveloffset=+1]

include::deployment-sles.adoc[Existing SLES Installation, leveloffset=+1]

Expand Down
Original file line number Diff line number Diff line change
@@ -1,19 +1,23 @@
include::entities.adoc[]

[[deployment_bare_metal]]
== Deployment on Bare Metal
== Deployment on Bare Metal or KVM

.Preparation Required
[NOTE]
You must have completed <<deployment.preparations>> to proceed.

[NOTE]
====
If deploying on KVM virtual machines, you may use a tool such as `virt-manager`
to configure the virtual machines and begin the {sle} 15 SP1 installation.
====

=== Environment Description

[IMPORTANT]
[NOTE]
====
These instructions currently do not describe how to set up a load balancer.
This will be added in future versions. You must provide your own load balancing
solution that directs access to the master nodes.
You must have a load balancer configured as described in <<loadbalancer>>.
====

[NOTE]
Expand All @@ -30,7 +34,7 @@ you must adjust the {ay} file to your needs according to the requirements.
Refer to the official {ay} documentation for more information: link:https://documentation.suse.com/sles/15-SP1/single-html/SLES-autoyast/#book-autoyast[{ay} Guide].
====

==== Hardware Prerequisites
==== Machine Configuration Prerequisites

Deployment with {ay} will require a minimum *disk size of 40 GB*.
10 GB out of that total space will be reserved for container images without any workloads,
Expand Down
4 changes: 2 additions & 2 deletions adoc/deployment-preparation.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -216,8 +216,8 @@ practices.
For {soc}, the {tf} configurations shipped with this version will automatically deploy
a suitable load balancer for the cluster.

For VMware you must configure a load balancer manually and allow it access to
all master nodes created during <<bootstrap>>.
For bare metal, KVM, or VMware, you must configure a load balancer manually and
allow it access to all master nodes created during <<bootstrap>>.

The load balancer should be configured before the actual deployment. It is needed
during the cluster bootstrap, and also during upgrades. To simplify configuration,
Expand Down
1 change: 1 addition & 0 deletions adoc/deployment-sysreqs.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ Currently we support:

* SUSE OpenStack Cloud 8
* VMware ESXi {vmware_version}
* KVM
* Bare Metal x86_64

== Nodes
Expand Down

0 comments on commit e09ca20

Please sign in to comment.