[OpenAFS] Deploying OpenAFS on VMs

Coy Hile coy.hile@coyhile.com
Mon, 20 Jun 2011 14:54:39 -0400

On Mon, Jun 20, 2011 at 12:56 PM, Hoskins, Matthew
<Matthew.Hoskins@njit.edu> wrote:

> =B7=A0=A0=A0=A0=A0=A0=A0=A0 Many fileservers / smaller fileservers:=A0 =
=A0This philosophy has
> evolved as we have moved more into virtualized fileservers.=A0=A0 With ph=
> hardware you are limited by ABILITY TO PURCHASE.=A0 Meaning, you can only=
> =93x=94 number of servers of =93n=94 size. =A0=A0This means if you want h=
ighly resilient
> servers, you can only afford to by a few of them.=A0=A0 This can lead to =
> fat fileservers.=A0=A0 If you go for many cheap fileservers, you might be=
> to get more distributed but end up suffering more small individual outage=
> =A0=A0With virtualized fileservers you have full flexibility.=A0 On the v=
> platform, you get HA by default on every VM.=A0=A0=A0 After that you get =
to design
> your fileserver layout decisions based on the DATA they will store.=A0=A0=
=A0 For
> example, in our layout we have the following classes of fileservers:
> o=A0=A0 Infrastructure (INF) Fileservers:=A0 Very small fileserver, for h=
> critical root.*, software, etc. the =93bones=94 of the cell.=A0 Replicate=
d of
> course.
> o=A0=A0 User fileservers (USR):=A0 Home volumes, nuff said
> o=A0=A0 Bulk Fileservers (BLK): Almost everything else, projects, web con=
> research data, yadda yadda
> o=A0=A0 Jumbo Fileservers (JMB):=A0 Used for ridiculously large volumes.=
=A0 These
> fileservers are the only fileserver that has a VARIABLE vicep partition
> size.=A0 =A0Used for archival data and some research projects.


What do you use for vicep* partition sizes?