Project Mercury Alpha 6: Now With Solr!

Events happening in the community are now at Drupal community events on www.drupal.org.
joshk's picture

I'm happy to announce the 0.6 Alpha release of the Mercury AMI, now including ApacheSolr as the search backend! This is the last piece of major infrastructure we want to integrate into the stack for scalability purposes. You can now move from a single-server install based on Mercury to a best-practice vertically scaled architecture with separate hardware to run front-end cache, application, back-end cache, search and database!

The quickest way to find it is by searching Amazon EC for "Pantheon" or "Mercury". The manifest path for the latest release (in 32bit and 64 bit flavors) is:

  • chapter3-storage/PANTHEON-pressflow-mercury-alpha-6.manifest.xml
  • chapter3-storage/PANTHEON-pressflow-mercury64-alpha-6.2.manifest.xml (back!)

If you'd like to "roll your own" we've updated the wiki instructions page with a new set of instructions for getting Solr up and running as part of the process. Feel free to improve that documentation, as it's definitely a community process.

This will likely be one of the last releases before we move the project into the Beta phase, at which point we'll be focusing on fine tuning and stability as well as portabilty onto non EC2 systems moreso than new features. If you have ideas for additional things you'd like to see integrated in the stack, please chime in. We're also going to be documenting real-world "how to" use-cases — e.g. "how do I put my existing site on Mercury" in user-friendly detail — so stay tuned for that.

As always, let us know what you think of the release, what you'd like to see in future iterations, and how your experience is in using the stack. There's plenty more to come.

Comments

64 bit missing changes

fred0's picture

Correct me if I'm wrong since I've just started messing with Mercury, but I believe the 64bit version is missing the path changes to /mnt in both the /etc/mysql/my.cnf and /etc/defaults/varnish files.

Doh!

joshk's picture

That's why we call it "alpha". We'll get this fixed asap.

Fixed!

joshk's picture

The new manifest path is: chapter3-storage/PANTHEON-pressflow-mercury64-alpha-6.1.manifest.xml

getting HTTP403 when trying to install that AMI??

bcmiller0's picture

I get this on EC2 when trying to launch an instance with that AMI:

HTTP 403 (Forbidden) response for URL http://s3.amazonaws.com:80/chapter3-storage/PANTHEON-pressflow-mercury64... check your S3 ACLs are correct.

Here is screen shot.

didn't get screen shot on launch issue

bcmiller0's picture

Here it is. Fairly new to EC2, so hopefully i'm not missing something.

http://groups.drupal.org/files/ami_0.jpg

Working on it.

joshk's picture

Looks like we misplaced some AMI files. We'll get the 64 bit version of the server back online asap.

Back online

joshk's picture

new manifest:

chapter3-storage/PANTHEON-pressflow-mercury64-alpha-6.2.manifest.xml

mercury working well

bcmiller0's picture

I've got a beta of our site running on mercury with three instances in EC2. A varnish server, a web server, and a msyql server. We plan to probably launch our site public facing in January. So i'll be adding mysql proxy to front-end our mysql servers, and look at getting sessions working with memcache in addition to the mercury cache router.

Also was little disappointed that varnish doesn't support HTTPS, so i'll be looking at some solution there to front-end HTTPS for varnish i suppose. Overall mercury seems to be running well for us. With just some testing and hitting it with siege.

Look forward to seeing you at drupal camp austin to hear more thoughts.

thanks for your work,

Https

joshk's picture

If you want to roll with HTTPS but still have cached anonymous traffic, you should probably front varnish with pound, or another tool. This addition to the stack is a bit out of scope for project Mercury — it's a bit of an edgy use-case; most of the time you're transferring secure data you don't want to be caching the page — but maybe for the future!