storage

[phpwiki]
Taking the time to read up on the GridShib CA and MyProxy CA was very useful. They and phpki ultimately all are backened by an openssl configuration so in a sense are compatible with each other. The decision to use one over the other seems to mainly be about where one stores a cert and how one can retreive it. The GridShib CA has a great way of creating certs that are truely private (client-based key) so I'm guessing there is not a key store in GridShib CA. MyProxy CA would seem to have a keystore since it's backended by Simple CA. This makes it like phpki except that the interface is command-line versus web.

It would be nice to have gridftp to transfer data between disk systems (if
that becomes necessary). This would be used when moving files between
physical locations and might occur as the result of a global filesystem
restructure, eg. a cp /path1/myfile /path2/myfile might result in the
initiation of a gridftp transfer for myfile between the hosts the provide
/path1 and /path2.

did a poor job of recording tasks today. spent the afternoon split between two projects, storage and mlist. Started recording my namespace understands and wishes for the storage project and documented the home automounting config. Set up a test rss gw list feed for the mlist project.

[phpwiki]
Our home dirs are mounted by using nfs and the automounter and
leveraging hostname aliases in the DNS.

Each machine that is to mount the home directories needs to be capable
of being an NFS client (http://nfs.sourceforge.net/nfs-howto/client.html).

Once it is an NFS client we need to configure the automounting system.
The reason we use the automounter is to avoid a lot of permanent mounts
of network resources. This can get messy if the server providing the
resources crashes.

The file that does the magic is the /etc/auto.home file. It should look
like this:

# $Id: auto.home,v 1.1 2003/05/27 16:26:39 root Exp jpr $

We are transitioning our storage resource to better distribute the
utilization of disk space. This transition is also geared toward
preparing for a consistent, predictable namespace accross all our
storage technologies.

The home directory configuration basically follows the idea that we have
a personal storage space allocated to us as part of our provisioned
resources in the lab. This space should be available through out the lab.

The most convenient way to do this is with nfs. This lets us house the
physical disks that make up the storage allocation on one machine but
have them available across the network.

Is it possible to assign mutliple IP addresses to a single interface using DHCP? The man page for dhcpd.conf suggests one can, but I haven't figured out how to do this. This is desirable so that we can multi-home our hosts to the internal/external IPs on the shared segment and not need to cross a router boundry for things like NFS file shares.