Difference between revisions of "MogileFS setup"

From Dreamwidth Notes
Jump to: navigation, search
(Configuring MogileFS for a Dreamwidth development installation)
Line 7: Line 7:
 
=== Basic Steps ===
 
=== Basic Steps ===
  
* Install prerequisites
 
 
* Build and install MogileFS Debian packages
 
* Build and install MogileFS Debian packages
 
* Create MogileFS Database
 
* Create MogileFS Database
Line 15: Line 14:
 
=== Install Prerequisites ===
 
=== Install Prerequisites ===
  
OBSOLETE INSTRUCTIONS. These need to be looked at. If you really need MogileFS for something, please talk to us and we'll see about getting this setup.
+
Follow the [https://code.google.com/p/mogilefs/wiki/InstallOnUbuntu installation instructions on the MogileFS wiki].
  
 
=== Create MogileFS database ===
 
=== Create MogileFS database ===

Revision as of 16:15, 5 April 2013

Note: This page is still a draft. Much of this information was pulled from the MogileFS Wiki combined with the INSTALL.txt instructions from the mogilefs source.

Configuring MogileFS for a Dreamwidth development installation

These are instructions for getting a simple MogileFS installation working on a single instance (likely development/testing) Dreamwidth installation. This is not a full setup document for a production, multi-server environment.

Basic Steps

  • Build and install MogileFS Debian packages
  • Create MogileFS Database
  • Configure MogileFS servers
  • Set up Dreamwidth installation to work with MogileFS

Install Prerequisites

Follow the installation instructions on the MogileFS wiki.

Create MogileFS database

You should already have MySQL installed for your Dreamwidth installation. So log in as root there and create the mogilefs user:

$ mysql -u root -p
mysql> create database mogilefs;
mysql> grant all on mogilefs.* to 'mogile'@'%' identified by 'mogilepw';
mysql> flush privileges;
mysql> quit

Then go ahead and create the schema using mogdbsetup

$ /usr/bin/mogdbsetup --yes --dbname=mogilefs --dbuser=mogile --dbpassword=mogilepw

Configure MogileFS servers

You will need to set up at least one tracker (mogilefsd) and one storage server (mogstored), but ideally several of each on different machines for redundancy. Keep in mind this is a simple development setup.

The tracker can be configured with /etc/mogilefs/mogilefsd.conf as follows:

$ cat > /etc/mogilefs/mogilefsd.conf <<EOF
daemonize = 1
db_dsn = DBI:mysql:mogilefs
db_user = mogile
db_pass = mogilepw
listen = 127.0.0.1:7001
conf_port = 7001
default_mindevcount = 1
EOF

Then start the tracker:

$ /usr/bin/mogilefsd

The storage server can be configured with /etc/mogilefs/mogstored.conf as follows:

$ cat > /etc/mogilefs/mogstored.conf <<EOF
daemonize = 1
httplisten = 127.0.0.1:7500
mgmtlisten = 127.0.0.1:7501
docroot = /var/mogdata
EOF
$ mkdir /var/mogdata

Then start the storage server:

$ /usr/bin/mogstored

Next you need to pass some configuration info to the tracker with mogadm, but mogadm needs a config file too:

$ cat > /etc/mogilefs/mogilefs.conf <<EOF
trackers = 127.0.0.1:7001
EOF
$ /usr/bin/mogadm host add localhost --ip=127.0.0.1 --port=7500 --status=alive
$ /usr/bin/mogadm device add localhost 1
$ mkdir /var/mogdata/dev1

Create a MogileFS domain and storage classes to be used by Dreamwidth:

$ /usr/bin/mogadm domain add dreamwidth
$ /usr/bin/mogadm class add dreamwidth temp --mindevcount=1
$ /usr/bin/mogadm class add dreamwidth captcha --mindevcount=1
$ /usr/bin/mogadm class add dreamwidth userpics --mindevcount=1

Now you have a working MogileFS installation that you can test with mogtool:

$ cat > /etc/mogilefs/mogtool.conf <<EOF
trackers = 127.0.0.1:7001
domain = dreamwidth
class = temp
EOF
$ /usr/bin/mogtool inject /etc/hosts hosts
$ /usr/bin/mogtool extract hosts -
$ /usr/bin/mogtool delete hosts

Set up Dreamwidth installation to work with MogileFS

Add to $LJHOME/etc/config-local.pl:

   %MOGILEFS_CONFIG = (
       hosts => [ '127.0.0.1:7001', ],
       domain => 'dreamwidth',
   );
   $USERPIC_MOGILEFS = 1;
   $CAPTCHA_MOGILEFS = 1;

Restart Apache, and try uploading an icon via editpics.bml