Bug 6128 - Stateless VSM Server for elastic cloud like deployments
Summary: Stateless VSM Server for elastic cloud like deployments
Status: CLOSED DUPLICATE of bug 6127
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Server (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.16.0
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-10 12:45 CET by Karl Mikaelsson
Modified: 2023-09-12 13:37 CEST (History)
1 user (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Karl Mikaelsson cendio 2017-01-10 12:45:32 CET 
In a computing world that moves towards a more dynamic approach to servers and services, having VSM server as a stateful service is a roadblock to being able to provide high availability and redundancy for a server cluster.

The modern approach to high availability is to have stateless services that read configuration and state from external services. If a service fails, trash the entire VM/container the service runs in and start a new VM from a known state.
Comment 1 Karl Mikaelsson cendio 2018-09-25 15:03:23 CEST 
Additional reading/inspiration:

 https://12factor.net/
Comment 2 Karl Mikaelsson cendio 2018-09-25 15:06:14 CEST 
Related bugs:

 Bug 6127 - Support HA over more than two vsmservers
Comment 3 Pierre Ossman cendio 2023-09-12 13:37:31 CEST 
vsmserver MUST have state as it needs to keep track of session information. If you move it to something else, you've just move the vsmserver role somewhere else, effectively just renaming it.

Since the initial description states that this is about redundancy, I'll mark it as duplicate of bug 6127.

*** This bug has been marked as a duplicate of bug 6127 ***
Note You need to log in before you can comment on or make changes to this bug.