Skip to content
This repository has been archived by the owner on Jan 14, 2020. It is now read-only.

Scale-out on multiple hosts #7

Open
schlomo opened this issue Jul 9, 2013 · 0 comments
Open

Scale-out on multiple hosts #7

schlomo opened this issue Jul 9, 2013 · 0 comments
Labels
enhancement

Comments

@schlomo
Copy link
Contributor

schlomo commented Jul 9, 2013

Goal

Increase service availablibity by running LML on multiple hosts that serve the same DHCP info.

Ideas

  • Use memcache to share the lab.conf information between hosts, each host maintains a local copy on disk as offline persistence
  • Put lab.conf on NAS share (locking!)
  • Pull missing data on-demand instead of depending on lab.conf containing it
schlomo added a commit that referenced this issue Sep 12, 2013
@schlomo
ITPRO-86 Lock write access to lab.conf, fixes #9 and helps #7
0f226e1 
Read-write Lab objects now lock the lab.conf during their entire
life time, thereby guaranteeing that nobody else will use lab.conf in
this time. Read-only Lab objects will wait till another writing process
releases the lock on the lab.conf.

Locks should also work over NFS so that LML can be used on multiple
hosts. However, this is no solution for DHCP leases, only for the LML
state data.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@schlomo