Investigate if there is a better way of handling Container Timer for automatic killing

[a0xnirudh]

As of now we are using hard-coded values like self.timer = "hour" in container_daemon.py. We should investigate if there is a better way of doing the same.

[shubham1337]

Hey!
I found a way to kill the containers based on their network activity, Here's the updated container_daemon.py
Basically, The daemon will now poll every 10 minutes to check the network activity of the containers and kill the ones which have no change in their network activity since last check.
10 minutes is maybe very less for this, we could change that no problem.
What do you think?

[northdpole]

This is a cool idea actually, add it as an option (as in if
config.IDLETIMEOUT == idle_time:
kill(with hatchet))

On 16/03/16 17:24, Shubham Sharma wrote:

Hey!
I found a way to kill the containers based on their network activity,
Here's the updated container_daemon.py
https://github.com/shubham1337/hackademic/blob/docker/ContainerManager/container_daemon.py
Basically, The daemon will now poll every 10 minutes to check the
network activity of the containers and kill the ones which have no
change in their network activity since last check.
10 minutes is maybe very less for this, we could change that no problem.
What do you think?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#178 (comment)

[shubham1337]

Could you please tell me what do you mean by "kill(with hatchet))" ?
Thanks! :D

[northdpole]

It was a lame attempt at a joke I meant add it but make the idle timeout configurable and read from a configuration file

[shubham1337]

Haha, Cool :)
Sure will add idle timeout as a configuration.