The inf layer

The inf layer is a minimal add-on to the lcfg layer. It's as close as you can get to just using the lcfg layer. (The lcfg layer itself doesn't contain a complete working configuration.)

When you put something in the lcfg or ed levels it makes it available for other parts of the University to use. However they can only use it if it doesn't depend on something in the dice level. You can test your software for these dependencies by trying it out on an inf level machine - see below.

The inf layer comes in several flavours as noted further down this page. Choose a flavour depending on whether you want to test just the lcfg layer, or add in the ed layer, or add in dice repositories too.

The inf layer uses DICE kerberos and ldap. It uses the LCFG kerberos component to configure kerberos. It only uses the openldap component if USE_OPENLDAP_COMPONENT is defined; otherwise it uses the file component to configure ldap. (For SL6 this is temporarily broken and it uses the lcfg-openldap component regardless.)

An inf layer test machine

There's a host at inf level which you can use for testing. It has the alias inflevel. If you ssh inflevel you will be prompted for your DICE password; this is OK. It has local home directories. If you need to, change its "flavour" by editing its LCFG file then running updaterpms and rebooting. You will need to become root to get enough privilege to run components. Use scp or similar to transfer files to it.

The minimal flavour

#define INF_FLAVOUR_MINIMAL

Doesn't use any "ed" level packages or configuration. Uses INF for auth and dir.

The ed flavour

#define INF_FLAVOUR_ED

As minimal but with ed layer packages and configuration

Uses ed layer kernel.h

DICE openafs configuration included

The dice flavour

#define INF_FLAVOUR_DICE

As ed but with dice repositories enabled

Uses ed layer kernel.h

hostkey enabled (kdcregister enabled)

pxeclient configured

DICE openafs configuration included

-- AlastairScobie - 07 Mar 2011