White dot for spacing only
The Dice Project


Summary of decisions from DICE Deployment meetings

These are listed in reverse order: most recent first.

2002-10-15

  1. Shared filespace hierarchy: There will be a shared filespace hierarchy based at /group with an unrestricted structure. This will be rfe-editable

2002-08-20

  1. Changing the hostname of machine: If a machine in the inf domain has its hostname changed then it is a requirement that the machine undergoes a complete re-installation. This is to guarantee that any kerberos client key belonging to the previous use of the machine is destroyed.
  2. New users: It was agreed that after 2002-09-18 any new users would only be given accounts in the DICE world and none (that they could use) in the legacy domains. It was acceptable however to have skeleton entries in the legacy passwd maps to ease administration of their file space.

2002-08-06

  1. /etc/resolv.conf searchlist: The default searchlist will only contain inf.ed.ac.uk. Users can configure their own one for their local machine.

2002-07-23

  1. Mozilla: Mozilla will be the default/recommended browser.
  2. Printing Duplex printing will be enabled by default on all printers monochrome and colour.
  3. RedHat 7.3 This will not be used as the default release for DICE and only provided where required initially. Some rollout may occur at Christmas 2002.

2002-07-09

  1. Backups:

2002-06-25

  1. Groups: Only known groups will be created for the moment; new requests will be handled on an ad-hoc basis.

2002-06-11

  1. Filesystem Maps:
    ltg
    to appear as /legacy/ltg. (Other groups such as CSTR, AIAI and ANC have still to be decided.)
    DCS student projects:
    to appear as /projects/<thing> where 'thing' is not a user.
    aisubmit
    will use /home/submit

2002-05-28

  1. Common Home Directories: CHDs not to be finalised until after term/Exam Board to avoid disruption.

2002-05-14

  1. Documentation: The documentation team will provide a framework for general purpose documentation for DICE(eg visitor).

2002-04-30

  1. 'staff' roles: there is no need for sub-categories within the 'staff' role (eg visitor).
  2. Privacy: all information required for the purposes of administering systems will be considered public.
  3. default 7.1: the default RedHat release will be 7.1
  4. Pseudo-user UIDs: for 'local' pseudo-users use UIDs in the range 500-999, starting from 999 counting down.

2002-04-16

  1. Backups: backup facilities will be required on clients.
  2. POP: the mailhub will not support POP access

2002-04-02

  1. PhD UIDs: Where PhDs have UIDs (typically old accounts) that are not from the allocated student range we will not be altering them to conform
  2. Filesystem names These need to be defined standardly and a single component will add symlinks as required (corrected as per meeting of 2002-04-16).

2002-03-19

  1. Secondary groups: We will have a minimal number of standard secondary groups in the DICE world and there will be a managed way of creating additional secondary groups.
  2. Calendar system: We recommend staff to use the central calendar system that should be available by the end of May. The Division will not be providing its own calendar service.
  3. User web pages: We will recommend that user web pages will have URL homepages.inf.ed.ac.uk/user. Other alternativer URLs mentioned in Neil's reports will be implemented as redirects.
  4. /volatile, /public and /yesterday The following filesystem areas will be created: [See relevant section for full details.]

2002-03-05

  1. Applications: the legacy applications tasks reports will move to be sub-parts of single Applications task and include applications that need attention for DICE (eg VMware).
  2. Goals/Milestones: there is now a single page for these which everyone will edit. It will also include all actions related to a task. Reports should still have a Recent Changes section.

2002-02-19

  1. Primary groups There would be just two primary groups; one for real users and one for daemon-like pseudo-users. Test accounts that require a full user environment would fall into the first category.
  2. Secondary groups We will continue to need secondary groups to control access to the file system (until the latter is replaced). Some predefined secondary groups will be derived from roles.

2002-02-05

  1. '-doc' proposal accepted.
  2. Coding Languages: unless there are extenuating circumstances coding/scripting should be in C, PERL or Bourne Shell.
  3. Tasks/Actions/Timescales
  4. Review of Reports


 : Deploy : Meetings 

Mini Informatics Logo - Link to Main Informatics Page
Please contact us with any comments or corrections.
Unless explicitly stated otherwise, all material is copyright The University of Edinburgh
Spacing Line