Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
We are a multi tenant hosting provider and use Apache on RHEL 5 servers. As the environment is shared, as of now, we didn't provide users access to directly change their site vhosts. But now we wish to make the process flexible and were thinking of having multiple Apache instances for each of the sites on the server. This will ensure that each site user will have access to change vhosts, restart apache etc for his her respective instance.
Can you please suggest if having multiple Apache instances on a single RHEL 5 server was possible?
It is possible to run multiple apache instances with different ports. But it may not what you want for multi-tenant setup. You may start think of container based virtualization.
May you please elaborate on "container based virtualization"?
We basically want the users to have access to their site's respective vhosts and are able to safely restart Apache to reflect new config changes i.e. without affecting other sites on the server.
Currently(in our old system) we have a virtual RHEL server with single Apache instance and multiple virtualhosts with varying IP-Port combinations.
I am recommending to create separate vm for your different customer.
if your user based is not much, it should be fine. But definitely you need more system resource for each customer.
you can look at openvz for container.
www.openvz.org
Good Luck
Thanks again for your reply. This kernel virtualization offered by OpenVZ is new to me. I will explore this further.
Is it the most effective way how multi tenant hosting providers allocate independent shells to users?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.