OpenVZ Forum


Home » General » Support » OpenVZ kernel reliability - production ready?
Re: OpenVZ kernel reliability - production ready? [message #50955 is a reply to message #50954] Wed, 11 December 2013 20:44 Go to previous messageGo to previous message
rkelleyrtp is currently offline  rkelleyrtp
Messages: 3
Registered: December 2013
Junior Member
Thanks for your reply. Please see my answers below.

Paparaciz wrote on Wed, 11 December 2013 15:22
I'm not sure what answer you expect, but I didn't saw any big issues to use openvz in rhel5 or rhel6 based os and kernel.

what you heard of kernel crashing needs to be checked (is it hardware, or openvz specific problem), but I didn't saw such thing.


I was hoping some people would chime in with their experience deploying OpenVZ in production environments. Such as, "I am running <xxx> containers on a node node with <yyy> resources and have seen (or not seen) OpenVZ crash" Basically, some real-world feedback for deploying OpenVZ. For what its worth, we are running production-grade hardware with ECC RAM, dual power supplies, dual NICs, etc.

Quote:
It's quite strange that you want stick to some specific versions.

Not strange at all. Typical production environments are tested against very specific versions of code before deployments. I would be surprised if anyone would randomly update their Linux kernels on production environments without adequate testing.


Quote:
Also take a mention that separate nginx/php/mysql services will need resources.

Yep, I have profiled our typical run-time environment (how much RAM, CPU, HDD) and have some good baseline numbers to start with. With those numbers, I know each OpenVZ node can support XXX number of containers. Thus, I have a scaling plan in mind.

Quote:
Finally I don't understand what you want to achieve with such setup.

As I mentioned in the original post, I want to spin up an OpenVZ container per web site we will be hosting. But, before we go down this route, I need to make sure we won't have any kernel-level issues (random reboots, etc) once we are in production.

In the end, I am hoping a bunch of people would chime in with their experience deploying OpenVZ in real production networks where reliability is paramount. I don't know how many people actually use OpenVZ in production - thus all the questions.

Thanks.

[Updated on: Wed, 11 December 2013 20:44]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: FUSE not working in container on Debian7 x64
Next Topic: "Connection refused" when connecting from VE to host's public IP
Goto Forum:
  


Current Time: Wed Aug 27 05:10:22 GMT 2025

Total time taken to generate the page: 0.12606 seconds