cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject Re: Management server + MySQL server requirements
Date Tue, 01 Mar 2016 14:54:59 GMT

Thanks for the reply Simon.

It would seem that the 250GB suggested by the installation documents is somewhat of an overkill.
Would it be possible to simply use the smallest sized 10k rpm drives out there?

Also, will there be high IOPs on the secondary storage? I'm using a zfs volume with normal
7.2K rpm SATA drives with L2ARC and ZIL caches but I'm thinking if these are redundant because
of the functions of secondary storage.



On Tue, Mar 1, 2016 at 6:45 AM -0800, "Simon Weller" <> wrote:

To be honest, we haven't utilized the usage service as of yet. We're looking at it for a new
project though.

I'll have to defer to others in terms of real world disk space usage.

From: <>
Sent: Tuesday, March 1, 2016 8:32 AM
Subject: Re: Management server + MySQL server requirements

Hi Simon,

What about with usage enabled? How much hard disk space do the management servers use in total?

On Tue, Mar 1, 2016 at 6:30 AM -0800, "Simon Weller" <> wrote:

One of our lab clusters is a similar size, with no usage enabled.
The cloud database is about 100MB.

This cluster goes back about 5 years, so there's a fair bit of historical data stored.

- Si

From: <>
Sent: Tuesday, March 1, 2016 8:13 AM
Subject: Re: Management server + MySQL server requirements

Hi Simon,

Looking at a 6-8 24core host cluster which will eventually be doubled in size

From: Simon Weller

Sent: Tuesday, March 1, 21:15

Subject: Re: Management server + MySQL server requirements



Can you give us an idea of the size of your deployment? How many hosts?


From: <>

Sent: Tuesday, March 1, 2016 6:09 AM


Subject: Re: Management server + MySQL server requirements

Hi Simon,

Is there any way to estimate the size of the DB? Doesn't seem to be any documents on how much
space to provision based on the expected size.


On Mon, Feb 29, 2016 at 11:48 AM -0800, "Simon Weller" <> wrote:


You could argue the same thing with your MySQL master. If you need to restart the server due
to kernel updates et al, it's still going to require a failover to your backup MySQL server
instance for all management servers.  Any CS management design should be built to deal with
this and all management instances should be able to use a secondary synced database source.

In an ideal world, yes, separating the DB layer is a good idea. But if your ACS deployment
isn't that large, co-locating the database with management should (and does) work fine.

- Si


From: Paul Angus <>

Sent: Monday, February 29, 2016 1:20 PM


Subject: RE: Management server + MySQL server requirements

Hi All,

I'd suggest that outside of a lab environment, the MySQL database(s) should never be in the
same vm as any of the management services. The most critical reason being that if you wish
to restart the management server which the MySQL master happens to be on, it will require
the MySQL services to also be shutdown. If they are separated, then secondary management servers
can continue to service requests and updates while the other mgmt. server is restarted.


Paul Angus

VP Technology   ,       ShapeBlue

d:      +44 203 617 0528 | s: +44 203 603 0540<tel:+44%20203%20617%200528%20|%20s:%20+44%20203%20603%200540>    
|      m:      +44 7711 418784<tel:+44%207711%20418784>

e: | t: @cloudyangus<|%20t:%20@cloudyangus>     
|      w:<>

a:      53 Chandos Place, Covent Garden London WC2N 4HS UK


Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India
LLP is a company incorporated in India and is operated under license from Shape Blue Ltd.
Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under
license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic
of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered

This email and any attachments to it may be confidential and are intended solely for the use
of the individual to whom it is addressed. Any views or opinions expressed are solely those
of the author and do not necessarily represent those of Shape Blue Ltd or related companies.
If you are not the intended recipient of this email, you must neither take any action based
upon its contents, nor copy or show it to anyone. Please contact the sender if you believe
you have received this email in error.

-----Original Message-----

From: Stavros Konstantaras []

Sent: 29 February 2016 11:16


Subject: Re: Management server + MySQL server requirements

Hi Simon,

Your proposal is correct,I currently have the recommended setup: 2 machines with nice amount
of cores and RAM, with management server and mysql installed. Usage server is not currently
used, BUT we do use MySQL replication for some form of HA.

However, the drawback that I see is that the management server on the second head node must
be down otherwise it causes the replication to fail pretty quickly. So in case of failure
of the first head node the admin needs to login to the second head node and initiate the management
server (or maybe you can script it and automate this).

Last requirement needed is a script that automates MySQL backups (crontab can be used for

Kind Regards


> On 28 Feb 2016, at 00:06, Simon Weller <> wrote:


> 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 <>

> Sent: Saturday, February 27, 2016 10:37 AM

> To:

> 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

Find out more about ShapeBlue and our range of CloudStack related services:

IaaS Cloud Design & Build<> |
CSForge - rapid IaaS deployment framework<>

CloudStack Consulting<> | CloudStack Software

CloudStack Infrastructure Support<>
| CloudStack Bootcamp Training Courses<>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message