Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[doc] 3.3.1 Environment Description - load balancer message "wrong"? #824

Closed
Martin-Weiss opened this issue May 26, 2020 · 7 comments
Closed
Assignees
Labels
Blocked Blocked by lack of information or external factors DeploymentGuide Fix will change the Deployment Guide EngineeringInput NeedsEngineering Input
Milestone

Comments

@Martin-Weiss
Copy link
Contributor

3.3.1 Environment Description

https://susedoc.github.io/doc-caasp/master/single-html/caasp-deployment/#_environment_description


This seems to be outdated:

This will be added in future versions. You must provide your own load balancing solution that directs access to the master nodes.

-> we have the nginx and haproxy load balancer examples in this guide - so maybe just link it?

@r0ckarong
Copy link
Contributor

This box is related to the VMWare deployment and we do not provide any information on how to set up load balancer in a VMWare environment (yet). From what I recall we rely on the VMWare administrator to know how to set up load balancing in their environment. I will change the wording slightly to reflrect this box is directly talking about VMWare.

@r0ckarong r0ckarong self-assigned this Jun 2, 2020
@r0ckarong r0ckarong added the DeploymentGuide Fix will change the Deployment Guide label Jun 2, 2020
@r0ckarong r0ckarong added this to the Sprint 31 milestone Jun 2, 2020
@Martin-Weiss
Copy link
Contributor Author

This box is related to the VMWare deployment and we do not provide any information on how to set up load balancer in a VMWare environment (yet). From what I recall we rely on the VMWare administrator to know how to set up load balancing in their environment. I will change the wording slightly to reflrect this box is directly talking about VMWare.

See https://susedoc.github.io/doc-caasp/master/single-html/caasp-deployment/#loadbalancer - this is not "environment specific" at all. And even in the terraform for VMware we deliver "segments" of the load balancer configuration for VMware.. ;-).

@r0ckarong
Copy link
Contributor

@thehejik @kkaempf Are both nginx and haproxy tested on VMWare? If so can I just assume they can be deployed like for any other platform?

@r0ckarong r0ckarong reopened this Jun 2, 2020
@kkaempf
Copy link
Member

kkaempf commented Jun 2, 2020

@fgerling - can you answer this ?

@thehejik
Copy link
Contributor

thehejik commented Jun 2, 2020

It wasn't tested for quite some time.

The info in doc should be suitable for any platform if you configure it manually.

We are not delivering haproxy nor nginx code in terraform states to customers, although skuba master branch has the haproxy lb tf code available for vmware and kvm/libvirt but for development purposes only (we are removing it by skuba patch in IBS).

@r0ckarong
Copy link
Contributor

It wasn't tested for quite some time.

The info in doc should be suitable for any platform if you configure it manually.

We are not delivering haproxy nor nginx code in terraform states to customers, although skuba master branch has the haproxy lb tf code available for vmware and kvm/libvirt but for development purposes only (we are removing it by skuba patch in IBS).

What is the correct procedure to deploy a load balancer for a VMWare environment? Deploy the same template you use for the rest of the cluster nodes and deploy LB software on it and configure? And then proceed with the actual cluster setup?

@r0ckarong r0ckarong added Blocked Blocked by lack of information or external factors EngineeringInput NeedsEngineering Input labels Jun 3, 2020
@Martin-Weiss
Copy link
Contributor Author

Either setup a single VM with SLES and install haproxy package or setup a SLE-HA cluster in VMs.

Then configure haproxy based on the documented haproxy.conf adjusted to the names of your masters/workers.

Create a DNS entry for "api" pointing to the load balancers VIP and then deploy the cluster using skuba.

P.S. in the meantime we might not need to document / recommend the nginx "workaround" anymore - as haproxy supported is available via SLE-HA (if customer wants it supported) or haproxy is also available "unsupported" via the packagehub channel...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blocked Blocked by lack of information or external factors DeploymentGuide Fix will change the Deployment Guide EngineeringInput NeedsEngineering Input
Projects
None yet
Development

No branches or pull requests

4 participants