Dear Phil,
One tool to look seriously at, and again this is merely conjecture, might
be "tmux". The really cool thing about tmux is it essentially starts
independent processes or if small scale - threads, and the ability to have
process started on a backup docker image ready to go after the loss of a
"dead man" heartbeat or some such thing might make these dogs hunt. That
said I must now invoke and ask you to sing with me the "Consultants
Creed":
- Free advice is worth exactly what you pay for it. -
(Voice reverently as a Gregorian Chant :^)
On this melody, I will be happy to supply harmony when we next meet. That
said (or sung), if your issues were less interesting I would have way less
in the area of off hand suggestions.
Thanks and...
Kindest Regards,
Flint
On Thu, 27 Oct 2016, PHILIP TULLY wrote:
Date: Thu, 27 Oct 2016 20:56:22 -0400
From: PHILIP TULLY <[email protected]>
Reply-To: Linux on 390 Port <[email protected]>
To: [email protected]
Subject: Re: Docker on Z
The issue here is we have multiple docker engines on multiple lpars ( we
still think from an economics and manageability point of view that under VM
is better than on the metal).
We have been doing the testing to have one engine pick up the workload form
another that has failed, this works.
We are still trying to make the environment more flexible. These docker
engine VMs are sized at 60G and 8 vcpu but can grow (without ipl) to 120G and
16 vcpu's. It is the automation piece to exploit the flexibility of the
platform that we need to figure out. Yes, we can define full and "waste"
resources but at these sizes the resources are big.
On Tue, Oct 25, 2016 at 04:57 PM, R P Herrold wrote:
On Tue, 25 Oct 2016, PHILIP TULLY wrote:
We are looking to implement Docker on Z, as we have begun the testing
part of the issue is to be able to grow a docker engine and growing it
dynamically based on it's current needs especially when a node in the
Docker cluster fails.
So the question is does anyone see a way for the VM system to see the
memory resource grow, which would allow me to add more dynamically.
I thought one point of Docker was to have 'fast to spin up'
instances, ready to spin up, which then pulled in ephemeral
data from a back end persistent store, so that a swarm of them
handled load spikes, and once the spike passes, that the
excess units are shut down
-- Russ herrold
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
Kindest Regards,
☮ Paul Flint
(802) 479-2360 Home
(802) 595-9365 Cell
/************************************
Based upon email reliability concerns,
please send an acknowledgement in response to this note.
Paul Flint
17 Averill Street
Barre, VT
05641
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
