Atom feed of this document
 

 Installing MooseFS as shared storage for the instances directory

In the previous section we presented a convenient way to deploy a shared storage using NFS. For better transactions performance, you could deploy MooseFS instead.

MooseFS (Moose File System) is a shared file system ; it implements the same rough concepts of shared storage solutions - such as Ceph, Lustre or even GlusterFS.

Main concepts

  • A metadata server (MDS), also called master server, which manages the file repartition, their access and the namespace.

  • A metalogger server (MLS) which backs up the MDS logs, including, objects, chunks, sessions and object metadata

  • A chunk server (CSS) which store the data as chunks and replicate them across the chunkservers

  • A client, which talks with the MDS and interact with the CSS. MooseFS clients manage MooseFS filesystem using FUSE

For more informations, please see the Official project website

Our setup will be made the following way :

  • Two compute nodes running both MooseFS chunkserver and client services.

  • One MooseFS master server, running the metadata service.

  • One MooseFS slave server, running the metalogger service.

For that particular walkthrough, we will use the following network schema :

  • 10.0.10.15 for the MooseFS metadata server admin IP

  • 10.0.10.16 for the MooseFS metadata server main IP

  • 10.0.10.17 for the MooseFS metalogger server admin IP

  • 10.0.10.18 for the MooseFS metalogger server main IP

  • 10.0.10.19 for the MooseFS first chunkserver IP

  • 10.0.10.20 for the MooseFS second chunkserver IP

 

Figure 4.3. MooseFS deployment for OpenStack


Log a bug against this page


loading table of contents...