Is there way to start several OpenVZ containers that keep running and are later used by tool sessions?
Is there way to start several OpenVZ containers that keep running and are later used by tool sessions? This is to prevent the container startup time when several users try to run tools at the same time.
We have few demos planned for our website MaterialsHUB.org and we are expecting group sizes of ~50 people. During these demos several users will start launching tools on the hub and we want to improve their experience by saving the time to start OpenVZ containers.
Please let me know if there is a way to keep some OpenVZ containers running all the time which can be used to run the tool sessions.
0 Like 0 Dislike
Nicholas J. Kisseberth @ on
I can’t find the ability in the open source release, so we must have added that in the “new” middleware (few years old now, so I guess its not so new). Even if it did exist in the open source release it would have been an early version that would have created multiple standby containers for each tool which can become resource intense if you don’t have extra execution hosts. I’ve since added the ability to have generic standby containers that could be resized for any tool.
If tool startup is slow, one common mistake I have seen are excess files in the container template. Files left in /tmp in the template image slow down session startup, package cache in template image can also slow down session start up (run ‘apt-get cache clean’ inside the container template to clean it out).
Hopefully this fall’s release of HUBzero will include the new middleware which has support for standby containers.
Reply Report abuse
Please login to answer the question.