Trying to make up my mind about Interworx. I’ve been in contact with Paul, about how Interworx functions.
However, there’s 2 things I’m unsure of :
- How does the clustering work exactly (I know about how H-Sphere does clustering, but the way Paul describes it, all nodes act like 1?) I read a small thread about the work nodes do vs. CM + hard drives. The reply from Iworx was that the node hard drives only need to be big enough for the OS + rrd and logs. The website files are stored on the CM (which also has the MySQL server… which brings up other points). So, my CM server needs to be in a huge Raid 5 array with 50 disks? Or what exactly? Also, what happens when the MySQL performance for the entire cluster is degraded to the point I need to start up a second MySQL server for new domains added to the cluster?
I’m just trying to wrap my head around this one, since most of my servers are 4x250gb Sata2 in Raid10 and quad cores/ram… typical servers basically. So if the CM (1 of those typical servers) becomes full… I need to create a second/third/4th cluster? That seems… rough, if that’s the case. Basically, I’d need to manage multiple CM’s? If this is the case, I would actually need a SAN switch and multiple SAN’s to ensure I actually have enough storage? Isn’t this dangerous if the CM actually goes down? Raid can only go so far…
If the system does NOT work this way, if httpd is down for the count on one node, does it move onto the next node?
- Reseller-owned websites. Are they all added onto the same server? Or are they randomly added onto different servers (thus making sure that if there is downtime, not all reseller sites are affected)
Other questions :
Is it okay to assume that this solution is like cPanel, but adds on a “virtual” layer, which places sites on single-servers (that do everything : http, dns, email), and have one main node act as the MySQL server?
Will the API be fully developed shortly? Can it list accounts (and reseller-owned accounts)?
Are there limits in place for reseller backups/restores, to avoid disk i/o problems?
Is there some way to prevent resellers from placing sites on some servers (for example, different continents), or to have them manually choose which server?
Also, can you move 1 account from one node, to another, with no downtime? Usually, this would be for manual load balancing and such. Is this process automated? Can it be done with reseller-owned accounts as well?
And for the API… does it create the account with the CM, which then decides which server it goes on? Or does it need to communicate with each node?
Also, I plan to use a semi-custom backup solution. If I can handle the SSH/login parts, how hard would it be for me to add a page or section into Interworx, that allows the user to browse & restore their own backups (their home directory, emails, mysql) ?
I briefly emailed with Paul… but, Windows 2008 support? It’s not mission critical or anything, but if Interworx works like how I think it works, Windows 2008 support would be really nice to have so us providers can offer a full solution, rather than just half.
And this one goes back to #1… if the system really needs a sort of SAN/San Switch… could Interworx also put in OpenVZ support? I’ve seen OpenVZ management scripts built in days, and there’s multiple open sourced ones out there that in theory, should be easy to integrate. The only problem is getting it to use iSCSI (easy, but this part I’m not familiar with)
I apologize for the many questions, but I’m trying to wrap my head around Interworx, since there’s no working clustered demo to play with.