[ASK] CloudLinux

[mangkukmerah]

Update : tadinya saya undang support mereka untuk ngasi penjelasan ke sini, bingung katanya harus pake google translate... kalo di translate belum tentu akurat

Request mereka untuk bikin thread penjelasan CloudLinux dalam bahasa Enggres aja bradah disini

 

[gresshost]

segera pake deh...tapi saya blm berani implement di existing server, takut error aja ..
Next server launching aja....

setujuh...sambil ikut mantau juga deh

 

[iseletsk]

Hello,

My name is Igor Seletskiy, and I am CEO at CloudLinux. I want to respond to few issues raised here. I am sorry -- I don't speak Indonesian -- so, I would have to write in English:

1) Support for cPanel -- we have plugins that work with cPanel. You don't have to control / do anything via command line
http://www.cloudlinux.com/docs/whmplugin.php
http://www.cloudlinux.com/docs/cpanel-enduser-plugin.php

2) Limits for system users: We limit cron jobs as well. If user have shell access, you can use lve_wrappers and set his shell to lve_bash or something similar (http://www.cloudlinux.com/docs/lve_wrapper.php) -- and that will limit anything he does via shell

3) Majority (~90%) of our customers converted their production servers to CloudLinux. Beyond installation of new kernel/reboot -- we do very little to the system -- and this has been executed on hundreds of servers already. Overall -- it is very easy, and quick process. And if for some weird reason new kernel doesn't boo, or you don't like what you get -- just boot back to CentOS kernel.

If you have any other questions -- I would be happy to answer.

 

[rendy]

Hello,

My name is Igor Seletskiy, and I am CEO at CloudLinux. I want to respond to few issues raised here. I am sorry -- I don't speak Indonesian -- so, I would have to write in English:

1) Support for cPanel -- we have plugins that work with cPanel. You don't have to control / do anything via command line
http://www.cloudlinux.com/docs/whmplugin.php
http://www.cloudlinux.com/docs/cpanel-enduser-plugin.php

2) Limits for system users: We limit cron jobs as well. If user have shell access, you can use lve_wrappers and set his shell to lve_bash or something similar (http://www.cloudlinux.com/docs/lve_wrapper.php) -- and that will limit anything he does via shell

3) Majority (~90%) of our customers converted their production servers to CloudLinux. Beyond installation of new kernel/reboot -- we do very little to the system -- and this has been executed on hundreds of servers already. Overall -- it is very easy, and quick process. And if for some weird reason new kernel doesn't boo, or you don't like what you get -- just boot back to CentOS kernel.

If you have any other questions -- I would be happy to answer.

Igor
can i use CLoud Linux in Virtuozzo?

 

[iseletsk]

Igor
can i use CLoud Linux in Virtuozzo?

No, no Virtuozzo/OpenVZ support, at least until RHEL 6/we both rebase to 2.6.32 kernel. We are working with them on making sure it works in the next version.

We do support any HyperVizor - like Xen, VMware, Hyper-V, KVM, etc...

 

[rendy]

No, no Virtuozzo/OpenVZ support, at least until RHEL 6/we both rebase to 2.6.32 kernel. We are working with them on making sure it works in the next version.

We do support any HyperVizor - like Xen, VMware, Hyper-V, KVM, etc...

Ah i See,
so what happened when user get the limit cpu resource?
is their web will go blank, or there is an error code will displayed there?

 

[mangkukmerah]

Hello,

My name is Igor Seletskiy, and I am CEO at CloudLinux. I want to respond to few issues raised here. I am sorry -- I don't speak Indonesian -- so, I would have to write in English:

1) Support for cPanel -- we have plugins that work with cPanel. You don't have to control / do anything via command line
http://www.cloudlinux.com/docs/whmplugin.php
http://www.cloudlinux.com/docs/cpanel-enduser-plugin.php

2) Limits for system users: We limit cron jobs as well. If user have shell access, you can use lve_wrappers and set his shell to lve_bash or something similar (http://www.cloudlinux.com/docs/lve_wrapper.php) -- and that will limit anything he does via shell

3) Majority (~90%) of our customers converted their production servers to CloudLinux. Beyond installation of new kernel/reboot -- we do very little to the system -- and this has been executed on hundreds of servers already. Overall -- it is very easy, and quick process. And if for some weird reason new kernel doesn't boo, or you don't like what you get -- just boot back to CentOS kernel.

If you have any other questions -- I would be happy to answer.

Hi Mr. Seletskiy,

1. Nice, Gonna use the plugin ASAP
2. As far as I know, CloudLinux is not yet fully supported by cPanel (although cPanel is fully supported by CloudLinux) since cPanel still showing me CentOS as my OS , please advise

 

[iseletsk]

When user reaches CPU limit, his website will become slow (as site's processes will not get CPU time beyond limit you setup -- so they would tend to sleep more).
At this point no errors is given.
We also control the number of concurrent connections to apache, as apache can keep only limited number of them. As site becomes slow more and more connections will accumulate (not always, but often).
Once site reaches max allowed number of concurrent connections -- Apache will start producing 503 error -- server busy. As soon as the number of concurrent connections drops bellow limit, site will be ready to accept new connections and will start working again.

 

[iseletsk]

cPanel/CloudLinux: You are correct. cPanel installer and some of the scripts check /etc/redhat-release file.
The content of that file is one line saying which distro it is.
We change it to CentOS so that cPanel would recognize it/continue working as before. From cPanel perspective -- there is no difference if it runs on cPanel or on CloudLinux at this moment.

 

[mangkukmerah]

cPanel/CloudLinux: You are correct. cPanel installer and some of the scripts check /etc/redhat-release file.
The content of that file is one line saying which distro it is.
We change it to CentOS so that cPanel would recognize it/continue working as before. From cPanel perspective -- there is no difference if it runs on cPanel or on CloudLinux at this moment.

Okay, got it and totally understood now the reason behind it . Thanks for answering my long unanswered question. Using your product for 4 months now and feeling like it's going to a smooth and good route in the terms of development and support