Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Using MMM on AWS (Amazon Cloud) with Virtual IP
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Arjen Lentz  
View profile  
 More options Sep 19 2012, 8:47 pm
From: Arjen Lentz <ar...@openquery.com>
Date: Thu, 20 Sep 2012 10:47:31 +1000 (EST)
Local: Wed, Sep 19 2012 8:47 pm
Subject: Re: [mmm-devel] Using MMM on AWS (Amazon Cloud) with Virtual IP
Hi Mike

> How would this work for your mysql clients?

You'd need to have an extra hook in MMM control to also have an agent on each client machine that does the same as the regular agent in terms of adjusting /etc/hosts, but not worry about a local mysql server. Essentially extend the agent with a role that does less than the normal one.

However, as I mentioned, with Amazon Elastic IP the overall solution becomes very expensive, and in many cases the cost of running a DB-heavy infrastructure on Amazon is costly. The reason is that you pay for RAM and CPU time, and with MySQL a large chunk of RAM is globally allocated (InnoDB buffer pool, etc) and if you have a fairly busy site both the rest of the RAM (dealing with connections) as well as CPU time (queries) are highly utilised.
Amazon works out economically if you have medium or relatively low RAM/CPU use, otherwise it becomes horrendously costly.

You need to have some idea about the load profile of your app, understand how MySQL works (like above, but there's more to it), and then make projections of Amazon pricing versus another service such as Linode or another "cloud".
You may find that the Amazon option turns out vastly more expensive once you take your actual use into account.
Add to that the effort of adapting MMM for this purpose, and it just doesn't make sense any more.

Regards,
Arjen.

> On Sep 19, 2012 1:43 AM, "Arjen Lentz" < ar...@openquery.com > wrote:

> We worked out a few years ago how to implement this, just didn't need
> to use it in the end.

> You can use hostname based as Marcus suggested, but it would require
> code changes/additions to MMM.
> You can use /etc/hosts, and configure the local resolver library (OS
> wide setting) to check for mtime change on that file to reload. Then
> the MMM agent can modify the hosts file when there's a master switch,
> and you get failover in the same instant way the IP address shift
> works.

> ----- Original Message -----
> > From: "Mike!" < nibl...@gmail.com >
> > To: mmm-devel@googlegroups.com
> > Sent: Monday, 17 September, 2012 4:30:32 PM
> > Subject: Re: [mmm-devel] Using MMM on AWS (Amazon Cloud) with
> > Virtual IP
> > That doesn't work. Mmm uses ip addresses which are linked to roles.
> > If
> > a role moves from one node to another, mmm agent removes the ip from
> > one host and assignes it to another. Usually the nodes tend to be on
> > the same network.

> > I think your problem is particulalry difficult to solve. The only
> > solution I can think of is putting all your db and mmm nodes, as
> > well
> > as db clients in a vpn. That way you have full control of the ip
> > addresses they usee, and you can just use any private range you
> > like.

> > Mike
> > On Sep 17, 2012 8:14 AM, "Marcus Bointon" < marcus.boin...@gmail.com

> > wrote:

> > On 17 Sep 2012, at 05:56, Arjen Lentz < ar...@openquery.com > wrote:

> > > In Amazon you'd need to use the "Elastic IP" to get a virtual IP
> > > address for MMM purposes.
> > > The downside is that traffic no the Elastic IP address is charged
> > > as
> > > external rates, so that means that all the internal traffic
> > > between
> > > your webservers and your database servers would get charged as
> > > external. Makes it rather costly.

> > If you can use names instead of IPs, you can use EC2's generated
> > hostnames. The trick with these is that on the outside these resolve
> > to public IPs, but on the inside they resolve to EC2 internal IPs,
> > so
> > they will stay working if instances get new IPs. This fixes a lot of
> > things that would otherwise require fixed (i.e. elastic) IPs.

> > Marcus

> > --
> > You received this message because you are subscribed to the Google
> > Groups "MySQL Multi Master Manager Development" group.
> > To post to this group, send email to mmm-devel@googlegroups.com .
> > To unsubscribe from this group, send email to
> > mmm-devel+unsubscribe@googlegroups.com .
> > For more options, visit this group at
> > http://groups.google.com/group/mmm-devel?hl=en .

> > --
> > You received this message because you are subscribed to the Google
> > Groups "MySQL Multi Master Manager Development" group.
> > To post to this group, send email to mmm-devel@googlegroups.com .
> > To unsubscribe from this group, send email to
> > mmm-devel+unsubscribe@googlegroups.com .
> > For more options, visit this group at
> > http://groups.google.com/group/mmm-devel?hl=en .

> --
> Arjen Lentz, Exec.Director @ Open Query ( http://openquery.com )
> Australian peace of mind for your MySQL infrastructure.

> Follow us at http://openquery.com/blog/ & http://twitter.com/openquery

> --
> You received this message because you are subscribed to the Google
> Groups "MySQL Multi Master Manager Development" group.
> To post to this group, send email to mmm-devel@googlegroups.com .
> To unsubscribe from this group, send email to
> mmm-devel+unsubscribe@googlegroups.com .
> For more options, visit this group at
> http://groups.google.com/group/mmm-devel?hl=en .

> --
> You received this message because you are subscribed to the Google
> Groups "MySQL Multi Master Manager Development" group.
> To post to this group, send email to mmm-devel@googlegroups.com.
> To unsubscribe from this group, send email to
> mmm-devel+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/mmm-devel?hl=en.

--
Arjen Lentz, Exec.Director @ Open Query (http://openquery.com)
Australian peace of mind for your MySQL infrastructure.

Follow us at http://openquery.com/blog/ & http://twitter.com/openquery


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.