Permalink
Browse files

Updated marfs_cctest.cfg, to try to improve pedagogical value.

Some old (untested) remnants of Scality/EMC interaction, plus Multi-Component @ NFS and RDMA.
  • Loading branch information...
jti-lanl committed Oct 15, 2018
1 parent 7c695dd commit 1ab1b0327f05778cb2b96cc21eb99247f08de8d7
Showing with 57 additions and 51 deletions.
  1. +57 −51 common/configuration/src/marfs_cctest.cfg
@@ -1,19 +1,22 @@
<config>

<name>CCstar Testbed</name>

<version>1.6</version>
<name>Example Config</name>
<version>1.10</version>

<mnt_top>/marfs</mnt_top>

<mdfs_top>/gpfs</mdfs_top>


# This is an example MARFSCONFIGRC file. Some features illustrated here
# have not been exercised in a long time.


# ...........................................................................
# Repositories
# ...........................................................................

<repo>
<name>repo1</name>

<host>10.135.0.%d:81</host>
<host_offset>21</host_offset>
<host_count>2</host_count>
@@ -43,9 +46,9 @@



# This does authentication via HTTP_DIGEST
# Scality
<repo>
<name>repo2</name>
<name>scality_repo</name>

<host>10.135.0.%d:81</host>
<host_offset>30</host_offset>
@@ -73,6 +76,7 @@
</repo>


# EMC S3
<repo>
<name>emcS3_00</name>
<host>10.140.0.15:9020</host>
@@ -88,6 +92,7 @@
<latency>10000</latency>
</repo>

# EMC S3 + https
<repo>
<name>emcS3_00_https</name>
<host>10.140.0.15:9021</host>
@@ -104,11 +109,12 @@
</repo>


# MarFS Multi-Component, over NFS
<repo>
<name>mc10+2</name>
<name>mc_nfs_repo</name>

# --- This implies a comprehensive set of NFS mounts to
# corresponding back-end file-systems.
# --- This implies a comprehensive set of NFS mounts
# to corresponding back-end file-systems.
<host>/mnt/nfs/mc/repo10+2/pod%d/block%s/cap%d/scatter%d</host>
<host_offset>0</host_offset>
<host_count>1</host_count>
@@ -146,49 +152,47 @@
</repo>



# experimental ...
# MarFS Multi-Component over RDMA
<repo>
<name>mc_sockets10+2</name>

# In contract with the MC DAL, these paths now represent local
# paths on the individual remote file-systems. The "%%d" elements
# survive the first level of formatting (in the DAL). Then, libne
# fills in the remaining details, in ne_open(), using an sprintf
# function provided by the DAL, which has access to the generic
# options provided in the "<dal>" component, below. For now, the
# naming-scheme for ZFS mount-points leaves no way to select
# capacity-units. Replace "xxxx" with the port-number where the
# RDMA-fileserver will be listening on all the hosts.
<host>10.135.0.%%d:xxxx/zfs/repo/pod%d/block%%d/sockets%d</host> ###
<name>mc_rdma_repo</name>

# In contrast with the NFS repo above (MC DAL), these paths now
# represent local paths on the individual remote file-systems. The
# "%%d" elements survive the first level of formatting (in the DAL).
# Then, libne fills in the remaining details, in ne_open(), using an
# sprintf function provided by the DAL, which has access to the generic
# options provided in the "<dal>" component, below. Replace "xxxx" with
# the port-number where the RDMA-fileserver will be listening on all the
# hosts.
<host>10.135.0.%%d:xxxx/zfs/repo/pod%d/block%%d/cap%d/sockets%d</host> ###
<host_offset>1</host_offset> ### unavailable to libne, so unused
<host_count>6</host_count> ### unavailable to libne, so unused

<update_in_place>no</update_in_place>
<ssl>no</ssl>
<access_method>SEMI_DIRECT</access_method>
# <max_get_size>0</max_get_size>
<chunk_size>1073741824</chunk_size> # 1G

<max_pack_file_count>-1</max_pack_file_count> # 0=disable, -1=unlimited
<min_pack_file_count>10</min_pack_file_count>
<max_pack_file_size>104857600</max_pack_file_size> # 100 MiB max indivi
<max_pack_file_size>104857600</max_pack_file_size> # 100 MiB max individual file
<min_pack_file_size>1</min_pack_file_size>

<security_method>NONE</security_method>

<enc_type>NONE</enc_type>
<comp_type>NONE</comp_type>
<correct_type>NONE</correct_type>
<latency>10000</latency> #? what is the right value for this?
<latency>10000</latency>
# <write_timeout>20</write_timeout>
# <read_timeout>20</read_timeout>

<dal>
<type>MC_SOCKETS</type>
<type>MC_SOCKETS</type> # RDMA impl via rsockets. IP sockets TBD.

# --- this defines the total range of octet-values that can
# be installed in the <host> spec, above.
# --- this defines the total range of octet-values that can be
# installed in the <host> spec, above. Given n=10, and e=2, this
# implies that each server has two different storage systems.
<opt> <key_val> host_offset : 1 </key_val> </opt>
<opt> <key_val> host_count : 6 </key_val> </opt>

@@ -224,17 +228,18 @@



# --- namespaces


# ...........................................................................
# Namespaces
# ...........................................................................

# /marfs/project1 holds data backed on Scality object-store
<namespace>
<name>project</name>
<name>project1</name>
<alias>proxy</alias>
<mnt_path>/project</mnt_path>
<mnt_path>/scality</mnt_path>
<bperms>RM,WM,RD,WD,TD,UD</bperms>
<iperms>RM,WM,RD,WD,TD,UD</iperms>
<iwrite_repo_name>repo2</iwrite_repo_name>
<iwrite_repo_name>scality_repo</iwrite_repo_name>
<range>
<min_size>0</min_size>
<max_size>-1</max_size>
@@ -248,10 +253,11 @@
</namespace>


# /marfs/project2 holds data backed on EMC object-store
<namespace>
<name>s3</name>
<alias>s3</alias>
<mnt_path>/s3</mnt_path>
<name>project2</name>
<alias>proxy</alias>
<mnt_path>/emc</mnt_path>
<bperms>RM,WM,RD,WD,TD,UD</bperms>
<iperms>RM,WM,RD,WD,TD,UD</iperms>
<iwrite_repo_name>emcS3_00</iwrite_repo_name>
@@ -263,56 +269,56 @@
<md_path>/gpfs/fs2/s3/mdfs</md_path>
<trash_md_path>/gpfs/fs2/trash</trash_md_path>
<fsinfo_path>/gpfs/fs2/s3/fsinfo</fsinfo_path>
<quota_space>1073741824</quota_space>
<quota_names>32</quota_names>
<quota_space>107374182400</quota_space> # limited amount of space
<quota_names>32</quota_names> # limited number of files (not enforced)
</namespace>


# --- namespaces using Multi-Component repos

# /marfs/mc for Multi-Component over NFS
<namespace>
<name>mc</name>
<alias>proxy2</alias>
<mnt_path>/mc</mnt_path>
<bperms>RM,WM,RD,WD,TD,UD</bperms>
<iperms>RM,WM,RD,WD,TD,UD</iperms>
<iwrite_repo_name>mc10+2</iwrite_repo_name>
<iwrite_repo_name>mc_nfs_repo</iwrite_repo_name>
<range>
<min_size>0</min_size>
<max_size>-1</max_size>
<repo_name>mc10+2</repo_name>
<repo_name>mc_nfs_repo</repo_name>
</range>
<md_path>/gpfs/marfs/mc/mdfs</md_path>
<trash_md_path>/gpfs/marfs/mc-trash</trash_md_path>
<fsinfo_path>/gpfs/marfs/mc/fsinfo</fsinfo_path>
<quota_space>-1</quota_space> ###
<quota_space>-1</quota_space>
<quota_names>-1</quota_names>
</namespace>


# experimental MC + sockets
# /marfs/rdma for Multi-Component over RDMA
<namespace>
<name>mc_skt</name>
<name>rdma</name>
<alias>proxy2</alias>
<mnt_path>/mc_skt</mnt_path>
<bperms>RM,WM,RD,WD,TD,UD</bperms>
<iperms>RM,WM,RD,WD,TD,UD</iperms>
<iwrite_repo_name>mc_sockets10+2</iwrite_repo_name>
<iwrite_repo_name>mc_rdma_repo</iwrite_repo_name>
<range>
<min_size>0</min_size>
<max_size>-1</max_size>
<repo_name>mc_sockets10+2</repo_name>
<repo_name>mc_rdma_repo</repo_name>
</range>
<md_path>/gpfs/marfs/mc_skt/mdfs</md_path>
<trash_md_path>/gpfs/marfs/mc_skt_trash</trash_md_path>
<fsinfo_path>/gpfs/marfs/mc_skt/fsinfo</fsinfo_path>
<quota_space>-1</quota_space> ###
<quota_space>-1</quota_space>
<quota_names>-1</quota_names>
</namespace>



# --- "root" namespace, represents the top-level dir in the marfs mount
# No MD is actually stored here.
<namespace>
<name>root</name>
<alias>root</alias>

0 comments on commit 1ab1b03

Please sign in to comment.