Josh, Unless you plan to create a massive cloud, there is probably no reason to separate MySQL from the management server. It would actually be better to deploy two management servers and then replicate MySQL over to the second server for some form of HA.
You don't really need SSDs. A couple of 10/15K SAS/SATA drives will be fine. Most of the space allocate is for the MySQL databases. If you plan to use the usage service, the stats collection will require more drive space. This is configured as a separate MySQL database. I'd suggest you deploy a minimum of 16GB of RAM and 8 cores or so. If you plan to grow the deployment rapidly, leave some empty memory slots for the future. - Si ________________________________________ From: Josh Davis <[email protected]> Sent: Saturday, February 27, 2016 10:37 AM To: [email protected] Subject: Management server + MySQL server requirements Hi all, apologies for the spam. This is the hardware suggestion for MySQL on the management server node. I'm looking at a separate server for MySQL DB. Is the bulk of the 250GB requirement used by the management server or the MySQL DB? Do I need to use SSDs or is SAS or even SATA fine for the management server? Can I place the MySQL DB on a VM as well?Is the MySQL server supposed to be public facing?Is it sufficient to only connect to the management network? No need to access the storage or guest network? "The machines that will run the Management Server and MySQL database must meet the following requirements. The same machines can also be used to provide primary and secondary storage, such as via localdisk or NFS. The Management Server may be placed on a virtual machine.Operating system:Preferred: CentOS/RHEL 6.3+ or Ubuntu 12.04(.1)64-bit x86 CPU (more cores results in better performance)4 GB of memory250 GB of local disk (more results in better capability; 500 GB recommended)At least 1 NICStatically allocated IP addressFully qualified domain name as returned by the hostname command" Thanks!Josh
