Deployment to Serve...
 
Notifications
Clear all

Deployment to Serverrs.

3 Posts
2 Users
0 Likes
1,434 Views
Posts: 6
Topic starter
(@jasper)
Active Member
Joined: 6 years ago

Good day to all. I'd like to open with a "Congrats" on an excellent Panel. We have been using Linux with ISPpanel for some time and have now opted to open up a Windows Offering. Many of our clients and several new ones desire an IIS/Windows offering.

(A) Here is our "Current" equipment available:

2 x Poweredge R710 servers: 1 x 8way Xeon Proc,  64GB ram, 2x200GB disk (Mirror: OS), 4x1TB (Raid 10: data).

1 x Poweredge R510 server: 2 x 8way Xeon Procs,  64GB ram, 2x200GB disk (Mirror:OS), 2x500GB disk (mirror, possibly for Log/TX files), 4x600GB SAS (Raid 10).

1 x Poweredge R210 CoreDuo Proc, 2x500GB disk (mirrored), 8GB Ram.

We can bump the ram/disk on all servers (R210 is maxed...). All servers are running Windows 2008R2 x64, 4x1GB Nic ports (R210 has 2 Nic Ports). We may/may not acquire Windows 2012/2016 - that will be decided once we are confident in our client base needs. At this time, they all pretty much need what we have in terms of Windows Server.

(B) Here is what we will be offering at the outset:

Email Hosting with Webmail (hMail/Mail Enable - not sure which yet), mySql, MS SQL (2008R2), MS SQL-express, ASP, ASP.Net, PHP (5.x, no v7 yet), AWstats, FileZilla FTP, Web Hosting (CMS: C5, Modx etc) and various others. We will be using Let's Encrypt for certain pieces (Filezilla already has SSL support).

We have been playing with SoldCP for about 2 months and have all the kinks worked out (a few with AWstats, but that will come). We are pretty confident in installing, configuring, securing and otherwise rolling out SolidCP in a limited production scenario and have several clients that will be "ginnie pigs".

What we don't know is the best (or at least a "Good") deployment strategy to the servers at our disposal. We believe we have the "horse power" to install everything onto every box (except the R210), but I don't that is not the object of the exercise.

Any thoughts or suggestions would be appreciated.

Thanks for taking the time to read this.

Jasper...

2 Replies
Posts: 1964
Admin
(@m-tiggelaar)
Noble Member
Joined: 8 years ago

Hello,

I would recommend 2012R2 or 2016 mainly due to SNI functionality (without it people need a dedicated IP per certificate which in this day and age really isn't proffered).

The rest all looks fine 🙂

Differences between hmail and mailenable is more or less integrated Web mail (mailenable) and optional paid features, vs hmail which is pop/imap mainly.

php 5 + 7 etc can be installed (multiple versions) by using php manager (can be installed via web applications).

For your type of deployment i would run :

Filezilla, webhosting, awstats , portal on one box

second box mail,

third box database (mysql / mssql) and enterprise. (you technically can dedicate the lowest box to enterprise + portal but it is more or less how you prefer to have things arranged.

You have more then plenty of power to run everything though no problem 🙂

Regards,

Marco

Reply
Posts: 6
Topic starter
(@jasper)
Active Member
Joined: 6 years ago

Marco, thanks for taking the time to review this.

I was sure we had the horsepower and appreciate your insight. We have all the scripts to install the required MS pieces (urlrewrite,arr,php mgr,php 5.x etc) - they have been tested and fine tuned so we are comfortable with the install of the requirements.

Here is what I was thinking of for deployment:

R210, Portal & Enterprise. This one am not sure of as I think Enterprise probably needs some horsepower. This guys has 8GB ram, Core Duo and mirrored Sata Drives,

R510 - DB stuff (mySQL/SQL),

R710(s): Mail on 1, Filezilla, webhosting, awstats the other.

It's likely we will be moving to 2012/2016 servers (as you pointed out: SNI functionality). We are leaving that on our existing Linux boxes as we have the SNI module on them for a bit until we are sure of our deployment and functionality.

Thanks again for the time - much appreciated.

Reply
Share: