|
|
| Re: Clustering services possibilities [message #62152 is a reply to message #61668] |
Tue, 14 April 2009 09:00   |
Lxhelp
Messages: 23691
Registered: July 2006 |
The Champion |
|
|
If you are using plesk, you need to contact them.
On Wed, Apr 08, 2009 at 07:00:28PM -0000, Edwin Bekaert wrote:
>
>
> I have a VPS (virtuozzo + plesk) where all services are running on for limited number of customers.
>
> Today I want cluster the different services in order to:
> * increase stability
> * tighten security
> * optimize performance
>
> This is my idea:
> * VPS_cp : CP + DNS1 + Mail fallback
> * VPS_mail : Mail + AVAS + DNS2
|
|
|
|
| Re: Clustering services possibilities [message #62163 is a reply to message #62159] |
Tue, 14 April 2009 10:43 |
Lxhelp
Messages: 23691
Registered: July 2006 |
The Champion |
|
|
You have to have lxadmin first, and then we can help you set it up. But if you have plesk, we have absolutely no clue.
On Tue, Apr 14, 2009 at 01:29:33PM -0000, Edwin Bekaert wrote:
>
>
> I mean today I have plesk but I want to cluster services, hence my question in lxadmin forum... As I might choose lxadmin to do the job...
>
|
|
|
|
| Re: Clustering services possibilities [message #62200 is a reply to message #61668] |
Tue, 14 April 2009 23:57 |
 blinkie 
Messages: 56
Registered: January 2009 |
Valuable Member |
|
|
| ednique wrote on Wed, 08 April 2009 12:00 |
1) where do I put webmail? on VPS_web because it needs apache? is that possible?
|
No. Webmail must be installed on the mail server. I believe LXAdmin's webmail clients read the raw mail spool instead of connecting as clients via IMAP. Someone correct me if I'm wrong (I've only started installing this platform).
| Quote: |
2) Can the CP run on standard https port as no other webpage is served by VPS_cp?
|
Yes, it can run on 80 and 443. But make sure your billing solution will be happy with this. For instance, WHMCS hard codes the LXAdmin default ports of 7778 and 7777.
| Quote: |
3) Do I need AVAS on mail fallback? or will VPS_mail do AVAS when it comes back on and receives the messages from VPS_cp?
|
LXAdmin only supports a single mail server in any template. It doesn't support multiple MX (relay or "backup") servers. There is no clear indication as to when the platform will support this as the developers don't believe it's a priority (snicker).
| Quote: |
4) Do you think these seperations are good or can you suggest something better?
|
Personally, I don't think a virtualized platform makes a great hosting platform to start with. Not when you're using resource constrained servers as virtualization platforms to start.
| Quote: |
5) If mail is on VPS_mail do I need to change the php scripts of VPS_web if they need to send mail?
|
No, because webmail doesn't live on the "web" server, it lives on the "mail" server.
| Quote: |
6) What memory should I need on each of these VPS's? 25-50 clients using more mail then web. 5% has a userbase on their forum of about 150 people.
|
"Using more mail than web..." What does that mean? Web is a breeze compared to 50 or so clients hitting your mail server via IMAP, with open connections, and folder sorting, etc.
Hope that answers some of your questions. I've found that LXAdmin doesn't really support distribution to any robust extent at this time. Some of its shortcomings are mentioned above (e.g. lack of support for backup mail servers). Another one you might need to be aware of (depends on the size of your deployment) is lack of support for shared mass storage infrastructure--the way home directories are setup it makes it difficult to mount those directories from a SAN...which is how every medium sized hosting provider has done it since say...1995. Another thing is that it assigns real UNIX userids to accounts; that's another idea that has been outdated since the mid to late 1990's when massive hosting systems had to be created (by massive, I mean those that expand beyond the kernel limits for maximum userid number).
So, while this platform certainly looks pretty, I've found it has a mounting list of flaws that make it unsuitable for large scale deployments...despite being (ahem) "distributed."
|
|
|
|
| Re: Clustering services possibilities [message #62210 is a reply to message #62164] |
Wed, 15 April 2009 04:51 |
Lxhelp
Messages: 23691
Registered: July 2006 |
The Champion |
|
|
I am sorry for the misunderstanding. We have many people who actually ask plesk related questions here, and I initially thought yours were similar.
I would like to apologize for my statements.
thanks.
On Tue, Apr 14, 2009 at 03:18:44PM -0000, Edwin Bekaert wrote:
>
>
> So I post a message to know:
> * what I was thinking about doing with lxadmin is possible and the right way of working
> * what the experts here think about this setup or maybe could suggest something better
> * what type of VPS I need to buy
> * To have an answer on my questions before ordering
>
> To only find out I have to order first before you can tell me what is possible...
>
> To only find out that you don't realise I want to quit plesk and head over to lxAdmin if lxAdmin can do what I think it can do...
>
> To realize I should not have said the forbidden word "Plesk" that have put you in a very defensive non-supportive mode...
>
|
|
|
|
| Re: Clustering services possibilities [message #62280 is a reply to message #62209] |
Wed, 15 April 2009 12:53 |
blinkie
Messages: 56
Registered: January 2009 |
Valuable Member |
|
|
| ednique wrote on Wed, 15 April 2009 01:30 |
I guess I will need to digg into this much deeper as I wanna be sure this is going to work...
|
Unfortunately, there's no real way to be sure until you setup a testbed.
| Quote: |
Getting 3 physical servers for doing that with so little clients is too much overhead... and too much $$$...
|
SO then why bother with a VPS setup in the first place? How much memory, disk, and CPU will actually be available to each VPS? If you stuff everything on a single box or split it over two...each application server (mail, web, etc.) will have access to all of the disk, memory, cpu on that system thanks to scheduling. Try to keep that in mind.
| Quote: |
Yes I would be using WHMCS, but maybe the hardcoded ports can be changed? or are these files encrypted?
|
They can be changed by opening a ticket with WHMCS support, and Matt will hardcode them to whatever you want, then send you back a custom module. Sadly, the module is encrypted. But if you dig around this forum you will find the source of an original version (1.4) of the module, which you can modify yourself.
| Quote: |
For the backup mail server I would just install that myself, that's not that difficult,
|
What is your plan for that? Are you going to write custom scripts that will copy config information over to your backup mail server? There's no automated support for this in LXAdmin right now and there's no indication support is imminent. A properly configured mail relay (backup mail server) in 2009 will only accept mail for addresses it knows about. A similar server from 1998 (as an example) would have been configured to accept all mail for all domains it knows about and then forward them onto the highest priority MX--this is problematic because your secondary MX servers could easily get kill (bandwidth, cpu, disk) by something like SPAM (it all depends on the number of clients of hosted accounts of course).
In other words, what I'm trying to point out is that LXAdmin Enterprise as it is designed today doesn't offer very many benefits over non-Enterprise simply because it implements systems in ways that are not ideal for a distributed platform. In fact, one of the whole points of distribution is load balancing. This is currently impossible with LXAdmin Enterprise because it creates those home directories... (well, it's not totally impossible, but it's not a supported configuration--also, the mail system likely doesn't support solid file locking so load balancing could be problematic).
Anyhoo, just want to make sure you are aware of the limitations now because the only way I have discovered them is by going through the process of setting this up (still not live though as I figure out the best approach for getting past the above limitations). The discouraging thing is that there is no real documentation, the only help is this forum, and LXHelp isn't always available....these are all potentially bad things for a platform that will be a core part of any business. But you get what you pay for right?
|
|
|
| Re: Clustering services possibilities [message #62353 is a reply to message #62200] |
Thu, 16 April 2009 23:32 |
|
| blinkie wrote on Tue, 14 April 2009 23:57 | | ednique wrote on Wed, 08 April 2009 12:00 |
1) where do I put webmail? on VPS_web because it needs apache? is that possible?
|
No. Webmail must be installed on the mail server. I believe LXAdmin's webmail clients read the raw mail spool instead of connecting as clients via IMAP. Someone correct me if I'm wrong (I've only started installing this platform).
|
Actually, webmail does connect through IMAP.
| Quote: |
| Quote: |
2) Can the CP run on standard https port as no other webpage is served by VPS_cp?
|
Yes, it can run on 80 and 443. But make sure your billing solution will be happy with this. For instance, WHMCS hard codes the LXAdmin default ports of 7778 and 7777.
|
WHMCS should theoretically work, since I believe the API works on port 7779. I am not sure though, maybe that port is acually for internal things, but I thought it was for the API.
| Quote: |
| Quote: |
5) If mail is on VPS_mail do I need to change the php scripts of VPS_web if they need to send mail?
|
No, because webmail doesn't live on the "web" server, it lives on the "mail" server.
|
If it sends mail with authentication (as in, if the script logs in to send the mail), then you will need to change the mail server address to that of the mail server. If the script uses mail() or directly connects to sendmail, then you don't need to change anything.
My Site
|
|
|
HyperVM & Kloxo Support
Members
Search
Help
Register
Login
Home
