From hervelubaki2001 at yahoo.fr Fri Aug 3 15:56:24 2007 From: hervelubaki2001 at yahoo.fr (herve lubaki) Date: Fri Aug 3 16:39:52 2007 Subject: freebsd-cluster Message-ID: <103693.94307.qm@web86107.mail.ird.yahoo.com> He! I' m herve,I study in university of Kinshasa ( D.R. of Congo); option informatic. I' want to know how to make a basic freedsd-cluster of servers and if someone can give my softwares and doc for cluster for that. thrank!! e-mail : hervelubaki2001@yahoo.fr --------------------------------- Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail From raysonlogin at gmail.com Mon Aug 6 04:15:26 2007 From: raysonlogin at gmail.com (Rayson Ho) Date: Mon Aug 6 04:15:28 2007 Subject: freebsd-cluster In-Reply-To: <103693.94307.qm@web86107.mail.ird.yahoo.com> References: <103693.94307.qm@web86107.mail.ird.yahoo.com> Message-ID: <73a01bf20708052050j1e1a3a6dp22bdbcb0275eed1d@mail.gmail.com> What kind of cluster?? The requirements for an HPC cluster and that of a HA cluster are different... Rayson On 8/3/07, herve lubaki wrote: > He! > I' m herve,I study in university of Kinshasa ( D.R. of Congo); option informatic. > I' want to know how to make a basic freedsd-cluster of servers and if someone can give my softwares and doc for cluster for that. > thrank!! > e-mail : hervelubaki2001@yahoo.fr > > > --------------------------------- > Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail > _______________________________________________ > freebsd-cluster@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-cluster > To unsubscribe, send any mail to "freebsd-cluster-unsubscribe@freebsd.org" > From jarrod at ipglobal.net Mon Aug 6 05:21:15 2007 From: jarrod at ipglobal.net (jarrod@ipglobal.net) Date: Mon Aug 6 05:21:17 2007 Subject: freebsd-cluster In-Reply-To: <73a01bf20708052050j1e1a3a6dp22bdbcb0275eed1d@mail.gmail.com> References: <103693.94307.qm@web86107.mail.ird.yahoo.com> <73a01bf20708052050j1e1a3a6dp22bdbcb0275eed1d@mail.gmail.com> Message-ID: <4480.98.201.15.111.1186376243.squirrel@reademail.com> I am interested to know if a distributed file system exists for freebsd similar to redhat GFS? I am aware of a few that exist, but require integration at the application layer. I desire a fs that client servers running standard server hardware for accessing the same backend information. > What kind of cluster?? The requirements for an HPC cluster and that of > a HA cluster are different... > > Rayson > > > > On 8/3/07, herve lubaki wrote: >> He! >> I' m herve,I study in university of Kinshasa ( D.R. of Congo); option >> informatic. >> I' want to know how to make a basic freedsd-cluster of servers and >> if someone can give my softwares and doc for cluster for that. >> thrank!! >> e-mail : hervelubaki2001@yahoo.fr >> >> >> --------------------------------- >> Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! >> Mail >> _______________________________________________ >> freebsd-cluster@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-cluster >> To unsubscribe, send any mail to >> "freebsd-cluster-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-cluster@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-cluster > To unsubscribe, send any mail to "freebsd-cluster-unsubscribe@freebsd.org" > From johndecot at yahoo.com Mon Aug 6 08:20:29 2007 From: johndecot at yahoo.com (john decot) Date: Mon Aug 6 08:20:32 2007 Subject: metric problem Message-ID: <962834.37025.qm@web55404.mail.re4.yahoo.com> Hi all, As I am new user for clustering, I am trying LAM/MPI with ganglia. I have face a problem while monitoring ganglia with web. i.e can't locate metric for selected cluster. I have telnet 127.0.0.1 8652 and results shows without metric. Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. ]> gmod.conf as follows: /* This configuration is as close to 2.5.x default behavior as possible The values closely match ./gmond/metric.h definitions in 2.5.x */ globals { daemonize = yes setuid = yes user = ganglia debug_level = 0 max_udp_msg_len = 1472 mute = no deaf = no host_dmax = 0 /*secs */ cleanup_threshold = 300 /*secs */ gexec = no } /* If a cluster attribute is specified, then all gmond hosts are wrapped inside * of a tag. If you do not specify a cluster tag, then all will * NOT be wrapped inside of a tag. */ cluster { name = "my cluster" owner = "unspecified" latlong = "unspecified" url = "unspecified" } /* The host section describes attributes of the host, like the location */ host { location = "unspecified" } /* Feel free to specify as many udp_send_channels as you like. Gmond used to only support having a single channel */ udp_send_channel { #mcast_join = 239.2.11.71 port = 8649 } /* You can specify as many udp_recv_channels as you like as well. */ udp_recv_channel { # mcast_join = 239.2.11.71 port = 8649 # bind = 239.2.11.71 } /* You can specify as many tcp_accept_channels as you like to share an xml description of the state of the cluster */ tcp_accept_channel { port = 8649 } /* The old internal 2.5.x metric array has been replaced by the following collection_group directives. What follows is the default behavior for collecting and sending metrics that is as close to 2.5.x behavior as possible. */ /* This collection group will cause a heartbeat (or beacon) to be sent every 20 seconds. In the heartbeat is the GMOND_STARTED data which expresses the age of the running gmond. */ collection_group { collect_once = yes time_threshold = 20 metric { name = "heartbeat" } } /* This collection group will send general info about this host every 1200 secs. This information doesn't change between reboots and is only collected once. */ collection_group { collect_once = yes time_threshold = 1200 metric { name = "cpu_num" } metric { name = "cpu_speed" } metric { name = "mem_total" } /* Should this be here? Swap can be added/removed between reboots. */ metric { name = "swap_total" } metric { name = "boottime" } metric { name = "machine_type" } metric { name = "os_name" } metric { name = "os_release" } metric { name = "location" } } /* This collection group will send the status of gexecd for this host every 300 secs */ /* Unlike 2.5.x the default behavior is to report gexecd OFF. */ collection_group { collect_once = yes time_threshold = 300 metric { name = "gexec" } } /* This collection group will collect the CPU status info every 20 secs. The time threshold is set to 90 seconds. In honesty, this time_threshold could be set significantly higher to reduce unneccessary network chatter. */ collection_group { collect_every = 20 time_threshold = 90 /* CPU status */ metric { name = "cpu_user" value_threshold = "1.0" } metric { name = "cpu_system" value_threshold = "1.0" } metric { name = "cpu_idle" value_threshold = "5.0" } metric { name = "cpu_nice" value_threshold = "1.0" } metric { name = "cpu_aidle" value_threshold = "5.0" } metric { name = "cpu_wio" value_threshold = "1.0" } /* The next two metrics are optional if you want more detail... ... since they are accounted for in cpu_system. metric { name = "cpu_intr" value_threshold = "1.0" } metric { name = "cpu_sintr" value_threshold = "1.0" } */ } collection_group { collect_every = 20 time_threshold = 90 /* Load Averages */ metric { name = "load_one" value_threshold = "1.0" } metric { name = "load_five" value_threshold = "1.0" } metric { name = "load_fifteen" value_threshold = "1.0" } } /* This group collects the number of running and total processes */ collection_group { collect_every = 80 time_threshold = 950 metric { name = "proc_run" value_threshold = "1.0" } metric { name = "proc_total" value_threshold = "1.0" } } /* This collection group grabs the volatile memory metrics every 40 secs and sends them at least every 180 secs. This time_threshold can be increased significantly to reduce unneeded network traffic. */ collection_group { collect_every = 40 time_threshold = 180 metric { name = "mem_free" value_threshold = "1024.0" } metric { name = "mem_shared" value_threshold = "1024.0" } metric { name = "mem_buffers" value_threshold = "1024.0" } metric { name = "mem_cached" value_threshold = "1024.0" } metric { name = "swap_free" value_threshold = "1024.0" } } collection_group { collect_every = 40 time_threshold = 300 metric { name = "bytes_out" value_threshold = 4096 } metric { name = "bytes_in" value_threshold = 4096 } metric { name = "pkts_in" value_threshold = 256 } metric { name = "pkts_out" value_threshold = 256 } } /* Different than 2.5.x default since the old config made no sense */ collection_group { collect_every = 1800 time_threshold = 3600 metric { name = "disk_total" value_threshold = 1.0 } } collection_group { collect_every = 40 time_threshold = 180 metric { name = "disk_free" value_threshold = 1.0 } metric { name = "part_max_used" value_threshold = 1.0 } } gmetad.conf as follows : # This is an example of a Ganglia Meta Daemon configuration file # http://ganglia.sourceforge.net/ # # $Id: gmetad.conf,v 1.17 2005/03/15 18:15:05 massie Exp $ # #------------------------------------------------------------------------------- # Setting the debug_level to 1 will keep daemon in the forground and # show only error messages. Setting this value higher than 1 will make # gmetad output debugging information and stay in the foreground. # default: 0 # debug_level 10 # #------------------------------------------------------------------------------- # What to monitor. The most important section of this file. # # The data_source tag specifies either a cluster or a grid to # monitor. If we detect the source is a cluster, we will maintain a complete # set of RRD databases for it, which can be used to create historical # graphs of the metrics. If the source is a grid (it comes from another gmetad), # we will only maintain summary RRDs for it. # # Format: # data_source "my cluster" [polling interval] address1:port addreses2:port ... # # The keyword 'data_source' must immediately be followed by a unique # string which identifies the source, then an optional polling interval in # seconds. The source will be polled at this interval on average. # If the polling interval is omitted, 15sec is asssumed. # # A list of machines which service the data source follows, in the # format ip:port, or name:port. If a port is not specified then 8649 # (the default gmond port) is assumed. # default: There is no default value # # data_source "my cluster" 10 localhost my.machine.edu:8649 1.2.3.5:8655 # data_source "my grid" 50 1.3.4.7:8655 grid.org:8651 grid-backup.org:8651 # data_source "another source" 1.3.4.7:8655 1.3.4.8 data_source "my cluster" 10 localhost # # Round-Robin Archives # You can specify custom Round-Robin archives here (defaults are listed below) # # RRAs "RRA:AVERAGE:0.5:1:240" "RRA:AVERAGE:0.5:24:240" "RRA:AVERAGE:0.5:168:240" "RRA:AVERAGE:0.5:672:240" \ # "RRA:AVERAGE:0.5:5760:370" # # #------------------------------------------------------------------------------- # Scalability mode. If on, we summarize over downstream grids, and respect # authority tags. If off, we take on 2.5.0-era behavior: we do not wrap our output # in tags, we ignore all tags we see, and always assume # we are the "authority" on data source feeds. This approach does not scale to # large groups of clusters, but is provided for backwards compatibility. # default: on # scalable off # #------------------------------------------------------------------------------- # The name of this Grid. All the data sources above will be wrapped in a GRID # tag with this name. # default: Unspecified # gridname "MyGrid" # #------------------------------------------------------------------------------- # The authority URL for this grid. Used by other gmetads to locate graphs # for our data sources. Generally points to a ganglia/ # website on this machine. # default: "http://hostname/ganglia/", # where hostname is the name of this machine, as defined by gethostname(). # authority "http://mycluster.org/newprefix/" # #------------------------------------------------------------------------------- # List of machines this gmetad will share XML with. Localhost # is always trusted. # default: There is no default value # trusted_hosts 127.0.0.1 169.229.50.165 my.gmetad.org # #------------------------------------------------------------------------------- # If you want any host which connects to the gmetad XML to receive # data, then set this value to "on" # default: off # all_trusted on # #------------------------------------------------------------------------------- # If you don't want gmetad to setuid then set this to off # default: on # setuid off # #------------------------------------------------------------------------------- # User gmetad will setuid to (defaults to "ganglia") # default: "ganglia" # setuid_username "ganglia" # #------------------------------------------------------------------------------- # The port gmetad will answer requests for XML # default: 8651 # xml_port 8651 # #------------------------------------------------------------------------------- # The port gmetad will answer queries for XML. This facility allows # simple subtree and summation views of the XML tree. # default: 8652 # interactive_port 8652 # #------------------------------------------------------------------------------- # The number of threads answering XML requests # default: 4 # server_threads 10 # #------------------------------------------------------------------------------- # Where gmetad stores its round-robin databases # default: "/var/db/ganglia/rrds" # rrd_rootdir "/some/other/place" so, could some help me to set metric Regards, John --------------------------------- Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center. From johndecot at yahoo.com Mon Aug 6 09:14:52 2007 From: johndecot at yahoo.com (john decot) Date: Mon Aug 6 09:14:55 2007 Subject: metric problem Message-ID: <471603.56671.qm@web55407.mail.re4.yahoo.com> Hi all, As I am new user for clustering, I am trying LAM/MPI with ganglia. I have face a problem while monitoring ganglia with web. i.e can't locate metric for selected cluster. I have telnet 127.0.0.1 8652 and results shows without metric. Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. ]> gmod.conf as follows: /* This configuration is as close to 2.5.x default behavior as possible The values closely match ./gmond/metric.h definitions in 2.5.x */ globals { daemonize = yes setuid = yes user = ganglia debug_level = 0 max_udp_msg_len = 1472 mute = no deaf = no host_dmax = 0 /*secs */ cleanup_threshold = 300 /*secs */ gexec = no } /* If a cluster attribute is specified, then all gmond hosts are wrapped inside * of a tag. If you do not specify a cluster tag, then all will * NOT be wrapped inside of a tag. */ cluster { name = "my cluster" owner = "unspecified" latlong = "unspecified" url = "unspecified" } /* The host section describes attributes of the host, like the location */ host { location = "unspecified" } /* Feel free to specify as many udp_send_channels as you like. Gmond used to only support having a single channel */ udp_send_channel { #mcast_join = 239.2.11.71 port = 8649 } /* You can specify as many udp_recv_channels as you like as well. */ udp_recv_channel { # mcast_join = 239.2.11.71 port = 8649 # bind = 239.2.11.71 } /* You can specify as many tcp_accept_channels as you like to share an xml description of the state of the cluster */ tcp_accept_channel { port = 8649 } /* The old internal 2.5.x metric array has been replaced by the following collection_group directives. What follows is the default behavior for collecting and sending metrics that is as close to 2.5.x behavior as possible. */ /* This collection group will cause a heartbeat (or beacon) to be sent every 20 seconds. In the heartbeat is the GMOND_STARTED data which expresses the age of the running gmond. */ collection_group { collect_once = yes time_threshold = 20 metric { name = "heartbeat" } } /* This collection group will send general info about this host every 1200 secs. This information doesn't change between reboots and is only collected once. */ collection_group { collect_once = yes time_threshold = 1200 metric { name = "cpu_num" } metric { name = "cpu_speed" } metric { name = "mem_total" } /* Should this be here? Swap can be added/removed between reboots. */ metric { name = "swap_total" } metric { name = "boottime" } metric { name = "machine_type" } metric { name = "os_name" } metric { name = "os_release" } metric { name = "location" } } /* This collection group will send the status of gexecd for this host every 300 secs */ /* Unlike 2.5.x the default behavior is to report gexecd OFF. */ collection_group { collect_once = yes time_threshold = 300 metric { name = "gexec" } } /* This collection group will collect the CPU status info every 20 secs. The time threshold is set to 90 seconds. In honesty, this time_threshold could be set significantly higher to reduce unneccessary network chatter. */ collection_group { collect_every = 20 time_threshold = 90 /* CPU status */ metric { name = "cpu_user" value_threshold = "1.0" } metric { name = "cpu_system" value_threshold = "1.0" } metric { name = "cpu_idle" value_threshold = "5.0" } metric { name = "cpu_nice" value_threshold = "1.0" } metric { name = "cpu_aidle" value_threshold = "5.0" } metric { name = "cpu_wio" value_threshold = "1.0" } /* The next two metrics are optional if you want more detail... ... since they are accounted for in cpu_system. metric { name = "cpu_intr" value_threshold = "1.0" } metric { name = "cpu_sintr" value_threshold = "1.0" } */ } collection_group { collect_every = 20 time_threshold = 90 /* Load Averages */ metric { name = "load_one" value_threshold = "1.0" } metric { name = "load_five" value_threshold = "1.0" } metric { name = "load_fifteen" value_threshold = "1.0" } } /* This group collects the number of running and total processes */ collection_group { collect_every = 80 time_threshold = 950 metric { name = "proc_run" value_threshold = "1.0" } metric { name = "proc_total" value_threshold = "1.0" } } /* This collection group grabs the volatile memory metrics every 40 secs and sends them at least every 180 secs. This time_threshold can be increased significantly to reduce unneeded network traffic. */ collection_group { collect_every = 40 time_threshold = 180 metric { name = "mem_free" value_threshold = "1024.0" } metric { name = "mem_shared" value_threshold = "1024.0" } metric { name = "mem_buffers" value_threshold = "1024.0" } metric { name = "mem_cached" value_threshold = "1024.0" } metric { name = "swap_free" value_threshold = "1024.0" } } collection_group { collect_every = 40 time_threshold = 300 metric { name = "bytes_out" value_threshold = 4096 } metric { name = "bytes_in" value_threshold = 4096 } metric { name = "pkts_in" value_threshold = 256 } metric { name = "pkts_out" value_threshold = 256 } } /* Different than 2.5.x default since the old config made no sense */ collection_group { collect_every = 1800 time_threshold = 3600 metric { name = "disk_total" value_threshold = 1.0 } } collection_group { collect_every = 40 time_threshold = 180 metric { name = "disk_free" value_threshold = 1.0 } metric { name = "part_max_used" value_threshold = 1.0 } } gmetad.conf as follows : # This is an example of a Ganglia Meta Daemon configuration file # http://ganglia.sourceforge.net/ # # $Id: gmetad.conf,v 1.17 2005/03/15 18:15:05 massie Exp $ # #------------------------------------------------------------------------------- # Setting the debug_level to 1 will keep daemon in the forground and # show only error messages. Setting this value higher than 1 will make # gmetad output debugging information and stay in the foreground. # default: 0 # debug_level 10 # #------------------------------------------------------------------------------- # What to monitor. The most important section of this file. # # The data_source tag specifies either a cluster or a grid to # monitor. If we detect the source is a cluster, we will maintain a complete # set of RRD databases for it, which can be used to create historical # graphs of the metrics. If the source is a grid (it comes from another gmetad), # we will only maintain summary RRDs for it. # # Format: # data_source "my cluster" [polling interval] address1:port addreses2:port ... # # The keyword 'data_source' must immediately be followed by a unique # string which identifies the source, then an optional polling interval in # seconds. The source will be polled at this interval on average. # If the polling interval is omitted, 15sec is asssumed. # # A list of machines which service the data source follows, in the # format ip:port, or name:port. If a port is not specified then 8649 # (the default gmond port) is assumed. # default: There is no default value # # data_source "my cluster" 10 localhost my.machine.edu:8649 1.2.3.5:8655 # data_source "my grid" 50 1.3.4.7:8655 grid.org:8651 grid-backup.org:8651 # data_source "another source" 1.3.4.7:8655 1.3.4.8 data_source "my cluster" 10 localhost # # Round-Robin Archives # You can specify custom Round-Robin archives here (defaults are listed below) # # RRAs "RRA:AVERAGE:0.5:1:240" "RRA:AVERAGE:0.5:24:240" "RRA:AVERAGE:0.5:168:240" "RRA:AVERAGE:0.5:672:240" \ # "RRA:AVERAGE:0.5:5760:370" # # #------------------------------------------------------------------------------- # Scalability mode. If on, we summarize over downstream grids, and respect # authority tags. If off, we take on 2.5.0-era behavior: we do not wrap our output # in tags, we ignore all tags we see, and always assume # we are the "authority" on data source feeds. This approach does not scale to # large groups of clusters, but is provided for backwards compatibility. # default: on # scalable off # #------------------------------------------------------------------------------- # The name of this Grid. All the data sources above will be wrapped in a GRID # tag with this name. # default: Unspecified # gridname "MyGrid" # #------------------------------------------------------------------------------- # The authority URL for this grid. Used by other gmetads to locate graphs # for our data sources. Generally points to a ganglia/ # website on this machine. # default: "http://hostname/ganglia/", # where hostname is the name of this machine, as defined by gethostname(). # authority "http://mycluster.org/newprefix/" # #------------------------------------------------------------------------------- # List of machines this gmetad will share XML with. Localhost # is always trusted. # default: There is no default value # trusted_hosts 127.0.0.1 169.229.50.165 my.gmetad.org # #------------------------------------------------------------------------------- # If you want any host which connects to the gmetad XML to receive # data, then set this value to "on" # default: off # all_trusted on # #------------------------------------------------------------------------------- # If you don't want gmetad to setuid then set this to off # default: on # setuid off # #------------------------------------------------------------------------------- # User gmetad will setuid to (defaults to "ganglia") # default: "ganglia" # setuid_username "ganglia" # #------------------------------------------------------------------------------- # The port gmetad will answer requests for XML # default: 8651 # xml_port 8651 # #------------------------------------------------------------------------------- # The port gmetad will answer queries for XML. This facility allows # simple subtree and summation views of the XML tree. # default: 8652 # interactive_port 8652 # #------------------------------------------------------------------------------- # The number of threads answering XML requests # default: 4 # server_threads 10 # #------------------------------------------------------------------------------- # Where gmetad stores its round-robin databases # default: "/var/db/ganglia/rrds" # rrd_rootdir "/some/other/place" so, could some help me to set metric Regards, John --------------------------------- Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, when. From anderson at freebsd.org Mon Aug 6 11:47:53 2007 From: anderson at freebsd.org (Eric Anderson) Date: Mon Aug 6 11:47:55 2007 Subject: freebsd-cluster In-Reply-To: <4480.98.201.15.111.1186376243.squirrel@reademail.com> References: <103693.94307.qm@web86107.mail.ird.yahoo.com> <73a01bf20708052050j1e1a3a6dp22bdbcb0275eed1d@mail.gmail.com> <4480.98.201.15.111.1186376243.squirrel@reademail.com> Message-ID: <46B70636.9000807@freebsd.org> On 08/05/07 23:57, jarrod@ipglobal.net wrote: > I am interested to know if a distributed file system exists for freebsd > similar to redhat GFS? I am aware of a few that exist, but require > integration at the application layer. I desire a fs that client servers > running standard server hardware for accessing the same backend > information. There are no clustered file systems for FreeBSD, and only Coda comes close, but probably not what you want. Maybe NFS can work for you, but more than likely not. Eric >> What kind of cluster?? The requirements for an HPC cluster and that of >> a HA cluster are different... >> >> Rayson >> >> >> >> On 8/3/07, herve lubaki wrote: >>> He! >>> I' m herve,I study in university of Kinshasa ( D.R. of Congo); option >>> informatic. >>> I' want to know how to make a basic freedsd-cluster of servers and >>> if someone can give my softwares and doc for cluster for that. >>> thrank!! >>> e-mail : hervelubaki2001@yahoo.fr >>> >>> >>> --------------------------------- >>> Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! >>> Mail >>> _______________________________________________ >>> freebsd-cluster@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-cluster >>> To unsubscribe, send any mail to >>> "freebsd-cluster-unsubscribe@freebsd.org" >>> >> _______________________________________________ >> freebsd-cluster@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-cluster >> To unsubscribe, send any mail to "freebsd-cluster-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-cluster@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-cluster > To unsubscribe, send any mail to "freebsd-cluster-unsubscribe@freebsd.org" From jarrod at ipglobal.net Mon Aug 6 15:19:11 2007 From: jarrod at ipglobal.net (Jarrod Baumann) Date: Mon Aug 6 15:19:12 2007 Subject: freebsd-cluster In-Reply-To: <46B70636.9000807@freebsd.org> References: <103693.94307.qm@web86107.mail.ird.yahoo.com> <73a01bf20708052050j1e1a3a6dp22bdbcb0275eed1d@mail.gmail.com> <4480.98.201.15.111.1186376243.squirrel@reademail.com> <46B70636.9000807@freebsd.org> Message-ID: <001801c7d839$697f14a0$3c7d3de0$@net> How about and drivers, experimental/beta or not, that exist for mounting other existing clustered DFS environments? I have come up empty on Google :( -----Original Message----- From: Eric Anderson [mailto:anderson@freebsd.org] Sent: Monday, August 06, 2007 6:30 AM To: jarrod@ipglobal.net Cc: freebsd-cluster@freebsd.org Subject: Re: freebsd-cluster On 08/05/07 23:57, jarrod@ipglobal.net wrote: > I am interested to know if a distributed file system exists for freebsd > similar to redhat GFS? I am aware of a few that exist, but require > integration at the application layer. I desire a fs that client servers > running standard server hardware for accessing the same backend > information. There are no clustered file systems for FreeBSD, and only Coda comes close, but probably not what you want. Maybe NFS can work for you, but more than likely not. Eric >> What kind of cluster?? The requirements for an HPC cluster and that of >> a HA cluster are different... >> >> Rayson >> >> >> >> On 8/3/07, herve lubaki wrote: >>> He! >>> I' m herve,I study in university of Kinshasa ( D.R. of Congo); option >>> informatic. >>> I' want to know how to make a basic freedsd-cluster of servers and >>> if someone can give my softwares and doc for cluster for that. >>> thrank!! >>> e-mail : hervelubaki2001@yahoo.fr >>> >>> >>> --------------------------------- >>> Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! >>> Mail >>> _______________________________________________ >>> freebsd-cluster@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-cluster >>> To unsubscribe, send any mail to >>> "freebsd-cluster-unsubscribe@freebsd.org" >>> >> _______________________________________________ >> freebsd-cluster@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-cluster >> To unsubscribe, send any mail to "freebsd-cluster-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-cluster@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-cluster > To unsubscribe, send any mail to "freebsd-cluster-unsubscribe@freebsd.org" From olli at lurza.secnetix.de Mon Aug 6 15:55:38 2007 From: olli at lurza.secnetix.de (Oliver Fromme) Date: Mon Aug 6 15:55:43 2007 Subject: freebsd-cluster In-Reply-To: <001801c7d839$697f14a0$3c7d3de0$@net> Message-ID: <200708061555.l76FtUo2043815@lurza.secnetix.de> Jarrod Baumann wrote: > How about and drivers, experimental/beta or not, that exist for > mounting other existing clustered DFS environments? Well, there's FUSE in FreeBSD's ports collection, so you should be able to mount any file system for which there is a FUSE driver available. In theory. FUSE provides an API that allows file system drivers to run in userland. There's a ton of FUSE file systems on its home page ... Most of them are only written and tested on Linux, but it should be possible to compile and run them on FreeBSD with minor efforts.) Other than that, there is no distributed file system for FreeBSD. Coda and AFS have been mentioned, but last time I looked they were not really usable. When a customer asks me to set up clustered storage (HA), I usually recommend a NetApp Filer cluster. At least they use a BSD-derived OS, so it's not completely off-topic. ;-) Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Gesch?ftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M?n- chen, HRB 125758, Gesch?ftsf?hrer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd C++: "an octopus made by nailing extra legs onto a dog" -- Steve Taylor, 1998 From anderson at freebsd.org Tue Aug 7 19:46:37 2007 From: anderson at freebsd.org (Eric Anderson) Date: Tue Aug 7 19:46:40 2007 Subject: freebsd-cluster In-Reply-To: <200708061555.l76FtUo2043815@lurza.secnetix.de> References: <200708061555.l76FtUo2043815@lurza.secnetix.de> Message-ID: <46B8CC16.9070309@freebsd.org> Oliver Fromme wrote: > Jarrod Baumann wrote: > > How about and drivers, experimental/beta or not, that exist for > > mounting other existing clustered DFS environments? > > Well, there's FUSE in FreeBSD's ports collection, so you > should be able to mount any file system for which there is > a FUSE driver available. In theory. > > FUSE provides an API that allows file system drivers to > run in userland. There's a ton of FUSE file systems on > its home page ... Most of them are only written and tested > on Linux, but it should be possible to compile and run them > on FreeBSD with minor efforts.) > > Other than that, there is no distributed file system for > FreeBSD. Coda and AFS have been mentioned, but last time > I looked they were not really usable. > > When a customer asks me to set up clustered storage (HA), > I usually recommend a NetApp Filer cluster. At least they > use a BSD-derived OS, so it's not completely off-topic. ;-) > > Best regards > Oliver > Oh, and I forgot to mention this piece of software: http://www.bsdcluster.com/ I haven't played with it recently, but it was promising when I did play with it about a year ago. It's not a clustered file system implementation, but it does have some failover/HA pieces in it, and some VFS hooks to distribute changes. It's worth a look for sure.. Eric From register at dating24.ro Sun Aug 19 18:09:16 2007 From: register at dating24.ro (dating24) Date: Sun Aug 19 18:09:22 2007 Subject: Your account on dating24.ro Enjoy! Message-ID: <20070819183026.1163.qmail@runemedia.net> [1]www.dating24.ro - anunturi - prietenii - intalniri - matrimoniale - - chat privat - chat public - poze - [2]Intra si tu alaturi de prietenii tai in comunitatea dating24.ro Te asteptam! [3]Inregistreaza-te acum! _________________________________________________________________ Utilizatorii Yahoo, Gmail sau Hotmail! In cazul in care ati primit acest mesaj in Bulk va rugam sa adaugati adresa noreply@dating24.ro in Adress Book sau la Contacte Personale, dupa caz. Va multumim pentru intelegere si va uram succes in continuare. Echipa [4]dating24.ro References 1. http://www.dating24.ro/ 2. http://www.dating24.ro/ 3. http://www.dating24.ro/inregistrare_pas1.php 4. http://www.dating24.ro/